diff --git a/doc/source/configuration/index.rst b/doc/source/configuration/index.rst
index 438e3d88..db72b559 100644
--- a/doc/source/configuration/index.rst
+++ b/doc/source/configuration/index.rst
@@ -15,14 +15,14 @@ Driver configuration
 In order to use the compute-hyperv Nova driver, the following configuration
 option will have to be set in the ``nova.conf`` file:
 
-  .. code-block:: ini
+.. code-block:: ini
 
     [DEFAULT]
     compute_driver = compute_hyperv.driver.HyperVDriver
 
 And for Hyper-V Clusters, the following:
 
-  .. code-block:: ini
+.. code-block:: ini
 
     [DEFAULT]
     compute_driver = compute_hyperv.cluster.driver.HyperVClusterDriver
@@ -54,14 +54,14 @@ Nova instance files location
 By default, the OpenStack Hyper-V installer will configure ``nova-compute`` to
 use the following path as the ``instances_path``:
 
-  .. code-block:: ini
+.. code-block:: ini
 
     [DEFAULT]
     instances_path = C:\OpenStack\Instances
 
 ``instances_path`` can be set to an SMB share, mounted or unmounted:
 
-  .. code-block:: ini
+.. code-block:: ini
 
     [DEFAULT]
     # in this case, X is a persistently mounted SMB share.
@@ -72,7 +72,7 @@ use the following path as the ``instances_path``:
 
 Alternatively, CSVs can be used:
 
-  .. code-block:: ini
+.. code-block:: ini
 
     [DEFAULT]
     instances_path = C:\ClusterStorage\Volume1\OpenStack\Instances
@@ -137,7 +137,7 @@ For live migrating virtual machines to hosts with different CPU features the
 following configuration option must be set in the compute node's ``nova.conf``
 file:
 
-  .. code-block:: ini
+.. code-block:: ini
 
     [hyperv]
     limit_cpu_features = True
diff --git a/doc/source/install/next-steps.rst b/doc/source/install/next-steps.rst
index 3206b4a7..54fd4d93 100644
--- a/doc/source/install/next-steps.rst
+++ b/doc/source/install/next-steps.rst
@@ -60,13 +60,13 @@ Neutron Server meets the following requirements:
 * ``networking-hyperv`` installed. To check if ``networking-hyperv`` is
   installed, run the following:
 
-  .. code-block:: bash
+.. code-block:: bash
 
     pip freeze | grep networking-hyperv
 
   If there is no output, it can be installed by running the command:
 
-  .. code-block:: bash
+.. code-block:: bash
 
     pip install networking-hyperv==VERSION
 
@@ -79,7 +79,7 @@ Neutron Server meets the following requirements:
   driver. The configuration option can be found in
   ``/etc/neutron/plugins/ml2/ml2_conf.ini``:
 
-  .. code-block:: ini
+.. code-block:: ini
 
     [ml2]
     mechanism_drivers = openvswitch,hyperv
diff --git a/doc/source/troubleshooting/index.rst b/doc/source/troubleshooting/index.rst
index 031eaa92..086671f1 100644
--- a/doc/source/troubleshooting/index.rst
+++ b/doc/source/troubleshooting/index.rst
@@ -66,18 +66,18 @@ How to restart a service on Hyper-V
 
 Restarting a service on OpenStack can easily be done through Powershell:
 
-  .. code-block:: powershell
+.. code-block:: powershell
 
      Restart-Service service-name
 
 or through cmd:
 
-  .. code-block:: bat
+.. code-block:: bat
 
      net stop service_name && net start service_name
 
 For example, the following command will restart the iSCSI initiator service:
 
-  .. code-block:: powershell
+.. code-block:: powershell
 
      Restart-Service msiscsi