[UG] Fix formatting typos

Fixes noticed formatting typos.

Change-Id: I72007861e3536ce5445f6cc449a09028cb020855

userdocs/fuel-user-guide/cli/cli_config_openstack.rst

@@ -23,28 +23,28 @@ defined.
 
 #. Log in to the Fuel Master node.
 #. Edit the ``.yaml`` file with the configuration options of the services that
-   you want to change. 
+   you want to change.
 
    **Example:**
 
-    .. code-block:: yaml
+   .. code-block:: yaml
 
-         configuration:
-           nova_config:
-             DEFAULT/debug:
-               value: True
-             DEFAULT/amqp_durable_queues:
-               value: False
-           keystone_config:
-             DEFAULT/default_publisher_id:
-               ensure: absent
-             DEFAULT/crypt_strength:
-               value: 6000
+        configuration:
+          nova_config:
+            DEFAULT/debug:
+              value: True
+            DEFAULT/amqp_durable_queues:
+              value: False
+          keystone_config:
+            DEFAULT/default_publisher_id:
+              ensure: absent
+            DEFAULT/crypt_strength:
+              value: 6000
 
 #. Upload the ``.yaml`` file:
 
    * To upload the changes for an OpenStack environment:
- 
+
      .. code-block:: console
 
          fuel openstack-config --env <env_id> --upload file.yaml
@@ -53,7 +53,7 @@ defined.
 
      .. code-block:: console
 
-        fuel openstack-config --env <env_id> --role compute \ 
+        fuel openstack-config --env <env_id> --role compute \
         --upload <file.yaml>
 
    * To upload the changes for selected nodes:

userdocs/fuel-user-guide/maintain-environment/custom-graph.rst

@@ -62,9 +62,9 @@ information about the graph. It has no impact on the business logic.
 
       fuel2 graph list --env env_id
 
-  where ``env_id`` is the ID of the environment.
+   where ``env_id`` is the ID of the environment.
 
-To upload a graph:
+**To upload a graph:**
 
 #. Log in to the Fuel master node.
 #. Run the following command:
@@ -75,16 +75,16 @@ To upload a graph:
       fuel2 graph upload --release release_id [--type graph_type] --file tasks.yaml
       fuel2 graph upload --plugin plugin_id [--type graph_type] --file tasks.yaml
 
-  where ``--type`` is an optional parameter. The ``default`` graph type with
-  confirmation should be used if no type is defined.
+   where ``--type`` is an optional parameter. The ``default`` graph type with
+   confirmation should be used if no type is defined.
 
-Thw graphs downloaded with the keys ``--all`` and ``--plugins`` are the
+The graphs downloaded with the keys ``--all`` and ``--plugins`` are the
 result of other graphs merge performed by Nailgun and are not supposed to be
 edited and uploaded back.
 In most cases because they will completely override further changes made in
 source graphs.
 
-To download a graph:
+**To download a graph:**
 
 #. Log in to the Fuel master node.
 #. Run the following command:
@@ -99,7 +99,7 @@ To download a graph:
      where ``--type`` is an optional parameter. The command downloads the
      ``default``if no type is defined.
 
-To execute a graph:
+**To execute a graph:**
 
 #. Log in to the Fuel master node.
 #. Run the following command:

userdocs/fuel-user-guide/maintain-environment/deployment-history.rst

@@ -12,19 +12,19 @@ To get the information on a deployment task:
 #. Log in to the Fuel master node.
 #. Find the ID of the deployment task:
 
-  .. code-block:: console
-  
-     fuel task
-     fuel2 task list
+   .. code-block:: console
+
+      fuel task
+      fuel2 task list
 
 #. Get the information on the deployment task:
 
-  .. code-block:: console
+   .. code-block:: console
 
-     fuel deployment-tasks --task-id <task-id> --statuses ready, pending --nodes 1,2
-     fuel2 task history show <task-id> --nodes 3 --statuses error skipped
+      fuel deployment-tasks --task-id <task-id> --statuses ready, pending --nodes 1,2
+      fuel2 task history show <task-id> --nodes 3 --statuses error skipped
 
-  where <task-id> is the ID of the deployment task.
+   where <task-id> is the ID of the deployment task.
 
 .. warning:: The commands ``fuel task`` and ``fuel2 task list`` show
              the Nailgun tasks; for example, provisioning, deployment,