(DOCSP-43740) [OM] Standardizing FCV (#470)

Standardizing FCV: 
- Replacing all instances of fCV or FCV with substitution |fcv| 
- Replacing all instances of "|fcv| of \<ver-num\>" with "|fcv|
\<ver-num\>"

------------------------------------------------------

- [DOCSP-43740](https://jira.mongodb.org/browse/DOCSP-43740)
-
[STAGING](https://deploy-preview-470--10gen-docs-ops-manager.netlify.app/)
- [LATEST BUILD
LOG](https://app.netlify.com/sites/10gen-docs-ops-manager/deploys/67095bb9c4044c000895880c)

### Self-Review Checklist

- [ ]
[Define](https://wiki.corp.mongodb.com/display/DE/Taxonomy+tagging+instructions)
taxonomy
[values](https://wiki.corp.mongodb.com/display/DE/Docs+Taxonomy) at top
of page.
- [ ] Add genre facets (tutorial or reference), as in this [example
PR](10gen/cloud-docs#5042).
- [ ] Add programmingLanguage (if necessary).
- [ ] Add meta keywords (if necessary).
- [x] Resolve any new warnings or errors in the build.
- [x] Proofread for spelling and grammatical errors.
- [x] Check staging for rendering issues.
- [x] Confirm links are working.

---------

Co-authored-by: Elyse Foreman <[email protected]>

Author: elyse-mdb

source/application.txt

@@ -79,7 +79,7 @@ Backup Workflow
 
 Backups rely upon the :manual:`MongoDB version compatibility
 </reference/command/setFeatureCompatibilityVersion>` of your database.
-For MongoDB 4.4, the FCV can be ``4.2`` or ``4.4``. 
+For MongoDB 4.4, the |fcv| can be ``4.2`` or ``4.4``. 
 
 .. include:: /includes/backup/wtchk-process-overview-main-om.rst
 

source/core/requirements.txt

@@ -58,7 +58,7 @@ for all |onprem| components that it serves:
    You want to serve both the |onprem| application and a
    :opsmgr:`Backup Daemon </reference/glossary/#std-term-backup-daemon>` on one host. 
    This |onprem| configuration will manage and monitor 300 MongoDB hosts,
-   back up 200 hosts, and run FCV 4.2 or later. The
+   back up 200 hosts, and run |fcv| 4.2 or later. The
    total disk capacity of all databases being backed up is 4 TB. 
    The total requirements would be:
 

source/includes/fact-index-rolling-build.rst

@@ -30,8 +30,7 @@ availability, |mms| removes one node from the cluster at a time
 starting with a :manual:`secondary </reference/glossary/#std-term-secondary>`.
 
 After you build an index in a rolling fashion, if your MongoDB database
-runs with an :manual:`FCV 
-</reference/command/setFeatureCompatibilityVersion>`
+runs with an |fcv-link|
 less than ``4.2``, :doc:`resync the head database 
 </tutorial/resync-backup>` to ensure that the head database takes the 
 new index into account.

source/includes/setting-fileConf-mms.backup.journal.heads.rst

@@ -10,7 +10,7 @@
    enable or disable journaling for the :opsmgr:`head database </reference/glossary/#std-term-head-database>` of a
    single backup job.
 
-   FCV |fcv-link| ``4.2`` and later use :term:`backup cursors 
+   |fcv-link| ``4.2`` and later use :term:`backup cursors 
    <backup cursor>` instead of :opsmgr:`head databases </reference/glossary/#std-term-head-database>` 
    for backups.
 

source/index.txt

@@ -71,7 +71,7 @@ Backup Workflow
 
 Backups rely upon the :manual:`MongoDB version compatibility</reference/command/setFeatureCompatibilityVersion>`
 of your database. This Feature Compatibility Version ranges from the
-current version to one version earlier. For MongoDB 4.4, the FCV can be
+current version to one version earlier. For MongoDB 4.4, the |fcv| can be
 ``4.2`` or ``4.4``.
 
 .. include:: /includes/backup/wtchk-process-overview-main-om.rst

source/reference/faq/faq-backup.txt

@@ -56,7 +56,7 @@ Does Backup Work with All Types of Deployments?
 
 - For MongoDB 4.2 and later, see
   :ref:`Backup Considerations for Databases <4.2-backup-considerations>`.
-- For any MongoDB with |fcv| of ``4.0`` and earlier databases, Backup
+- For any MongoDB with |fcv| ``4.0`` and earlier databases, Backup
   doesn't support standalone deployments. Backup has full
   support for replica sets and sharded clusters.
 
@@ -87,7 +87,7 @@ Will Backup Impact My Production Databases?
 .. note::
 
    This answer applies only to databases running MongoDB with |fcv|
-   of ``4.0`` and earlier
+   ``4.0`` and earlier
 
 The Backup feature typically has minimal impact on production MongoDB
 deployments. This impact performs similar to that of adding a new
@@ -152,7 +152,7 @@ Legacy Backup Agent
 Backup capability has been moved to the {+mdbagent+} with Backup
 activated. This replaces the individual Backup Agent. This information
 covers issues unique to the legacy Backup Agent. All of this
-information applies to MongoDB databases running |fcv| of ``4.0`` or
+information applies to MongoDB databases running |fcv| ``4.0`` or
 earlier.
 
 Where Should I Run The Backup Agent?
@@ -258,8 +258,7 @@ How Does |mms| Provide Point-in-Time Restores?
 
 .. important::
 
-   |onprem| 4.2.13 and later supports this feature with |fcv| of
-   ``4.2`` or later.
+   |onprem| 4.2.13 and later supports this feature with |fcv| ``4.2`` or later.
 
 When you trigger the restore, |mms| creates a link to this snapshot.
 Once clicked, |mms| retrieves chunks from the Snapshot Store and
@@ -372,7 +371,7 @@ What Conditions Require a Resync?
 
 .. important::
 
-   This feature is incompatible with MongoDB 4.2 with |fcv| of ``4.2``.
+   This feature is incompatible with MongoDB 4.2 with |fcv| ``4.2``.
 
 If the Backup Agent's :term:`tailing cursor <tailable cursor>` cannot
 keep up with your deployment's :manual:`oplog </reference/glossary/#std-term-oplog>`, then you must

source/tutorial/enable-backup.txt

@@ -34,7 +34,7 @@ Replica Set Requirements
 A Replica Set must:
 
 - Be monitored by |mms|.
-- Run MongoDB Enterprise with an |fcv| of 4.2 or later.
+- Run MongoDB Enterprise with |fcv| 4.2 or later.
 - Have an active :manual:`primary </reference/glossary/#std-term-primary>` node.
 - Have one node with :manual:`WiredTiger </core/wiredtiger>` set as its
   :ref:`storage engine <considerations-backup-storage-engine>`. 
@@ -45,7 +45,7 @@ Sharded Cluster Requirements
 A Sharded Cluster must:
 
 - Be monitored by |mms|.
-- Run MongoDB Enterprise with an |fcv| of 4.2 or later on all nodes
+- Run MongoDB Enterprise with |fcv| 4.2 or later on all nodes
   including the config server. 
 - Have an active :manual:`primary
   </reference/glossary/#std-term-primary>` node of each shard and the

source/tutorial/nav/restore-overview.txt

@@ -94,7 +94,7 @@ To perform automated restores:
      :manual:`setFeatureCompatibilityVersion </reference/command/setFeatureCompatibilityVersion>`.
 
 - Review the following compatibility matrix for the supported source cluster
-  |fcv| of each MongoDB version. The MongoDB version of each host in
+  each MongoDB version. The MongoDB version of each host in
   the target cluster *must* support the |fcv| of the snapshot of the
   source cluster.