From 6a5e9f894c4d1e6e4150cf7a10cd095e02a62e25 Mon Sep 17 00:00:00 2001
From: Mike Woofter <108414937+mongoKart@users.noreply.github.com>
Date: Tue, 2 Jul 2024 12:37:59 -0500
Subject: [PATCH] fix code

---
 source/whats-new.txt | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/source/whats-new.txt b/source/whats-new.txt
index b1d45f4a..de35c4c6 100644
--- a/source/whats-new.txt
+++ b/source/whats-new.txt
@@ -73,8 +73,12 @@ The {+driver-short+} v6.7 release includes the following features:
 - The ``ReadConcernMajorityNotAvailableYet`` error is now a retryable read error.
 
 - KMS providers can now be associated with a name, and multiple keys can be provided
-  for each KMS provider. The following code example shows how to configure a
-  ``ClientEncryption`` object with multiple AWS keys:
+  for each KMS provider. This feature requires ``mongodb-client-encryption`` v6.0.1 or later.
+  You can't use named KMS providers if your application uses the automatic
+  KMS provider refresh capability.
+
+  The following code example shows how to configure a ``ClientEncryption`` object with
+  multiple AWS keys:
 
 .. code-block:: javascript
    :copyable: true
@@ -91,10 +95,6 @@ The {+driver-short+} v6.7 release includes the following features:
   
    clientEncryption.createDataKey('aws:key-1', { ... });
 
-  You can't use named KMS providers if your application uses the automatic
-  KMS provider refresh capability.
-  This feature requires ``mongodb-client-encryption`` v6.0.1 or later.
-
 - When you create a KMIP data key, you can now specify the ``delegated`` option. If this
   option is set to ``true``, the KMIP provider performs encryption and decryption of
   the data key locally, ensuring that the encryption key never leaves the KMIP server.