DOCSP-24504 get featureCompatibilityVersion (#1637)

* DOCSP-24504 get featureCompatibilityVersion

* Remove space

Author: Dave Cuthbert

source/reference/command/setFeatureCompatibilityVersion.txt

@@ -7,7 +7,7 @@ setFeatureCompatibilityVersion
 .. contents:: On this page
    :local:
    :backlinks: none
-   :depth: 1
+   :depth: 2
    :class: singlecol
 
 Definition
@@ -156,58 +156,47 @@ Examples
 --------
 
 .. _view-fcv:
+.. _get-feature-compat-version: 
 
-View FeatureCompatibilityVersion
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Get FeatureCompatibilityVersion
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 To view the ``featureCompatibilityVersion`` for a :binary:`~bin.mongod`
-instance, run the following command on a :binary:`~bin.mongod` instance:
-
-.. note::
-
-   The operation is undefined on the :binary:`~bin.mongos` instances. For a
-   sharded cluster that has access control enabled, to run the command
-   against a member of the shard replica set, you must connect to the
-   member as a :ref:`shard local user <shard-local-users>`.
+instance, run the :dbcommand:`getParameter` command on a 
+:binary:`~bin.mongod` instance:
 
 .. code-block:: javascript
 
-   db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )
-
-The output from this command will resemble one of the following,
-depending on the current state of the :binary:`~bin.mongod`:
-
-- If the deployment has the default ``featureCompatibilityVersion``, or
-  if the :dbcommand:`setFeatureCompatibilityVersion` command has run
-  successfully against the deployment, the
-  ``featureCompatibilityVersion`` has the form:
-
-  .. code-block:: javascript
-
-     "featureCompatibilityVersion" : {
-        "version" : <version>
-     }
+   db.adminCommand( {
+                       getParameter: 1,
+                       featureCompatibilityVersion: 1
+                    }
+                  )
 
-- If the :binary:`~bin.mongod` is in a partially upgraded or downgraded
-  state, the ``featureCompatibilityVersion`` has the following form:
+The output resembles:
 
-  .. code-block:: javascript
+.. code-block:: javascript
 
-     "featureCompatibilityVersion" : {
-        "version" : <version> ,
-        "targetVersion" : <target version>
-     }
+   {
+     featureCompatibilityVersion: { version: '5.0' },
+     ok: 1,
+     '$clusterTime': {
+       clusterTime: Timestamp({ t: 1660318752, i: 5 }),
+       signature: {
+         hash: Binary(Buffer.from("ce0cff3621e9b089fa6d8e9a1e1efc1a1ff15dab", "hex"), 0),
+         keyId: Long("7129893797260951557")
+       }
+     },
+     operationTime: Timestamp({ t: 1660318752, i: 5 })
+   }
 
-  For instance, if a sharded cluster has a shard replica set that is
-  read only when you run :dbcommand:`setFeatureCompatibilityVersion`
-  command against the :binary:`~bin.mongos`, the command will fail, and the
-  ``featureCompatibilityVersion`` of the config servers will include
-  the ``targetVersion`` field.
+.. note::
 
-  Or if a replica set becomes read only while
-  :dbcommand:`setFeatureCompatibilityVersion` is running, the command
-  will fail, and the ``featureCompatibilityVersion`` of the replica set
-  will include the ``targetVersion`` field as well.
+   The operation is undefined on the :binary:`~bin.mongos` instances.
+   
+   On a sharded cluster that has access control enabled, you must
+   connect to the shard as a :ref:`shard local user <shard-local-users>`
+   to run the command.
 
 .. _set-fcv: