@@ -345,13 +345,13 @@ Supported networks :

       <td class="no-wrap"><strong>container</strong>:&lt;name|id&gt;</td>

       <td>

         Use the network stack of another container, specified via

-        its *name* or *id*.

+        its <i>name</i> or <i>id</i>.

       </td>

     </tr>

     <tr>

       <td class="no-wrap"><strong>NETWORK</strong></td>

       <td>

-        Connects the container to a user created network (using `docker network create` command)

+        Connects the container to a user created network (using <code>docker network create</code> command)

       </td>

     </tr>

   </tbody>

@@ -624,15 +624,15 @@ but the volume for `/bar` will not. Volumes inherited via `--volumes-from` will

 with the same logic -- if the original volume was specified with a name it will **not** be removed.

 ## Security configuration

-    --security-opt="label=user:USER"   : Set the label user for the container

-    --security-opt="label=role:ROLE"   : Set the label role for the container

-    --security-opt="label=type:TYPE"   : Set the label type for the container

-    --security-opt="label=level:LEVEL" : Set the label level for the container

-    --security-opt="label=disable"     : Turn off label confinement for the container

-    --security-opt="apparmor=PROFILE"  : Set the apparmor profile to be applied to the container

-    --security-opt="no-new-privileges" : Disable container processes from gaining new privileges

-    --security-opt="seccomp=unconfined": Turn off seccomp confinement for the container

-    --security-opt="seccomp=profile.json: White listed syscalls seccomp Json file to be used as a seccomp filter

+    --security-opt="label=user:USER"     : Set the label user for the container

+    --security-opt="label=role:ROLE"     : Set the label role for the container

+    --security-opt="label=type:TYPE"     : Set the label type for the container

+    --security-opt="label=level:LEVEL"   : Set the label level for the container

+    --security-opt="label=disable"       : Turn off label confinement for the container

+    --security-opt="apparmor=PROFILE"    : Set the apparmor profile to be applied to the container

+    --security-opt="no-new-privileges"   : Disable container processes from gaining new privileges

+    --security-opt="seccomp=unconfined"  : Turn off seccomp confinement for the container

+    --security-opt="seccomp=profile.json": White listed syscalls seccomp Json file to be used as a seccomp filter

 You can override the default labeling scheme for each container by specifying

@@ -737,7 +737,7 @@ We have four ways to set user memory usage:

       <td class="no-wrap"><strong>memory=L&lt;inf, memory-swap=2*L</strong></td>

       <td>

         (specify memory without memory-swap) The container is not allowed to

-        use more than L bytes of memory, swap *plus* memory usage is double

+        use more than L bytes of memory, swap <i>plus</i> memory usage is double

         of that.

       </td>

     </tr>

@@ -747,7 +747,7 @@ We have four ways to set user memory usage:

       </td>

       <td>

         (specify both memory and memory-swap) The container is not allowed to

-        use more than L bytes of memory, swap *plus* memory usage is limited

+        use more than L bytes of memory, swap <i>plus</i> memory usage is limited

         by S.

       </td>

     </tr>