Add major version # usage to contrib

Author: adellape

contributing_to_docs/doc_guidelines.adoc

@@ -79,7 +79,7 @@ instead.
 === Unique IDs
 
 The content in this repo is used to build docs that publish to multiple
-locations (e.g., docs.openshift.com, docs.openshift.org, and the Red Hat
+locations (e.g., docs.openshift.com, docs.okd.io, and the Red Hat
 Customer Portal). While heading IDs will be created automatically from any
 section titles (e.g., "Managing Authorization Policies" would generate an ID of
 `managing-authorization-policies`, which would act as an anchor reference), we
@@ -119,7 +119,7 @@ ID. For example:
 == Managing Authorization Policies
 ----
 
-== Product Name & Version Attributes
+== Product Name & Version
 
 When possible, generalize references to the product name and/or version using
 the `{product-title}` and/or `{product-version}` attributes. These attributes
@@ -140,16 +140,16 @@ possible values for `{product-title}` and `{product-version}`.
 |Distro |`{product-title}` |`{product-version}`
 
 |`openshift-origin`
-|OpenShift Origin
-|Latest
+|OKD
+|1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 3.6, 3.7, 3.9, 3.10, 3.11, Latest
 
 |`openshift-enterprise`
-|OpenShift Enterprise
-|3.1, 3.0
+|OpenShift Container Platform
+|3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.9, 3.10, 3.11
 
 |`openshift-dedicated`
 |OpenShift Dedicated
-|3.1, 3.0
+|Latest
 
 |`openshift-online`
 |OpenShift Online
@@ -168,19 +168,29 @@ statement] is not necessary. For example, if you were viewing a build for the
 `openshift-enterprise` distro (for any of the distro-defined branches), this
 would render as:
 
-"You can deploy applications on OpenShift Enterprise."
+"You can deploy applications on OpenShift Container Platform."
 
 And for the `openshift-origin` distro:
 
-"You can deploy applications on OpenShift Origin."
+"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 need 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
+OCP 4 differs from OCP 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].
+
+
 == Links, Hyperlinks, and Cross References
 Links can be used to cross-reference internal topics, or send customers to external information resources for further reading.