DOCSP-25406 Resolving Build Errors — WiredTiger journaling (#1897)

* DOCSP-25406 Resolve wiredTiger Journal Build Errors

* fix accidental typo

* resolve 3.6 release note errors + change out :docs: for :ref: links

* mystery typo?

* remove note for 4.2

* fix 5 that keeps changing to 1

* remove mention of storage.journal.enabled from monitoring.txt

* fix language to remove mention of journaling option in monitoring

* grammar fix

Author: ajhuh-mdb

source/administration/monitoring.txt

@@ -550,11 +550,15 @@ The Storage Node Watchdog monitors the following MongoDB directories to
 detect filesystem unresponsiveness:
 
 * The :option:`--dbpath <mongod --dbpath>` directory
-* The ``journal`` directory inside the :option:`--dbpath <mongod --dbpath>` directory if
-  :option:`journaling <mongod --journal>` is enabled
+* The ``journal`` directory inside the :option:`--dbpath <mongod --dbpath>` 
+  directory
 * The directory of :option:`--logpath <mongod --logpath>` file
 * The directory of :option:`--auditPath <mongod --auditPath>` file
 
+.. note::
+  
+  .. include:: /includes/journal-option-removed.rst
+
 By default, the Storage Node Watchdog is disabled. You can only enable
 the Storage Node Watchdog on a :binary:`~bin.mongod` at startup time by
 setting the :parameter:`watchdogPeriodSeconds` parameter to an integer

source/core/replica-set-members.txt

@@ -1,3 +1,5 @@
+.. _replica-set-members:
+
 ===================
 Replica Set Members
 ===================

source/core/storage-engines.txt

@@ -1,3 +1,5 @@
+.. _storage-engines:
+
 ===============
 Storage Engines
 ===============

source/includes/wiredtiger-node-nojournal.rst

@@ -1,4 +1,3 @@
-Starting in MongoDB 4.0, you cannot specify :option:`--nojournal
-<mongod --nojournal>` option or :setting:`storage.journal.enabled:
-false <storage.journal.enabled>` for replica set members that use the
+Starting in MongoDB 4.0, you cannot specify ``--nojournal`` option or 
+``storage.journal.enabled: false`` for replica set members that use the 
 WiredTiger storage engine.

source/release-notes/2.0.txt

@@ -31,10 +31,10 @@ for handling CSV input/output. This may break existing import/export
 workflows that relied on the previous behavior. For more information see
 :issue:`SERVER-1097`.
 
-:doc:`Journaling </core/journaling/>` is **enabled by default** in 2.0 for 64-bit builds.
+:ref:`<journaling-internals>` is **enabled by default** in 2.0 for 64-bit builds.
 If you still prefer to run without journaling, start :binary:`~bin.mongod`
-with the :option:`--nojournal <mongod --nojournal>` run-time option.
-Otherwise, MongoDB creates journal files during startup. The first time you start :binary:`~bin.mongod` with
+with the ``--nojournal`` run-time option. Otherwise, MongoDB creates journal 
+files during startup. The first time you start :binary:`~bin.mongod` with
 journaling, you will see a delay as :binary:`~bin.mongod` creates new files.
 In addition, you may see reduced write throughput.
 

source/release-notes/3.6-compatibility.txt

@@ -437,14 +437,14 @@ MongoDB 3.6 deprecates master-slave replication.
 ``--nojournal`` Option with WiredTiger
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-In version 3.6, the :option:`--nojournal <mongod --nojournal>` option is deprecated for
-:doc:`replica set members </core/replica-set-members/>`
-using the :doc:`WiredTiger storage engine </core/wiredtiger/>`.
-
-:doc:`Replica set members </core/replica-set-members/>` which use the
-WiredTiger :doc:`storage engine </core/storage-engines/>` should not
-use the :option:`--nojournal <mongod --nojournal>` option. For more information about
-journaling, see :doc:`/tutorial/manage-journaling`.
+In version 3.6, the ``--nojournal`` option is deprecated for
+:ref:`<replica-set-members>` using the 
+:ref:`WiredTiger storage engine <storage-wiredtiger>`.
+
+:ref:`Replica set members <replica-set-members>` that use the
+WiredTiger :ref:`storage engine <storage-engines>` should not
+use the ``--nojournal`` option. For more information about
+journaling, see :ref:`<manage-journaling>`.
 
 .. _aggregate-compatibility:
 

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

@@ -212,7 +212,7 @@ If the member uses ``zstd`` for journal compression only,
       </reference/configuration-options>` to prepare to restart as a
       standalone:
 
-      - Set :setting:`storage.journal.enabled` to ``false``.
+      - Set ``storage.journal.enabled`` to ``false``.
 
       - Comment out the :ref:`replication <replication-options>` settings
         for your deployment.
@@ -246,8 +246,7 @@ If the member uses ``zstd`` for journal compression only,
       - If you are using command-line options instead of a
         configuration file, 
 
-        - Include the :option:`--nojournal <mongod
-          --nojournal>` option
+        - Include the ``--nojournal`` option
 
         - Remove any :ref:`replication command-line options
           <cli-mongod-replica-set>` (such as :option:`--replSet
@@ -272,7 +271,7 @@ If the member uses ``zstd`` for journal compression only,
    #. Update the configuration file to prepare to restart as a replica set
       member with the new journal compressor:
 
-      - Remove the :setting:`storage.journal.enabled` setting.
+      - Remove the ``storage.journal.enabled`` setting.
 
       - Uncomment the :ref:`replication <replication-options>`
         settings for your deployment.
@@ -310,7 +309,7 @@ If the member uses ``zstd`` for journal compression only,
       - If you are using command-line options instead of a configuration
         file:
 
-        - Remove the :option:`--nojournal <mongod --nojournal>` option.
+        - Remove the ``--nojournal`` option.
 
         - Remove the :option:`--wiredTigerJournalCompressor <mongod
           --wiredTigerJournalCompressor>` command-line option to use

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

@@ -184,7 +184,7 @@ If the member only uses ``zstd`` for journal compression only,
       </reference/configuration-options>` to prepare to restart as a
       standalone:
 
-      - Set :setting:`storage.journal.enabled` to ``false``.
+      - Set ``storage.journal.enabled`` to ``false``.
 
       - Set parameter :parameter:`skipShardingConfigurationChecks` to true.
 
@@ -230,8 +230,7 @@ If the member only uses ``zstd`` for journal compression only,
       - If you are using command-line options instead of a
         configuration file:
 
-        - Include the :option:`--nojournal <mongod --nojournal>`
-          option.
+        - Include the ``--nojournal`` option.
 
         - Set parameter :parameter:`skipShardingConfigurationChecks` to true.
 
@@ -263,7 +262,7 @@ If the member only uses ``zstd`` for journal compression only,
 
    #. Update the configuration file to prepare to restart with the new journal compressor:
 
-      - Remove the :setting:`storage.journal.enabled` setting.
+      - Remove the ``storage.journal.enabled`` setting.
 
       - Remove the :parameter:`skipShardingConfigurationChecks` parameter setting.
 
@@ -310,7 +309,7 @@ If the member only uses ``zstd`` for journal compression only,
       - If you are using command-line options instead of a configuration
         file:
 
-        - Remove the :option:`--nojournal <mongod --nojournal>` option.
+        - Remove the ``--nojournal`` option.
 
         - Remove the :parameter:`skipShardingConfigurationChecks` parameter setting.