merge: DOCS-841

Author: Sam Kleinman

source/reference/command/collMod.txt

@@ -15,11 +15,11 @@ collMod
 
    .. code-block:: javascript
 
-      db.runCommand( {"collMod" : [collection] , "[flag]" : [value]" } )
+      db.runCommand( {"collMod" : <collection> , "<flag>" : <value> } )
 
-   In this command substitute ``[collection]`` with the name of the
-   collection, and ``[flag]`` and ``[value]`` with the flag and value
-   you want to set.
+   In this command substitute ``<collection>`` with the name of a
+   collection in the current database, and ``<flag>`` and ``<value>``
+   with the flag and value you want to set.
 
    .. index:: document; space allocation
    .. index:: usePowerOf2Sizes
@@ -38,11 +38,29 @@ collMod
       will be inserting and deleting large numbers of documents to
       ensure that MongoDB will effectively use space on disk.
 
-      .. note::
-         .. versionchanged:: 2.2.1
-            If you're using :collflag:`usePowerOf2Sizes`, ensure
-            you use at least 2.2.1 to avoid the issue described in
-            :issue:`SERVER-7238`.
+      .. example::
+
+         To enable :collflag:`usePowerOf2Sizes` on the collection
+         named ``sensor_readings``, use the following operation:
+
+         .. code-block:: javascript
+
+            db.runCommand({collMod: "sensor_readings", usePowerOf2Sizes:true })
+
+         To disable :collflag:`usePowerOf2Sizes` on the collection
+         ``products``, use the following operation:
+
+         .. code-block:: javascript
+
+            db.runCommand( { collMod: "products", "usePowerOf2Sizes": false })
+
+
+      .. warning::
+         .. versionchanged:: 2.2.1 
+            :collflag:`usePowerOf2Sizes` now
+            supports documents larger than 8 megabytes. If you enable
+            :collflag:`usePowerOf2Sizes` you **must** use at least
+            version 2.2.1.
 
          :collflag:`usePowerOf2Sizes` only affects subsequent
          allocations cased by document insertion or record relocation
@@ -51,6 +69,6 @@ collMod
 
          .. Commenting out the following after DOCS-717, it does take
             a lock but its to cover a very small metadata change.
-            
+
             This command obtains a write lock on the affected database
             and will block other operations until it has completed.