DOC-524 compact document use parameter directives

Author: kay-kim

source/reference/command/compact.txt

@@ -23,17 +23,20 @@ compact
 
    You may also specify the following options:
 
-   .. option:: force: true
+   :param force:
 
       .. versionchanged:: 2.2 :dbcommand:`compact` blocks activities only
         for its database.
 
-      To run on the primary node in a :term:`replica set`. Otherwise,
-      the :dbcommand:`compact` command returns an error when invoked on
-      a :term:`replica set` primary because the command blocks all
-      other activity.
+      The ``force`` specifies whether the :dbcommand:`compact` command
+      can run on the primary node in a :term:`replica set`. Set to
+      ``true`` to run the :dbcommand:`compact` command on the primary
+      node in a :term:`replica set`. Otherwise, the
+      :dbcommand:`compact` command returns an error when invoked on a
+      :term:`replica set` primary because the command blocks all other
+      activity.
 
-   .. option:: paddingFactor: <factor>
+   :param paddingFactor:
 
       .. versionadded:: v2.2
 
@@ -70,19 +73,19 @@ compact
 
          db.runCommand ( { compact: '<collection>', paddingFactor: 1.1 } )
 
-   .. option:: paddingBytes: <bytes>
+   :param paddingBytes:
 
       .. versionadded:: 2.2
 
-      To specify a padding as an absolute number of bytes. Specifying
-      ``paddingBytes`` can be useful if your documents start small but
-      then increase in size significantly. For example,if your
-      documents are initially 40 bytes long and you grow them by 1KB,
-      using ``paddingBytes: 1024`` might be reasonable since using
-      ``paddingFactor: 4.0`` would specify a record size of 160 bytes
-      (``4.0`` times the initial document size), which would only
-      provide a padding of 120 bytes (i.e. record size of 160 bytes
-      minus the document size).
+      The ``paddingBytes`` sets the padding as an absolute number
+      of bytes. Specifying ``paddingBytes`` can be useful if your
+      documents start small but then increase in size significantly.
+      For example,if your documents are initially 40 bytes long and you
+      grow them by 1KB, using ``paddingBytes: 1024`` might be
+      reasonable since using ``paddingFactor: 4.0`` would specify a
+      record size of 160 bytes (``4.0`` times the initial document
+      size), which would only provide a padding of 120 bytes (i.e.
+      record size of 160 bytes minus the document size).
 
       With the following command, you can use the ``paddingBytes``
       option of the :dbcommand:`compact` command to set the padding

themes/mongodb/static/mongodb-docs.css_t

@@ -110,7 +110,7 @@ div.sphinxsidebar h3 a {
 div.sphinxsidebar p {
     color: #333333;
     margin: 12px 0 5px 12px;
-    padding: 0 12p;
+    padding: 0 12px;
 }
 
 div.sphinxsidebar form {
@@ -305,6 +305,12 @@ table.docutils td {
     padding: 1px 8px 1em 5px;
 }
 
+table.docutils.field-list ul.first.last.simple>li {
+   padding-top: 1em; 
+}
+table.docutils.field-list ul.first.last.simple>li>p {
+    padding-top: 1em; 
+}
 /* for main page to knock out the bullets & padding for main columns */
 
 div#mongodb ul{