DOCSP-15287 remove multiple key string references (#2824) (#3158)

* DOCSP-15287 remove multiple key string references

* DOCSP-15287 remove multiple key string tab

* DOCSP-15287 remove multiple key string tab

* DOCSP-15287 nit fix

* DOCSP-15287 internal feedback

Author: jocelyn-mendez1

source/core/security-internal-authentication.txt

@@ -73,25 +73,12 @@ For example,
         content: |
 
           If the keyfile contains a single key, you can specify the key
-          string with or without quotes
+          string with or without quotes:
 
           .. code-block:: yaml
 
              my old secret key1
 
-      - id: multiple-key-strings
-        name: Multiple Key Strings
-        content: |
-
-           You can specify multiple key strings
-           [#exclude-encryption-keyfile]_ where each key string is
-           **enclosed in quotes**:
-
-           .. code-block:: yaml
-
-              'my old secret key1'
-              'my new secret key2'
-
       - id: multiple-key-sequence
         name: Multiple Key Sequence
         content: |

source/includes/extracts-4.2-changes.yaml

@@ -83,13 +83,11 @@ content: |
 
    Starting in MongoDB 4.2, :ref:`keyfiles for internal membership
    authentication <internal-auth-keyfile>` use YAML format to allow for
-   multiple keys in a keyfile. The YAML format accepts content of:
+   multiple keys in a keyfile. The YAML format accepts either:
 
-   - a single key string (same as in earlier versions),
+   - A single key string (same as in earlier versions)
    
-   - multiple key strings (each string must be enclosed in quotes), or
-   
-   - sequence of key strings.
+   - A sequence of key strings
 
    The YAML format is compatible with the existing single-key
    keyfiles that use the text file format.

source/tutorial/rotate-key-sharded-cluster.txt

@@ -4,8 +4,6 @@ Rotate Keys for Sharded Clusters
 
 .. default-domain:: mongodb
 
-
-
 Sharded cluster members can use :ref:`keyfiles <internal-auth-keyfile>`
 to authenticate each other as memers of the same deployment.
 
@@ -52,9 +50,7 @@ Procedure
 1. Modify the Keyfile to Include Old and New Keys
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Modify each member's keyfile to include both the old and new keys. You
-can specify multiple keys either as strings enclosed in quotes or as a
-sequence of keys.
+Modify each member's keyfile to include both the old and new keys.
 
 .. warning::
 
@@ -63,34 +59,14 @@ sequence of keys.
    keyfile using any method you choose (e.g. ``openssl rand -base64
    756``, etc.).
 
-.. tabs::
-
-   tabs:
-
-      - id: multiple-key-strings
-        name: Multiple Key Strings
-        content: |
-
-           You can specify multiple key strings where each key
-           string is **enclosed in quotes**
-
-           .. figure:: /images/example-multiple-keys1.png
-              :alt: Image of multiple key strings.
-              :figwidth: 600px
-
-
-      - id: multiple-key-sequence
-        name: Multiple Key Sequence
-        content: |
-
-           You can specify multiple key strings as a sequence of key
-           strings (optionally enclosed in quotes):
+You can specify multiple key strings as a sequence of key strings (optionally 
+enclosed in quotes):
 
-           .. figure:: /images/example-multiple-keys2.png
-              :alt: Image of multiple key string sequence.
-              :figwidth: 600px
+.. figure:: /images/example-multiple-keys2.png
+   :alt: Image of multiple key string sequence.
+   :figwidth: 600px
 
-2. Restart Each Member
+1. Restart Each Member
 ~~~~~~~~~~~~~~~~~~~~~~
 
 Once all the keyfiles contain both the old and new keys, restart each