[FAB-10699] Change other upgrade text to 1.2

Change name of doc and make text refer to 1.2 Change-Id: I163e8bebc476434909bc05029f48044e0ff816c3 Signed-off-by: joe-alewine <Joe.Alewine@ibm.com>
jaes-park · Jun 19, 2018 · 0bc3781 · 0bc3781
1 parent 3436f45
commit 0bc3781
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 7 deletions.
diff --git a/docs/source/ops_guide.rst b/docs/source/ops_guide.rst
@@ -4,7 +4,7 @@ Operations Guides
 .. toctree::
    :maxdepth: 1
 
-   upgrade_to_one_point_one
+   upgrade_to_newest_version
    config_update
    msp
    configtx

diff --git a/docs/source/upgrade_to_one_point_one.rst → docs/source/upgrade_to_newest_version.rst b/docs/source/upgrade_to_one_point_one.rst → docs/source/upgrade_to_newest_version.rst
@@ -1,17 +1,19 @@
-Upgrading from v1.0.x
-=====================
+Upgrading to the Newest Version of Fabric
+=========================================
 
-At a high level, upgrading a Fabric network to v1.1 can be performed by following these
+At a high level, upgrading a Fabric network to v1.2 can be performed by following these
 steps:
 
- * Upgrade binaries for orderers, peers, and fabric-ca. These upgrades may be done in parallel.
+ * Upgrade the binaries for the ordering service, the Fabric CA, and the peers.
+   These upgrades may be done in parallel.
  * Upgrade client SDKs.
- * Enable v1.1 channel capability requirements.
+ * Enable the v1.2 capability.
  * (Optional) Upgrade the Kafka cluster.
 
 To help understand this process, we've created the :doc:`upgrading_your_network_tutorial`
 tutorial that will take you through most of the major upgrade steps, including
-upgrading peers, orderers, as well as enabling capability requirements.
+upgrading peers, orderers, as well as the capability. We've included both a
+script as well as the individual steps to achieve these upgrades.
 
 Because our tutorial leverages the :doc:`build_network` (BYFN) sample, it has
 certain limitations (it does not use Fabric CA, for example). Therefore we have