DOCS-4449: build fixes

- fixes the HTML build errors
- adds preallocDataFiles setting to ref (to fix error)

Author: schmalliso

config/sphinx.yaml

@@ -25,7 +25,6 @@ web-base:
   inherit: root-base
   excluded:
     - /meta/reference.txt
-    - /meta/use-cases.txt
     - /meta/administration.txt
     - /meta/manual.txt
   tags:

source/administration/security-checklist.txt

@@ -1,3 +1,5 @@
+.. _security-operations:
+
 ==================
 Security Checklist
 ==================

source/administration/security-user-role-management.txt

@@ -1,3 +1,5 @@
+.. _user-management-guide:
+
 ==================================
 User and Role Management Tutorials
 ==================================

source/applications/design-notes.txt

@@ -97,7 +97,7 @@ No Fully Generalized Transactions
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 MongoDB does not have :doc:`fully generalized transactions
-</tutorial/isolate-sequence-of-operations/>`. If you model your data
+</core/write-operations-atomicity>`. If you model your data
 using rich documents that closely resemble your application's
 objects, each logical object will be in one MongoDB document. MongoDB
 allows you to modify a document in a single atomic operation. These

source/faq/developers.txt

@@ -103,7 +103,7 @@ MongoDB *does* have support for atomic operations *within* a single
 document. Given the possibilities provided by nested documents, this
 feature provides support for a large number of use-cases.
 
-.. seealso:: The :doc:`/tutorial/isolate-sequence-of-operations` page.
+.. seealso:: The :doc:`/core/write-operations-atomicity` page.
 
 How do you aggregate data with MongoDB?
 ---------------------------------------

source/includes/fact-findAndModify-update-comparison.rst

@@ -31,5 +31,5 @@ When updating a document, |operation| and the
 
 When modifying a *single* document, both |operation| and the
 :method:`~db.collection.update()` method *atomically* update the
-document. See :doc:`/tutorial/isolate-sequence-of-operations` for more
+document. See :doc:`/core/write-operations-atomicity` for more
 details about interactions and order of operations of these methods.

source/includes/options-conf.yaml

@@ -1035,4 +1035,18 @@ inherit:
   name: chunkSize
   program: mongos
   file: options-mongos.yaml
+---
+program: conf
+name: storage.preallocDataFiles
+type: boolean
+default: true
+directive: setting
+replacement:
+  program: ":program:`mongod`"
+description: |
+  Enables or disables data file preallocation. 
+post: |
+  Do **not** disable data file preallocation in production systems. Only
+  use this option for testing and with small data sets where you
+  frequently drop databases.
 ...

source/includes/steps-backup-sharded-clusters-dumps.yaml

@@ -15,11 +15,8 @@ post: |
    For more information, see the
    :ref:`sharding-balancing-disable-temporarily` procedure.
 
-   .. warning::
+   .. warning:: If you do not stop the balancer, the backup could have duplicate data or omit data as :term:`chunks <chunk>` migrate while recording backups. 
 
-      If you do not stop the balancer, the backup could have duplicate
-      data or omit data as :term:`chunks <chunk>` migrate while recording
-      backups.
 ---
 title: Lock replica set members.
 stepnum: 2

source/reference/command/connectionStatus.txt

@@ -41,7 +41,7 @@ Output
    .. data:: connectionStatus.authinfo.authenticatedUserRoles[n].role
 
       The definition of the current roles associated with the current
-      authenticated users. See :doc:`/reference/build-in-roles` and
+      authenticated users. See :doc:`/reference/built-in-roles` and
       :doc:`/reference/privilege-actions` for more information.
 
    .. data:: connectionStatus.authinfo.authenticatedUserRoles[n].db

source/reference/database-references.txt

@@ -17,13 +17,13 @@ typically in different collections or databases.
 
 MongoDB applications use one of two methods for relating documents:
 
-#. :ref:`Manual references <document-references>` where you save the
+-  :ref:`Manual references <document-references>` where you save the
    ``_id`` field of one document in another document as a reference.
    Then your application can run a second query to return the related
    data. These references are simple and sufficient for most use
    cases.
 
-#. :ref:`DBRefs <dbref>` are references from one document to another
+-  :ref:`DBRefs <dbref-explanation>` are references from one document to another
    using the value of the first document's ``_id`` field, collection name,
    and, optionally, its database name. By including these names, DBRefs
    allow documents located in multiple collections to be more easily linked
@@ -99,9 +99,9 @@ references as needed.
 The only limitation of manual linking is that these references do not
 convey the database and collection names. If you have documents in a
 single collection that relate to documents in more than one
-collection, you may need to consider using :ref:`DBRefs <dbref>`.
+collection, you may need to consider using DBRefs.
 
-.. _dbref:
+.. _dbref-explanation:
 
 DBRefs
 ------