anchor.diff:  
   |Code blocks
   
  -a|Use the following syntax for the `oc` command:
  +a|
  +....
  +Use the following syntax for the `oc` command:
   
   ----
   $ oc <action> <object_type> <object_name_or_id>
   ----
  -
  -a|Use the following syntax for the `oc` command:
  -
  -----
  -$ oc <action> <object_type> <object_name_or_id>
  -----
  +....
  +
  +a|
  +> Use the following syntax for the `oc` command:
  +>
  +> ----
  +> $ oc <action> <object_type> <object_name_or_id>
  +> ----
   
   a|Use backticks for all non-GUI "system items", including:
   
   * Inline commands, operations, literal values, variables, parameters, settings,
   flags, environment variables, user input
   * System term/item, user names, unique or example names for individual API
  -objects/resources (e.g., a Pod named "mypod"), daemon, service, or software
  +objects/resources (e.g., a Pod named `mypod`), daemon, service, or software
   package
   * RPM packages
   * File names or directory paths
   
  -a|$$`oc get`$$
  -
  -$$Set the `upgrade` variable to `true`.$$
  -
  -$$Use the `--amend` flag.$$
  -
  -$$Answer by typing `Yes` or `No` when prompted.$$
  -
  -$$`user_name`$$
  -
  -$$`service_name`$$
  -
  -$$`package_name`$$
  -
  -$$`filename`$$
  -
  -a|Use the `oc get services` command to get a list of services that are currently defined.
  +a|
  +....
  +`oc get`
  +
  +Set the `upgrade` variable to `true`.
   
   Use the `--amend` flag.
   
  -Set the `upgrade` variable to `true`.
  -
   Answer by typing `Yes` or `No` when prompted.
   
  -`cluster-admin` user
  -
  -`firewalld` service
  -
  -`rubygems` RPM package
  -
  -The `express.conf` configuration file is located in the `/usr/share` directory.
  +`user_name`
  +
  +`service_name`
  +
  +`package_name`
  +
  +`filename`
  +....
  +
  +a|
  +> Use the `oc get services` command to get a list of services that are currently defined.
  +>
  +> &nbsp;
  +>
  +> Use the `--amend` flag.
  +>
  +> &nbsp;
  +>
  +> Set the `upgrade` variable to `true`.
  +>
  +> &nbsp;
  +>
  +> Answer by typing `Yes` or `No` when prompted.
  +>
  +> &nbsp;
  +>
  +> `cluster-admin` user
  +>
  +> &nbsp;
  +>
  +> `firewalld` service
  +>
  +> &nbsp;
  +>
  +> `rubygems` RPM package
  +>
  +> &nbsp;
  +>
  +> The `express.conf` configuration file is located in the `/usr/share` directory.
   
   |System or software variable to be replaced by the user
  -a|$$`<project>`$$
  -
  -$$`<deployment>`$$
  -
  -a|Use the following command to roll back a Deployment, specifying the Deployment name:
  -
  -`oc rollback <deployment>`
  +a|
  +....
  +`<project>`
  +
  +`<deployment>`
  +....
  +
  +a|
  +> Use the following command to roll back a Deployment, specifying the Deployment name:
  +>
  +> `oc rollback <deployment>`
   
   |Use single asterisks for web console / GUI items (menus, buttons, page titles, etc.).
  -Use two characters to form the arrow in a series of menu items, $$->$$.
  -
  -a|Choose $$*Cluster Console*$$ from the list.
  -
  -Navigate to the $$*Operators* -> *Catalog Sources*$$ page.
  -
  -Click $$*Create Subscription*$$.
  -
  -a|Choose *Cluster Console* from the list.
  +Use two characters to form the arrow in a series of menu items (`$$->$$`).
  +
  +a|
  +....
  +Choose *Cluster Console* from the list.
   
   Navigate to the *Operators* -> *Catalog Sources* page.
   
   Click *Create Subscription*.
  +....
  +
  +a|
  +> Choose *Cluster Console* from the list.
  +>
  +> &nbsp;
  +>
  +> Navigate to the *Operators* -> *Catalog Sources* page.
  +>
  +> &nbsp;
  +>
  +> Click *Create Subscription*.
   
   |Use underscores to emphasize the first appearance of a new term.
   
  -|An $$_Operator_$$ is a method of packaging, deploying, and managing a Kubernetes application.
  -
  -|An _Operator_ is a method of packaging, deploying, and managing a Kubernetes application.
  +a|
  +....
  +An _Operator_ is a method of packaging, deploying,
  +and managing a Kubernetes application.
  +....
  +
  +a|
  +> An _Operator_ is a method of packaging, deploying, and managing a Kubernetes application.
   
   |Use of single asterisks for general emphasis is allowed but should only be used
   very sparingly. Let the writing, instead of font usage, create the emphasis
   wherever possible.
   
  -a|Do $$*not*$$ delete the file.
  -
  -a|Do *not* delete the file.
  +a|
  +....
  +Do *not* delete the file.
  +....
  +
  +a|
  +> Do *not* delete the file.
   
   |Footnotes
   
  -|A footnote is created with the footnote macro. If you plan to reference a footnote more than once, use the ID footnoteref macro. The customer portal does not support spaces in the footnoteref. For example, "dynamic PV" should be "dynamicPV".
  +|A footnote is created with the footnote macro. If you plan to reference a footnote more than once, use the ID footnoteref macro. The Customer Portal does not support spaces in the footnoteref. For example, "dynamic PV" should be "dynamicPV".
   
   |See link:http://asciidoctor.org/docs/user-manual/#user-footnotes[Footnotes] for the footnote and footnoteref syntax.
   
  
positive.code: ---- for code blocks
  ....
  
  
  === Code blocks
  Code blocks are used to show examples of command screen outputs, or
  configuration files. When using command blocks, always use the actual values for
  any items that a user would normally replace. Code blocks should represent
  exactly what a customer would see on their screen. If you must expand or
  provide information on what some of the contents of a screen output or
  configuration file represent, then use callouts to provide that information.
  
  Follow these general guidelines when using code blocks:
  
  * Do NOT use any markup in code blocks; code blocks generally do not accept any markup.
  
  * For all code blocks, you must include an empty line above a code block.
  +
  Acceptable:
  +
  
negative.code: 
  
  == Links, hyperlinks, and cross references
  Links can be used to cross-reference internal assemblies or send readers to external information resources for further reading.
  
  In OpenShift docs:
  
  