Update source/client-side-encryption/client-side-encryption.md

Co-authored-by: Jeremy Mikola <jmikola@gmail.com>
mongodb · Mar 4, 2024 · 20f6a1e · 20f6a1e
1 parent e4bd1a6
commit 20f6a1e
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/source/client-side-encryption/client-side-encryption.md b/source/client-side-encryption/client-side-encryption.md
@@ -1023,7 +1023,7 @@ an API for explicitly encrypting and decrypting values, and managing data keys i
 See
 [Why do we have a separate top level type for ClientEncryption?](#why-do-we-have-a-separate-top-level-type-for-clientencryption)
 and
-[Why do we need to pass a client to create a ClientEncryption?](#why-do-we-need-to-pass-a-client-to-create-a-clientencryption).
+[Why do we need to pass a client to create a ClientEncryption?](#why-do-we-need-to-pass-a-client-to-create-a-clientencryption)
 
 When implementing behavior and error handling for key vault functions, Drivers SHOULD assume the presence of a unique
 index in the key vault collection on the `keyAltNames` field with a partial index filter for only documents where