[FAB-9178] Fix erroneous indentation in three lists

Three doc files:

 - msp.rst
 - policies.rst
 - understand_fabcar_network.rst

have incorrect spacing/indentation in lists which generate build
warnings, so fix all three at once.

Change-Id: I0d951e4cbd4ade8b36da01d7d9e258fa772e220f
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>

Author: rpjday

docs/source/msp.rst

@@ -192,11 +192,12 @@ needs to be set appropriately. Here is an example:
 As shown above, the ``NodeOUs.Enable`` is set to ``true``, this enables the identify classification.
 Then, client (peer) identifiers are defined by setting the following properties
 for the ``NodeOUs.ClientOUIdentifier`` (``NodeOUs.PeerOUIdentifier``) key:
- a. ``OrganizationalUnitIdentifier``: Set this to the value that matches the OU that
- the x509 certificate of a client (peer) should contain.
- b. ``Certificate``: Set this to the CA or intermediate CA under which client (peer) identities
- should be validated. The field is relative to the MSP root folder. It can be empty, meaning
- that the identity's x509 certificate can be validated under any CA defined in the MSP configuration.
+
+a. ``OrganizationalUnitIdentifier``: Set this to the value that matches the OU that
+   the x509 certificate of a client (peer) should contain.
+b. ``Certificate``: Set this to the CA or intermediate CA under which client (peer) identities
+   should be validated. The field is relative to the MSP root folder. It can be empty, meaning
+   that the identity's x509 certificate can be validated under any CA defined in the MSP configuration.
 
 When the classification is enabled, MSP administrators need
 to be clients of that MSP, meaning that their x509 certificates need to carry

docs/source/policies.rst

@@ -315,11 +315,12 @@ message defined as follows:
 The ``msp_identifier`` is set to the ID of the MSP (as defined by the
 ``MSPConfig`` proto in the channel configuration for an org) which will
 evaluate the signature, and the ``Role`` is set to either ``MEMBER``,
-``ADMIN``, ``CLIENT`` or ``PEER``. In particular
+``ADMIN``, ``CLIENT`` or ``PEER``. In particular:
 
 1. ``MEMBER`` matches any certificate issued by the MSP.
 2. ``ADMIN`` matches certificates enumerated as admin in the MSP definition.
-3. ``CLIENT`` (``PEER``) matches certificates that carry the client (peer) Organizational unit
+3. ``CLIENT`` (``PEER``) matches certificates that carry the client (peer) Organizational unit.
+
 (see `MSP Documentation <http://hyperledger-fabric.readthedocs.io/en/latest/msp.html>`_)
 
 Constructing an ImplicitMetaPolicy

docs/source/understand_fabcar_network.rst

@@ -33,9 +33,10 @@ For detailed information on these components and what they do, refer to
 
 These components are bootstrapped by the ``./startFabric.sh`` script, which
 also:
-          * creates a channel and joins the peer to the channel
-          * installs the ``fabcar`` smart contract onto the peer's file system and instantiates it on the channel (instantiate starts a container)
-          * calls the ``initLedger`` function to populate the channel ledger with 10 unique cars
+
+* creates a channel and joins the peer to the channel
+* installs the ``fabcar`` smart contract onto the peer's file system and instantiates it on the channel (instantiate starts a container)
+* calls the ``initLedger`` function to populate the channel ledger with 10 unique cars
 
 These operations would typically be done by an organizational or peer admin.
 The script uses the CLI to execute these commands, however there is support in