Fix none-ascii char in doc

There exist some none-ascii chars in doc, which may cause trouble
in displaying.

Change-Id: Ic7ae90b6edb14ecad78b18e738c7e24f6466a500

doc/source/admin/ts-eql-volume-size.rst

@@ -55,8 +55,8 @@ following example, the ID and size are
 Verify the volume size on the EQL array by using its command-line
 interface.
 
-The actual size (``VolReserve``) is 1.01 GB. The EQL Group Manager
+The actual size (``VolReserve``) is 1.01GB. The EQL Group Manager
-should also report a volume size of 1.01 GB:
+should also report a volume size of 1.01GB:
 
 .. code-block:: console
 
@@ -112,7 +112,7 @@ Create a new image from this volume:
 When you uploaded the volume in the previous step, the Image service
 reported the volume's size as ``1`` (GB). However, when using
 :command:`openstack image show` to show the image, the displayed size is
-1085276160 bytes, or roughly 1.01 GB:
+1085276160 bytes, or roughly 1.01 GB:
 
 +------------------+--------------------------------------+
 | Property         | Value                                |
@@ -139,7 +139,7 @@ reported the volume's size as ``1`` (GB). However, when using
 
 Create a new volume using the previous image (``image_id 3020a21d-ba37-4495
 -8899-07fc201161b9`` in this example) as
-the source. Set the target volume size to 1 GB; this is the size
+the source. Set the target volume size to 1GB; this is the size
 reported by the ``cinder`` tool when you uploaded the volume to the
 Image service:
 
@@ -156,9 +156,9 @@ Solution
 ~~~~~~~~
 
 To work around this problem, increase the target size of the new image
-to the next whole number. In the problem example, you created a 1 GB
+to the next whole number. In the problem example, you created a 1GB
 volume to be used as volume-backed image, so a new volume using this
-volume-backed image should use a size of 2 GB:
+volume-backed image should use a size of 2GB:
 
 .. code-block:: console
 

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

@@ -196,15 +196,15 @@ Examples of option configuration in the ``cinder.conf`` file.
 
      $ sudo mkdir /var/lib/cinder/datacore -p
 
-     $ sudo /bin/sh –c "> /var/lib/cinder/datacore/.chap"
+     $ sudo /bin/sh -c "> /var/lib/cinder/datacore/.chap"
 
      $ sudo chown cinder:cinder /var/lib/cinder/datacore
 
-     $ sudo chmod –v 750 /var/lib/cinder/datacore
+     $ sudo chmod -v 750 /var/lib/cinder/datacore
 
      $ sudo chown cinder:cinder /var/lib/cinder/datacore/.chap
 
-     $ sudo chmod –v 600 /var/lib/cinder/datacore/.chap
+     $ sudo chmod -v 600 /var/lib/cinder/datacore/.chap
 
   After setting **datacore_iscsi_chap_enabled** and
   **datacore_iscsi_chap_storage**, CHAP authentication will be enabled in

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

@@ -146,7 +146,7 @@ in the ``multipath.conf`` file:
         device {
             vendor "DATERA"
             product "IBLOCK"
-            getuid_callout "/lib/udev/scsi_id --whitelisted –
+            getuid_callout "/lib/udev/scsi_id --whitelisted --
             replace-whitespace --page=0x80 --device=/dev/%n"
             path_grouping_policy group_by_prio
             path_checker tur

doc/source/configuration/block-storage/drivers/hpe-3par-driver.rst

@@ -319,7 +319,7 @@ OpenStack software.
    .. note::
 
       To stop the Web Services API Server, use the :command:`stopwsapi` command. For
-      other options run the :command:`setwsapi –h` command.
+      other options run the :command:`setwsapi -h` command.
 
 #. If you are not using an existing CPG, create a CPG on the HPE 3PAR storage
    system to be used as the default location for creating volumes.

doc/source/configuration/block-storage/drivers/ibm-gpfs-volume-driver.rst

@@ -181,19 +181,19 @@ options supported by the GPFS volume driver.
    * - Metadata Item Name
      - Description
    * - fstype
-     - Specifies whether to create a file system or a swap area on the new volume. If fstype=swap is specified, the mkswap command is used to create a swap area. Otherwise the mkfs command is passed the specified file system type, for example ext3, ext4 or ntfs.
+     - Specifies whether to create a file system or a swap area on the new volume. If fstype=swap is specified, the mkswap command is used to create a swap area. Otherwise the mkfs command is passed the specified file system type, for example ext3, ext4 or ntfs.
    * - fslabel
-     - Sets the file system label for the file system specified by fstype option. This value is only used if fstype is specified.
+     - Sets the file system label for the file system specified by fstype option. This value is only used if fstype is specified.
    * - data_pool_name
      - Specifies the GPFS storage pool to which the volume is to be assigned. Note: The GPFS storage pool must already have been created.
    * - replicas
-     - Specifies how many copies of the volume file to create. Valid values are 1, 2, and, for Spectrum Scale V3.5.0.7 and later, 3. This value cannot be greater than the value of the MaxDataReplicasattribute of the file system.
+     - Specifies how many copies of the volume file to create. Valid values are 1, 2, and, for Spectrum Scale V3.5.0.7 and later, 3. This value cannot be greater than the value of the MaxDataReplicasattribute of the file system.
    * - dio
-     - Enables or disables the Direct I/O caching policy for the volume file. Valid values are yes and no.
+     - Enables or disables the Direct I/O caching policy for the volume file. Valid values are yes and no.
    * - write_affinity_depth
-     - Specifies the allocation policy to be used for the volume file. Note: This option only works if allow-write-affinity is set for the GPFS data pool.
+     - Specifies the allocation policy to be used for the volume file. Note: This option only works if allow-write-affinity is set for the GPFS data pool.
    * - block_group_factor
-     - Specifies how many blocks are laid out sequentially in the volume file to behave as a single large block. Note: This option only works if allow-write-affinity is set for the GPFS data pool.
+     - Specifies how many blocks are laid out sequentially in the volume file to behave as a single large block. Note: This option only works if allow-write-affinity is set for the GPFS data pool.
    * - write_affinity_failure_group
      - Specifies the range of nodes (in GPFS shared nothing architecture) where replicas of blocks in the volume file are to be written. See Spectrum Scale documentation for more details about this option.
 

doc/source/configuration/block-storage/volume-encryption.rst

@@ -126,7 +126,7 @@ left out, the default volume type, ``unencrypted``, is used.
 
       $ . admin-openrc.sh
 
-#. Create an unencrypted 1 GB test volume:
+#. Create an unencrypted 1GB test volume:
 
    .. code-block:: console
 
@@ -134,7 +134,7 @@ left out, the default volume type, ``unencrypted``, is used.
       $ openstack volume create --size 1 'unencrypted volume'
 
 
-#. Create an encrypted 1 GB test volume:
+#. Create an encrypted 1GB test volume:
 
    .. code-block:: console
 

doc/source/contributor/threading.rst

@@ -32,7 +32,7 @@ delays in the case that there is only a single green thread::
     ...
     greenthread.sleep(0)
 
-In current code, time.sleep(0）does the same thing as greenthread.sleep(0) if
+In current code, time.sleep(0) does the same thing as greenthread.sleep(0) if
 time module is patched through eventlet.monkey_patch(). To be explicit, we recommend
 contributors use ``greenthread.sleep()`` instead of ``time.sleep()``.