Added 2 example playbooks for Issue IBM-Blockchain#414

Signed-off-by: rthatcher <robert.thatcher@uk.ibm.com>
sstone1 · Oct 30, 2020 · 44530c2 · 44530c2
1 parent 2a33b25
commit 44530c2
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/docs/source/tasks/enable-fabricv2-capability.rst b/docs/source/tasks/enable-fabricv2-capability.rst
@@ -2,8 +2,8 @@
 .. SPDX-License-Identifier: Apache-2.0
 ..
 
-Enable Hyperledger Fabric v2 Capability
-=======================================
+Enable Hyperledger Fabric v2.x capabilities
+===========================================
 
 Fabric v2 capability is distinct from Fabric v2.x binaries, and the most common scenario will be where the binaries on a network have been upgraded to v2.x, leaving the Capability of the channels at V1.x.  This playbook example can be used to upgrade firstly the system channel, then an array of named application channels.
 

diff --git a/docs/source/tasks/haca.rst b/docs/source/tasks/haca.rst
@@ -2,7 +2,7 @@
 .. SPDX-License-Identifier: Apache-2.0
 ..
 
-Creating a highly available Certificate Authority
+Creating a highly available certificate authority
 =================================================
 
 The default certificate authority in IBM Blockchain Platform is a single replica with an integrated SQLite database, however it is possible to configure the certificate authority to have an external PostgresSQL database and have multiple replicas of the certificate authority.