DOCSP-31018 feature compat case change (#3460)

* DOCSP-31018 feature compat case change

* Staging fix

Author: Dave Cuthbert

source/includes/arbiter-fcv.rst

@@ -1,5 +1,5 @@
 
 Arbiters do not replicate the :data:`admin.system.version` collection.
-Because of this, arbiters always have a Feature Compatibility Version equal
+Because of this, arbiters always have a feature compatibility version equal
 to the downgrade version of the binary, regardless of the fCV value of the
 replica set.

source/includes/downgrade-for-set-cluster-parameter.txt

@@ -1,4 +1,4 @@
 Starting in MongoDB 6.0, ensure that all :dbcommand:`setClusterParameter` 
-operations have completed. :abbr:`fCV (Feature Compatibility Version)` 
+operations have completed. :abbr:`fCV (feature compatibility version)` 
 downgrade cannot occur successfully if there are any ongoing 
 ``setClusterParameter`` operations on sharded clusters. 

source/includes/time-series-secondary-indexes-downgrade-FCV.rst

@@ -1,5 +1,5 @@
 If there are :term:`secondary indexes <secondary index>` on :ref:`time
 series collections <manual-timeseries-collection>` and you need to
-downgrade the Feature Compatibility Version (FCV), you must first drop
+downgrade the feature compatibility version (FCV), you must first drop
 any secondary indexes that are incompatible with the downgraded FCV.
 See :dbcommand:`setFeatureCompatibilityVersion`.

source/release-notes/3.4-downgrade-replica-set.txt

@@ -32,7 +32,7 @@ compatibility version and remove any :ref:`3.4 features incompatible
 outlined below. These steps are necessary only if
 ``featureCompatibilityVersion`` has ever been set  to ``"3.4"``.
 
-.. |fcv| replace:: :ref:`Feature Compatibility Version to "3.2"
+.. |fcv| replace:: :ref:`feature compatibility version to "3.2"
    <3.4-downgrade-feature-compatibility-rs>`
 
 .. |target| replace:: primary

source/release-notes/3.4-downgrade-sharded-cluster.txt

@@ -32,7 +32,7 @@ compatibility version and remove any :ref:`3.4 features incompatible
 below. These steps are necessary only if
 ``featureCompatibilityVersion`` has ever been set to ``"3.4"``.
 
-.. |fcv| replace:: :ref:`Feature Compatibility Version to "3.2" <3.4-downgrade-feature-compatibility-sharded-cluster>`
+.. |fcv| replace:: :ref:`feature compatibility version to "3.2" <3.4-downgrade-feature-compatibility-sharded-cluster>`
 
 .. |target| replace:: :binary:`~bin.mongos` instance
 

source/release-notes/3.4-downgrade.txt

@@ -51,7 +51,7 @@ or sharded cluster, see:
 
 .. |target| replace:: target
 
-.. |fcv| replace:: :ref:`Feature Compatibility Version to "3.2" <3.4-downgrade-feature-compatibility>`
+.. |fcv| replace:: :ref:`feature compatibility version to "3.2" <3.4-downgrade-feature-compatibility>`
 
 2. Remove Views
 ~~~~~~~~~~~~~~~

source/release-notes/6.0-downgrade-replica-set.txt

@@ -60,7 +60,7 @@ list of incompatible features and how to remove them, see
 
 .. |target| replace:: primary
 
-To downgrade the :abbr:`fCV (Feature Compatibility Version)` of your
+To downgrade the :abbr:`fCV (feature compatibility version)` of your
 replica set:
 
 a. Ensure that no initial sync is in progress. Running the

source/release-notes/6.0-downgrade-sharded-cluster.txt

@@ -73,7 +73,7 @@ operation will not complete.
 4. Downgrade Feature Compatibility Version (fCV)
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-To downgrade the :abbr:`fCV (Feature Compatibility Version)` of your
+To downgrade the :abbr:`fCV (feature compatibility version)` of your
 sharded cluster:
 
 a. Ensure that no initial sync is in progress. Running the