From 70d8373a03808e96b717cf691eb14095f0edd47d Mon Sep 17 00:00:00 2001 From: Steven Silvester Date: Mon, 4 Mar 2024 06:33:00 -0600 Subject: [PATCH] Update source/client-side-encryption/client-side-encryption.md Co-authored-by: Jeremy Mikola --- source/client-side-encryption/client-side-encryption.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/source/client-side-encryption/client-side-encryption.md b/source/client-side-encryption/client-side-encryption.md index 2ea088bc08..5f1cca96c7 100644 --- a/source/client-side-encryption/client-side-encryption.md +++ b/source/client-side-encryption/client-side-encryption.md @@ -2129,9 +2129,10 @@ Because single threaded drivers may exceed `serverSelectionTimeoutMS` by the dur ### What's the deal with metadataClient, keyVaultClient, and the internal client? -When automatically encrypting a command, the driver runs: - a `listCollections` command to determine if the target -collection has a remote schema. This uses the `metadataClient`. - a `find` against the key vault collection to fetch -keys. This uses the `keyVaultClient`. +When automatically encrypting a command, the driver runs: + +- a `listCollections` command to determine if the target collection has a remote schema. This uses the `metadataClient`. +- a `find` against the key vault collection to fetch keys. This uses the `keyVaultClient`. #### Why not reuse the parent MongoClient when maxPoolSize is limited?