[BACKPORT] DOCSP-36255: Build error fix (#6267)

* DOCSP-36255: Build error fix

* Docsp 36255 -- Build error cleanup (#6246)

* DOCSP-36255: Remove link to 2.6 release notes

* DOCSP-36255: missing link build error fix

* DOCSP-36255: Build error fix

* DOCSP-36255: Build error fix

* DOCSP-36255: Build error fix

* DOCSP-36255-7.2
build fixes

Author: sarah-olson-mongodb

source/core/replica-set-write-concern.txt

@@ -110,10 +110,6 @@ operation. Refer to the documentation for the write operation for
 instructions on write concern support and syntax. For complete 
 documentation on write concern, see :ref:`write-concern`.
 
-.. seealso::
-
-   :ref:`write-methods-incompatibility`
-
 .. _repl-set-modify-default-write-concern:
 
 Modify Default Write Concern

source/includes/fact-ssl-tlsCAFile-tlsUseSystemCA.rst

@@ -1,7 +1,7 @@
 When starting a :binary:`~bin.mongod` instance with 
 :ref:`TLS/SSL enabled <configure-mongod-mongos-for-tls-ssl>`, you must 
 specify a value for the :option:`--tlsCAFile <mongod --tlsCAFile>` flag, the 
-:setting:`tls.CAFile` configuration option, or the :parameter:`tlsUseSystemCA` 
+:setting:`net.tls.CAFile` configuration option, or the :parameter:`tlsUseSystemCA` 
 parameter. 
 
 ``--tlsCAFile``, ``tls.CAFile``, and ``tlsUseSystemCA`` are all mutually 

source/release-notes/3.0-compatibility.txt

@@ -327,7 +327,7 @@ If you do not currently have any users *or* you are using
 ``authSchema`` version 1, the query will not return any result.
 
 If your ``authSchema`` version is less
-than ``3`` or the query does not return any results, see :doc:`/release-notes/2.6-upgrade-authorization` to
+than ``3`` or the query does not return any results, see the 2.6 Upgrade Authorization to
 upgrade the ``authSchema`` version before upgrading to MongoDB 3.0.
 
 After upgrading MongoDB to 3.0 from 2.6, to use the new ``SCRAM-SHA-1``

source/release-notes/3.0-upgrade.txt

@@ -49,9 +49,7 @@ version earlier than MongoDB 2.4.
 If your existing MongoDB deployment is already running with
 authentication and authorization, your user data model ``authSchema``
 must be at least version 3. To verify the version of your existing
-``authSchema``, see :ref:`legacy-auth-model-removed`. To upgrade your
-``authSchema`` version, see
-:ref:`Upgrade Authorization Data <2.6-upgrade-authorization-model>` for details.
+``authSchema``, see :ref:`legacy-auth-model-removed`. 
 
 Preparedness
 ~~~~~~~~~~~~

source/release-notes/4.0.txt

@@ -1537,11 +1537,11 @@ Network Layer Improvements
 
   - :parameter:`connPoolMaxInUseConnsPerHost`
 
-  - :parameter:`connPoolMaxShardedInUseConnsPerHost`
+  - ``connPoolMaxShardedInUseConnsPerHost``
 
   - :parameter:`globalConnPoolIdleTimeoutMinutes`
 
-  - :parameter:`shardedConnPoolIdleTimeoutMinutes`
+  - ``shardedConnPoolIdleTimeoutMinutes``
 
 Configuration Options
 ~~~~~~~~~~~~~~~~~~~~~

source/release-notes/4.2.txt

@@ -1786,11 +1786,11 @@ the following output changes:
          <metrics.repl.network.notPrimaryUnacknowledgedWrites>`
 
    * - :serverstatus:`metrics.repl`
-     - Added new :serverstatus:`metrics.repl.stateTransition` metrics:
+     - Added new ``metrics.repl.stepDown`` metrics:
 
-       - :serverstatus:`metrics.repl.stateTransition.userOperationsKilled`
+       - ``metrics.repl.stepDown.userOperationsKilled``
 
-       - :serverstatus:`metrics.repl.stateTransition.userOperationsRunning`
+       - ``metrics.repl.stepDown.userOperationsRunning``
 
    * - :serverstatus:`transactions`