DOCSP-15698 identify and correct codeblock indentation

source/core/index-sparse.txt

@@ -125,7 +125,7 @@ The collection has a sparse index on the field ``score``:
 
 .. code-block:: javascript
 
-    db.scores.createIndex( { score: 1 } , { sparse: true } )
+   db.scores.createIndex( { score: 1 } , { sparse: true } )
 
 Then, the following query on the ``scores`` collection uses the sparse
 index to return the documents that have the ``score`` field less than
@@ -160,7 +160,7 @@ The collection has a sparse index on the field ``score``:
 
 .. code-block:: javascript
 
-    db.scores.createIndex( { score: 1 } , { sparse: true } )
+   db.scores.createIndex( { score: 1 } , { sparse: true } )
 
 Because the document for the userid ``"newbie"`` does not contain the
 ``score`` field, the sparse index does not contain an entry for that
@@ -217,7 +217,7 @@ the following operation:
 
 .. code-block:: javascript
 
-    db.scores.createIndex( { score: 1 } , { sparse: true, unique: true } )
+   db.scores.createIndex( { score: 1 } , { sparse: true, unique: true } )
 
 This index *would permit* the insertion of documents that had unique
 values for the ``score`` field *or* did not include a ``score`` field.

source/core/query-optimization.txt

@@ -110,7 +110,7 @@ For example, a collection ``inventory`` has the following index on the
 
 .. code-block:: javascript
 
-  db.inventory.createIndex( { type: 1, item: 1 } )
+   db.inventory.createIndex( { type: 1, item: 1 } )
 
 This index will cover the following operation which queries on the
 ``type`` and ``item`` fields and returns only the ``item`` field:

source/includes/example-push-each.rst

@@ -4,7 +4,7 @@ equals ``joe``:
 
 .. code-block:: javascript
 
-  db.students.update(
-     { name: "joe" },
-     { $push: { scores: { $each: [ 90, 92, 85 ] } } }
-  )
+   db.students.update(
+      { name: "joe" },
+      { $push: { scores: { $each: [ 90, 92, 85 ] } } }
+   )

source/includes/output-upgrade-check.rst

@@ -47,7 +47,7 @@ Warning Output
 
 .. code-block:: none
 
-    Warning: upgradeCheck only supports V1 indexes. Skipping index: <indexSpec>
+   Warning: upgradeCheck only supports V1 indexes. Skipping index: <indexSpec>
 
 To resolve, remove the invalid index and recreate the index omitting
 the version specification, or reindex the collection. Reindex operation

source/reference/command/collStats.txt

@@ -123,7 +123,7 @@ The following operation runs the :dbcommand:`collStats` command on the
 
 .. code-block:: javascript
 
-  db.runCommand( { collStats : "restaurants", scale: 1024 } )
+   db.runCommand( { collStats : "restaurants", scale: 1024 } )
 
 The following document provides a representation of the
 :dbcommand:`collStats` output. Depending on the configuration of your

source/reference/command/currentOp.txt

@@ -165,14 +165,14 @@ database ``db1`` that have been running longer than 3 seconds:
 
 .. code-block:: javascript
 
-  db.adminCommand(
-     {
-       currentOp: true,
-       "active" : true,
-       "secs_running" : { "$gt" : 3 },
-       "ns" : /^db1\./
-     }
-  )
+   db.adminCommand(
+      {
+        currentOp: true,
+        "active" : true,
+        "secs_running" : { "$gt" : 3 },
+        "ns" : /^db1\./
+      }
+   )
 
 .. _currentOp-cmd-index-creation:
 

source/reference/command/dataSize.txt

@@ -102,7 +102,7 @@ and the upper bound of the key to be examined being ``{field: 100}``.
 
 .. code-block:: javascript
 
-  db.runCommand({ dataSize: "database.collection", keyPattern: { field: 1 }, min: { field: 10 }, max: { field: 100 } })
+   db.runCommand({ dataSize: "database.collection", keyPattern: { field: 1 }, min: { field: 10 }, max: { field: 100 } })
 
 This will return a document that contains the size of all matching
 documents. Replace ``database.collection`` value with database

source/reference/command/findAndModify.txt

@@ -460,11 +460,11 @@ following form:
 
 .. code-block:: javascript
 
