[enterprise-3.7]Added OCP 3.7 Release Notes

_topic_map.yml

@@ -40,8 +40,8 @@ Topics:
 - Name: Overview
   File: index
   Distros: openshift-enterprise,openshift-dedicated
-- Name: OpenShift Container Platform 3.6 Release Notes
-  File: ocp_3_6_release_notes
+- Name: OpenShift Container Platform 3.7 Release Notes
+  File: ocp_3_7_release_notes
   Distros: openshift-enterprise
 - Name: Latest Product Updates
   File: osd_latest_product_updates

admin_guide/managing_networking.adoc

@@ -30,7 +30,7 @@ plugin], you can manage the separate pod overlay networks for projects using
 the administrator CLI.
 ifdef::openshift-enterprise,openshift-origin[]
 See the xref:../install_config/configuring_sdn.adoc#install-config-configuring-sdn[Configuring the SDN] section
-for plugin configuration steps, if necessary.
+for plug-in configuration steps, if necessary.
 endif::openshift-enterprise,openshift-origin[]
 
 [[joining-project-networks]]
@@ -1023,7 +1023,7 @@ the case with unicast.
 
 The *ovs-subnet* and *ovs-multitenant* plugins have their own legacy models of network
 isolation, and don't support Kubernetes `NetworkPolicy`. However, `NetworkPolicy` support
-is available by using the *ovs-networkpolicy* plugin.
+is available by using the *ovs-networkpolicy* plug-in.
 
 In a cluster
 xref:../install_config/configuring_sdn.adoc#install-config-configuring-sdn[configured
@@ -1260,4 +1260,4 @@ services to include this site in their HSTS preload lists. For example, sites
 such as Google can construct a list of sites that have `preload` set. Browsers
 can then use these lists to determine which sites to only talk to over HTTPS,
 even before they have interacted with the site. Without `preload` set, they need
-to have talked to the site over HTTPS to get the header.
+to have talked to the site over HTTPS to get the header.

architecture/service_catalog/index.adoc

@@ -77,7 +77,7 @@ known as _unbinding_. Part of the deletion process includes deleting the secret
 that references the service binding being deleted.
 
 Once all the service bindings are removed, the service instance may be deleted.
-Deleting the service instance is known as _deprovisioning_. 
+Deleting the service instance is known as _deprovisioning_.
 
 [[service-catalog-concepts-terminology]]
 == Concepts and Terminology

install_config/install/advanced_install.adoc

@@ -2171,7 +2171,7 @@ Technology Preview feature.
 The installer uses modularized playbooks allowing administrators to install
 specific components as needed. By breaking up the roles and playbooks, there is
 better targeting of ad hoc administration tasks. This results in an increased
-level of control during installations and results in time savings. 
+level of control during installations and results in time savings.
 
 [NOTE]
 ====

release_notes/index.adoc

@@ -7,7 +7,7 @@
 :experimental:
 
 ifdef::openshift-enterprise[]
-The following release notes for {product-title} 3.6 summarize all new features,
+The following release notes for {product-title} 3.7 summarize all new features,
 major corrections from the previous version, and any known bugs upon general
 availability.
 endif::[]
@@ -16,8 +16,8 @@ ifdef::openshift-dedicated[]
 The following release notes for {product-title} summarize key features upon
 general availability. OpenShift Dedicated uses the same code base as OpenShift
 Container Platform 3; for more detailed technical notes, see the
-link:https://docs.openshift.com/container-platform/3.6/release_notes/ocp_3_6_release_notes.html[OpenShift
-Container Platform 3.6 Release Notes].
+link:https://docs.openshift.com/container-platform/3.7/release_notes/ocp_3_7_release_notes.html[OpenShift
+Container Platform 3.7 Release Notes].
 endif::[]
 
 [[release-versioning-policy]]
@@ -29,13 +29,13 @@ beta APIs (which may occasionally be changed in a non-backwards compatible
 manner).
 
 The {product-title} version must match between master and node hosts, excluding
-temporary mismatches during cluster upgrades. For example, in a 3.6 cluster, all
-masters must be 3.6 and all nodes must be 3.6. However, {product-title} will
-continue to support older `oc` clients against newer servers. For example, a 3.6
-`oc` will work against 3.3, 3.4, 3.5, and 3.6 servers.
+temporary mismatches during cluster upgrades. For example, in a 3.7 cluster, all
+masters must be 3.7 and all nodes must be 3.7. However, {product-title} will
+continue to support older `oc` clients against newer servers. For example, a 3.4
+`oc` will work against 3.3, 3.4, and 3.5 servers.
 
 Changes of APIs for non-security related reasons will involve, at minimum, two
-minor releases (3.1 to 3.2 to 3.3, for example) to allow older `oc` to update.
+minor releases (3.4 to 3.5 to 3.6, for example) to allow older `oc` to update.
 Using new capabilities may require newer `oc`. A 3.2 server may have additional
 capabilities that a 3.1 `oc` cannot use and a 3.2 `oc` may have additional
 capabilities that are not supported by a 3.1 server.

release_notes/ocp_3_6_release_notes.adoc

@@ -30,7 +30,7 @@ security, privacy, compliance, and governance requirements.
 == About This Release
 
 Red Hat {product-title} version 3.6
-(link:https://access.redhat.com/errata/RHBA-2017:1716[RHBA-2017:1716]) is now
+(link:https://access.redhat.com/errata/RHEA-2017:1716[RHEA-2017:1716]) is now
 available. This release is based on
 link:https://github.com/openshift/origin/releases/tag/v3.6.0-rc.0[OpenShift
 Origin 3.6]. New features, changes, bug fixes, and known issues that pertain to