anchor.diff:  
   > You can deploy applications on OKD.
   
  -Considering that we use distinct branches to keep content for product versions
  -separated, global use of `{product-version}` across all branches is probably
  -less useful, but it is available if you come across a requirement for it. Just consider
  -how it will render across any branches that the content appears in.
  -
  -If it makes more sense in context to refer to the major version of the product
  -instead of a specific minor version (for example, if comparing how something in
  -OpenShift Container Platform 4 differs from OpenShift Container Platform 3),
  -just use the major version number. Do not prepend with a `v`, as in `v3` or `v4`.
  -
  -Do not use markup in headings.
  -
  -*Do not use internal company server names in command or example output*. See
  -suggested host name examples
  -https://docs.openshift.com/container-platform/3.11/install/example_inventories.html#multi-masters-single-etcd-using-native-ha[here].
  +Considering that we use distinct branches to keep content for product versions separated, global use of `{product-version}` across all branches is probably less useful, but it is available if you come across a requirement for it. Just consider how it will render across any branches that the content appears in.
  +
  +If it makes more sense in context to refer to the major version of the product instead of a specific minor version (for example, if comparing how something in OpenShift Container Platform 4 differs from OpenShift Container Platform 3), just use the major version number. Do not prepend with a `v`, as in `v3` or `v4`.
  +
  +*Do not use internal company server names in command or example output*. See suggested host name examples https://docs.openshift.com/container-platform/3.11/install/example_inventories.html#multi-masters-single-etcd-using-native-ha[here].
   
   
   == Links, hyperlinks, and cross references
  
positive.code: 
  Do not use "Overview" as a heading.
  
  === Discrete headings
  
  If you have a section heading that you do not want to appear in the TOC
  (like if you think that some section is not worth showing up or if there are already
  too many nested levels), you can use a discrete (or floating) heading:
  
  http://asciidoctor.org/docs/user-manual/#discrete-or-floating-section-titles
  
  A discrete heading also will not get a section number in the Customer Portal
  build of the doc. Previously, we would use plain bold mark-up around a heading
  like this, but discrete headings also allow you to ignore section nesting rules
  (like jumping from a `==` section level to a `====` level if you wanted for some
  style reason).
  
  To use a discrete heading, just add `[discrete]` to the line before your unique
  ID. For example:
  
  ----
  [discrete]
  
negative.code: 
  An object reference is when you are referring to the actual instance of an API object, where the object name is important.
  
  When referring to actual instances of API objects, use link:https://en.wikipedia.org/wiki/Camel_case#Variations_and_synonyms[PascalCase] and mark it up as monospace in backticks (````).
  
  [NOTE]
  ====
  Do not use backticks or other markup in headings.
  ====
  
  Be sure to match the proper object type (or `kind` in Kubernetes terms); for example, do not add an "s" to make it plural. *Only follow this guidance if you are explicitly referring to the API object (for example, when editing an object in the CLI or viewing an object in the web console).*
  
  For example:
  
  