Fix some typos in docs

This is to fix the following typos in docs:
  modfied
  certficate
  transacton
  specfies
  Pasive
  prefferably
  depoying
  resered
  preferrable
  readiblity

Change-Id: I1a5c62654d2c6da3704113299a13b5a593a40d71

cinder/api/openstack/rest_api_version_history.rst

@@ -362,7 +362,7 @@ on several external factors below:
    nova side currently.
 
 Administrator can disable this ability by updating the
-``volume:extend_attached_volume`` policy rule.  Extend of a resered
+``volume:extend_attached_volume`` policy rule.  Extend of a reserved
 Volume is NOT allowed.
 
 3.43 (Maximum in Pike)

doc/source/configuration/block-storage/drivers/dell-emc-powermax-driver.rst

@@ -1615,7 +1615,7 @@ restarted for changes to take effect.
 
   ``u4p_failover_target`` key value pairs will need to be on the same
   line (separated by commas) in cinder.conf. They are displayed on
-  separated lines above for readiblity.
+  separated lines above for readability.
 
 .. note::
 
@@ -1744,7 +1744,7 @@ Configure the source and target arrays
 
       ``replication_device`` key value pairs will need to be on the same
       line (separated by commas) in cinder.conf. They are displayed on
-      separated lines above for readiblity.
+      separated lines above for readability.
 
    * ``target_device_id`` is a unique PowerMax array serial number of the
      target array. For full failover functionality, the source and target

doc/source/configuration/block-storage/drivers/dell-emc-unity-driver.rst

@@ -343,7 +343,8 @@ steps:
 #. Setup the Unity array certificate and import it to the Unity, see section
    `Storage system certificate` of `Security Configuration Guide <https://www.emc.com/collateral/TechnicalDocument/docu69321.pdf>`_.
 
-#. Import the CA certficate to the Cinder nodes on which the driver is running.
+#. Import the CA certificate to the Cinder nodes on which the driver is
+   running.
 
 #. Enable the changes on cinder nodes and restart the cinder services.
 

doc/source/configuration/block-storage/drivers/hp-msa-driver.rst

@@ -74,7 +74,7 @@ Configuring the array
        of an array user account with ``manage`` privileges.
      * ``driver_use_ssl`` should be set to ``true`` to enable use of the
        HTTPS protocol.
-     * ``hpmsa_iscsi_ips`` specfies the iSCSI IP addresses for the array
+     * ``hpmsa_iscsi_ips`` specifies the iSCSI IP addresses for the array
        if using the iSCSI transport protocol.
 
    In the examples below, two back ends are defined, one for pool A and one for

doc/source/configuration/block-storage/drivers/huawei-storage-driver.rst

@@ -508,7 +508,7 @@ of the Huawei volume driver.
      - All
    * - iscsi_default_target_ip
      - ``-``
-     - Remote transacton port IP.
+     - Remote transaction port IP.
      - All
 .. important::
 

doc/source/configuration/block-storage/drivers/lenovo-driver.rst

@@ -75,7 +75,7 @@ Configuring the array
         of an array user account with ``manage`` privileges.
       * ``driver_use_ssl`` should be set to ``true`` to enable use of the
         HTTPS protocol.
-      * ``lenovo_iscsi_ips`` specfies the iSCSI IP addresses for the array
+      * ``lenovo_iscsi_ips`` specifies the iSCSI IP addresses for the array
         if using the iSCSI transport protocol.
 
    In the examples below, two back ends are defined, one for pool A and one

doc/source/configuration/block-storage/drivers/seagate-driver.rst

@@ -77,7 +77,7 @@ Configuring the array
    * ``driver_use_ssl`` must be set to True to enable use of the HTTPS
      protocol.
 
-   * ``seagate_iscsi_ips`` specfies the iSCSI IP addresses
+   * ``seagate_iscsi_ips`` specifies the iSCSI IP addresses
      for the array if using the iSCSI transport protocol
 
    In the examples below, two back ends are defined, one for pool A and one for

doc/source/configuration/block-storage/drivers/windows-smb-volume-driver.rst

@@ -18,7 +18,7 @@ The main reasons to use the Windows SMB driver are:
 * suitable for a various range of deployment types and sizes
 
 The ``cinder-volume`` service as well as the required Python components will
-be installed directly onto designated Windows nodes (prefferably the ones
+be installed directly onto designated Windows nodes (preferably the ones
 exposing the shares).
 
 Common deployment scenarios
@@ -33,7 +33,7 @@ The SMB driver is designed to support a variety of scenarios, such as:
 By using SoFS shares, the virtual disk images are stored on Cluster Shared
 Volumes (``CSV``).
 
-A common practice involves depoying CSVs on top of SAN backed LUNs
+A common practice involves deploying CSVs on top of SAN backed LUNs
 (exposed to all the nodes of the cluster through iSCSI or Fibre Channel). In
 absence of a SAN, Storage Spaces/Storage Spaces Direct (``S2D``) may be used
 for the underlying storage.
@@ -84,8 +84,9 @@ Active-Active Cinder clustering is currently experimental and should not be
 used in production. This implies having multiple Cinder Volume services
 handling the same share simultaneously.
 
-On the other hand, Active-Pasive clustering can easily be achieved, configuring
+On the other hand, Active-Passive clustering can easily be achieved,
-the Cinder Volume service as clustered using Microsoft Failover Cluster.
+configuring the Cinder Volume service as clustered using Microsoft Failover
+Cluster.
 
 By using SoFS, you can provide high availability of the shares used by Cinder.
 This can be used in conjunction with the Nova Hyper-V cluster driver, which

doc/source/configuration/block-storage/policy-config-HOWTO.rst

@@ -19,7 +19,7 @@ Policy configuration HowTo
 
 You can use Cinder policies to control how your users and administrators
 interact with the Block Storage Service.  In this HowTo, we'll discuss the user
-model Cinder employs and how it can be modfied by adjusting policies.
+model Cinder employs and how it can be modified by adjusting policies.
 
 * Like most OpenStack services, Cinder uses the OpenStack ``oslo.policy``
   library as a base for its policy-related code.  For a discussion of "rules"