-  db.people.findAndModify( {
-     query: { name: "Tom", state: "active", rating: { $gt: 10 } },
-     sort: { rating: 1 },
-     update: { $inc: { score: 1 } }
-  } );
+   db.people.findAndModify( {
+      query: { name: "Tom", state: "active", rating: { $gt: 10 } },
+      sort: { rating: 1 },
+      update: { $inc: { score: 1 } }
+   } );
 
 However, the :method:`~db.collection.findAndModify()` shell helper
 method returns only the unmodified document, or if ``new`` is
@@ -489,15 +489,15 @@ document or, if no matching document exists, create a new document:
 
 .. code-block:: javascript
 
-  db.runCommand(
-                 {
-                   findAndModify: "people",
-                   query: { name: "Gus", state: "active", rating: 100 },
-                   sort: { rating: 1 },
-                   update: { $inc: { score: 1 } },
-                   upsert: true
-                 }
-               )
+   db.runCommand(
+                  {
+                    findAndModify: "people",
+                    query: { name: "Gus", state: "active", rating: 100 },
+                    sort: { rating: 1 },
+                    update: { $inc: { score: 1 } },
+                    upsert: true
+                  }
+                )
 
 If the command finds a matching document, the command performs an update.
 

source/reference/command/removeShard.txt

@@ -25,7 +25,7 @@ against the ``admin`` database:
 
 .. code-block:: javascript
 
-    db.adminCommand( { removeShard : <shardToRemove> } )
+   db.adminCommand( { removeShard : <shardToRemove> } )
 
 Behavior
 --------

source/reference/command/usersInfo.txt

@@ -236,7 +236,7 @@ that resembles the following:
 
 .. code-block:: javascript
 
-    db.runCommand( { usersInfo: 1 } )
+   db.runCommand( { usersInfo: 1 } )
 
 When viewing all users, you can specify the ``showCredentials`` option
 but not the ``showPrivileges`` or the

source/reference/command/validate.txt

@@ -104,7 +104,7 @@ Examples
 
   .. code-block:: javascript
 
-    db.runCommand( { validate: "myCollection", full: true } )
+     db.runCommand( { validate: "myCollection", full: true } )
 
 .. _validate-output:
 

source/reference/installation-ubuntu-community-troubleshooting.txt

@@ -79,7 +79,7 @@ by running the following command in the terminal:
 
 .. code-block:: text
 
-  sudo apt-key list
+   sudo apt-key list
 
 The output should include an entry that resembles the following:
 

source/reference/method/db.collection.bulkWrite.txt

@@ -400,16 +400,16 @@ five operations.
 
 .. code-block:: javascript
 
-  db.collection.bulkWrite(
-     [
-        { insertOne : <document> },
-        { updateOne : <document> },
-        { updateMany : <document> },
-        { replaceOne : <document> },
-        { deleteOne : <document> },
-        { deleteMany : <document> }
-     ]
-  )
+   db.collection.bulkWrite(
+      [
+         { insertOne : <document> },
+         { updateOne : <document> },
+         { updateMany : <document> },
+         { replaceOne : <document> },
+         { deleteOne : <document> },
+         { deleteMany : <document> }
+      ]
+   )
 
 In the default ``ordered : true`` state, each operation will 
 be executed in order, from the first operation ``insertOne`` 
@@ -424,17 +424,17 @@ The following code represents an unordered
 
 .. code-block:: javascript
 
-  db.collection.bulkWrite(
-     [
-        { insertOne : <document> },
-        { updateOne : <document> },
-        { updateMany : <document> },
-        { replaceOne : <document> },
-        { deleteOne : <document> },
-        { deleteMany : <document> }
-     ],
-     { ordered : false }
-  )
+   db.collection.bulkWrite(
+      [
+         { insertOne : <document> },
+         { updateOne : <document> },
+         { updateMany : <document> },
+         { replaceOne : <document> },
+         { deleteOne : <document> },
+         { deleteMany : <document> }
+      ],
+      { ordered : false }
+   )
 
 With ``ordered : false``, the results of the operation may vary. For example, 
 the ``deleteOne`` or ``deleteMany`` may remove more or fewer documents 

source/reference/method/db.currentOp.txt

@@ -202,13 +202,13 @@ database ``db1`` that have been running longer than 3 seconds:
 
 .. code-block:: javascript
 
