update manpage list parsing

Author: juanvallejo

docs/man/man1/oadm-diagnostics.1

@@ -38,16 +38,22 @@ you will receive an error if they are not found. For example:
 .nf
 oadm diagnostics \-\-master\-config=/etc/origin/master/master\-config.yaml
 
+If master/node config files are not found and the \-\-host flag is not
+
 .fi
 .RE
-.IP \n+[step]
 
-\item If master/node config files are not found and the \-\-host flag is not
+.PP
 present, host diagnostics are skipped.
-\item If the client has cluster\-admin access, this access enables cluster
+    If the client has cluster\-admin access, this access enables cluster
+
+.PP
 diagnostics to run which regular users cannot.
-\item If a client config file is not found, client and cluster diagnostics
+    If a client config file is not found, client and cluster diagnostics
+
+.PP
 are skipped.
+
 .PP
 Diagnostics may be individually run by passing diagnostic name as arguments.
 The available diagnostic names are:

docs/man/man1/oc-adm-diagnostics.1

@@ -38,16 +38,22 @@ you will receive an error if they are not found. For example:
 .nf
 oc adm diagnostics \-\-master\-config=/etc/origin/master/master\-config.yaml
 
+If master/node config files are not found and the \-\-host flag is not
+
 .fi
 .RE
-.IP \n+[step]
 
-\item If master/node config files are not found and the \-\-host flag is not
+.PP
 present, host diagnostics are skipped.
-\item If the client has cluster\-admin access, this access enables cluster
+    If the client has cluster\-admin access, this access enables cluster
+
+.PP
 diagnostics to run which regular users cannot.
-\item If a client config file is not found, client and cluster diagnostics
+    If a client config file is not found, client and cluster diagnostics
+
+.PP
 are skipped.
+
 .PP
 Diagnostics may be individually run by passing diagnostic name as arguments.
 The available diagnostic names are:

docs/man/man1/oc-create-clusterresourcequota.1

@@ -22,15 +22,26 @@ and scaling up new ones. Use 'oc rollback' to rollback to any previous deploymen
 
 .PP
 There are several deployment strategies defined:
-.IP \n+[step]
 
-\item Rolling (default) \- scales up the new deployment in stages, gradually reducing the number
+.PP
+.RS
+
+.nf
+Rolling (default) \- scales up the new deployment in stages, gradually reducing the number
+
+.fi
+.RE
+
+.PP
 of old deployments. If one of the new deployed pods never becomes "ready", the new deployment
-will be rolled back (scaled down to zero). Use when your application can tolerate two versions
-of code running at the same time (many web applications, scalable databases)
-\item Recreate \- scales the old deployment down to zero, then scales the new deployment up to full.
+  will be rolled back (scaled down to zero). Use when your application can tolerate two versions
+  of code running at the same time (many web applications, scalable databases)
+    Recreate \- scales the old deployment down to zero, then scales the new deployment up to full.
+
+.PP
 Use when your application cannot tolerate two versions of code running at the same time
-\item Custom \- run your own deployment process inside a Docker container using your own scripts.
+    Custom \- run your own deployment process inside a Docker container using your own scripts.
+
 .PP
 If a deployment fails, you may opt to retry it (if the error was transient). Some deployments may
 never successfully complete \- in which case you can use the '\-\-latest' flag to force a redeployment.

docs/man/man1/oc-deploy.1

@@ -29,19 +29,30 @@ you cannot change a pod's volumes once it has been created.
 
 .PP
 Volume types include:
-.IP \n+[step]
 
-\item emptydir (empty directory) \fIdefault\fP
+.PP
+.RS
+
+.nf
+emptydir (empty directory) *default*
+
 A directory allocated when the pod is created on a local host, is removed when
 the pod is deleted and is not copied across servers
-\item hostdir (host directory)
+hostdir (host directory)
+
 A directory with specific path on any host (requires elevated privileges)
-\item persistentvolumeclaim or pvc (persistent volume claim)
+persistentvolumeclaim or pvc (persistent volume claim)
+
 Link the volume directory in the container to a persistent volume claim you have
 allocated by name \- a persistent volume claim is a request to allocate storage.
 Note that if your claim hasn't been bound, your pods will not start.
-\item secret (mounted secret)
+secret (mounted secret)
+
 Secret volumes mount a named secret to the provided directory.
+
+.fi
+.RE
+
 .PP
 For descriptions on other volume types, see 
 \[la]https://docs.openshift.com\[ra]