From d98c9e7808cf28e4bc873b2b827c0cdaa076f750 Mon Sep 17 00:00:00 2001
From: Nino Risteski <95188570+NinoRisteski@users.noreply.github.com>
Date: Sat, 18 Jan 2025 08:23:04 +0100
Subject: [PATCH] Update completion-fn-protocol.md

---
 docs/completion-fn-protocol.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/completion-fn-protocol.md b/docs/completion-fn-protocol.md
index 2f9f6c0399..9a160a39f1 100644
--- a/docs/completion-fn-protocol.md
+++ b/docs/completion-fn-protocol.md
@@ -38,4 +38,4 @@ The `get_completions` method returns a list of string completions. Each element
 #### Using your CompletionFn
 This is all that's needed to implement a Completion function that works with our existing Evals, allowing you to more easily evaluate your end-to-end logic on tasks.
 
-See [completion-fns.md](completion-fns.md) to see how to register and use your completion function with `oaieval`.
+See [completion-fns.md](completion-fns.md) to find out how to register and use your completion function with `oaieval`.