-  db.currentOp(
-     {
-       "active" : true,
-       "secs_running" : { "$gt" : 3 },
-       "ns" : /^db1\./
-     }
-  )
+   db.currentOp(
+      {
+        "active" : true,
+        "secs_running" : { "$gt" : 3 },
+        "ns" : /^db1\./
+      }
+   )
 
 .. _currentOp-index-creation:
 

source/reference/method/isInteractive.txt

@@ -59,7 +59,7 @@ Running a Javascript File inside the ``mongo`` Shell
 
    .. code-block:: javascript
 
-       let loadStatus = load("testExample.js");  //You may need to specify the path to the file
+      let loadStatus = load("testExample.js");  //You may need to specify the path to the file
 
    The method returns in the :binary:`~bin.mongo` shell:
 

source/reference/operator/aggregation/dateFromString.txt

@@ -207,16 +207,16 @@ to a date object:
 
 .. code-block:: javascript
 
-  db.logmessages.aggregate( [ {
-     $project: {
-        date: {
-           $dateFromString: {
-              dateString: '$date',
-              timezone: 'America/New_York'
-           }
-        }
-     }
-  } ] )
+   db.logmessages.aggregate( [ {
+      $project: {
+         date: {
+            $dateFromString: {
+               dateString: '$date',
+               timezone: 'America/New_York'
+            }
+         }
+      }
+   } ] )
 
 The above aggregation returns the following documents and converts each ``date`` field
 to the Eastern Time Zone:
@@ -234,16 +234,16 @@ hard coded argument. For example:
 
 .. code-block:: javascript
 
-  db.logmessages.aggregate( [ {
-     $project: {
-        date: {
-           $dateFromString: {
-              dateString: '$date',
-              timezone: '$timezone'
-           }
-        }
-     }
-  } ] )
+   db.logmessages.aggregate( [ {
+      $project: {
+         date: {
+            $dateFromString: {
+               dateString: '$date',
+               timezone: '$timezone'
+            }
+         }
+      }
+   } ] )
 
 The above aggregation returns the following documents and converts each ``date`` field
 to their respective UTC representations.

source/reference/operator/aggregation/match.txt

@@ -126,10 +126,10 @@ the documents:
 
 .. code-block:: javascript
 
-  db.articles.aggregate( [
-    { $match: { $or: [ { score: { $gt: 70, $lt: 90 } }, { views: { $gte: 1000 } } ] } },
-    { $group: { _id: null, count: { $sum: 1 } } }
-  ] );
+   db.articles.aggregate( [
+     { $match: { $or: [ { score: { $gt: 70, $lt: 90 } }, { views: { $gte: 1000 } } ] } },
+     { $group: { _id: null, count: { $sum: 1 } } }
+   ] );
 
 In the aggregation pipeline, :pipeline:`$match` selects the documents
 where either the ``score`` is greater than ``70`` and less than ``90``

source/reference/operator/aggregation/range.txt

@@ -104,13 +104,13 @@ the stopping points for each trip.
 
 .. code-block:: javascript
 
-  db.distances.aggregate([{
-      $project: {
-          _id: 0,
-          city: 1,
-          "Rest stops": { $range: [ 0, "$distance", 25 ] }
-      }
-  }])
+   db.distances.aggregate([{
+       $project: {
+           _id: 0,
+           city: 1,
+           "Rest stops": { $range: [ 0, "$distance", 25 ] }
+       }
+   }])
 
 The operation returns the following:
 

source/reference/operator/aggregation/redact.txt

@@ -200,20 +200,20 @@ fields contained in a document/embedded document at level ``5``, include a
 
 .. code-block:: javascript
 
-  db.accounts.aggregate(
-    [
-      { $match: { status: "A" } },
-      {
-        $redact: {
-          $cond: {
-            if: { $eq: [ "$level", 5 ] },
-            then: "$$PRUNE",
-            else: "$$DESCEND"
-          }
-        }
-      }
-    ]
-  );
+   db.accounts.aggregate(
+     [
+       { $match: { status: "A" } },
+       {
+         $redact: {
+           $cond: {
+             if: { $eq: [ "$level", 5 ] },
+             then: "$$PRUNE",
+             else: "$$DESCEND"
+           }
+         }
+       }
+     ]
+   );
 
 The :pipeline:`$redact` stage evaluates the ``level`` field to
 determine access. If the ``level`` field equals ``5``, then exclude all