Replace curly quotes with straight quotes

Change-Id: I71efb56ed841272aeeafc06d7af0173ed14b8399

doc/source/admin/group_capabilities_and_extra_specs.rst

@@ -25,7 +25,7 @@ in share types. Users know what a group can do from group specs.
 The group specs is a exact match requirement in share group filter
 (such as ConsistentSnapshotFilter). When the ConsistentSnapshotFilter is enabled
 (it is enabled by default), the scheduler will only create a share group on
-a backend that reports capabilities that match the share group type’s
+a backend that reports capabilities that match the share group type's
 group-spec keys.
 
 Common Group Capabilities

doc/source/admin/hitachi_hnas_driver.rst

@@ -377,7 +377,7 @@ Additional Notes
   real used space in HNAS. Also, a snapshot does not initially take any space in
   HNAS, it only stores the difference between the share and the snapshot, so it
   grows when share data is changed.
-- Admins should manage the tenant’s quota (*manila quota-update*) to control
+- Admins should manage the tenant's quota (*manila quota-update*) to control
   the backend usage.
 - By default, CIFS snapshots are disabled when the share is mounted, since it
   uses tree-clone to create snapshots and does not guarantee point-in-time

doc/source/admin/shared-file-systems-network-plugins.rst

@@ -6,7 +6,7 @@ Network plug-ins
 
 The Shared File Systems service architecture defines an abstraction layer for
 network resource provisioning and allowing administrators to choose from a
-different options for how network resources are assigned to their projects’
+different options for how network resources are assigned to their projects'
 networked storage. There are a set of network plug-ins that provide a variety
 of integration approaches with the network services that are available with
 OpenStack.

doc/source/configuration/shared-file-systems/drivers/hitachi-hsp-driver.rst

@@ -208,5 +208,5 @@ Additional notes
 
 - Shares are thin provisioned. It is reported to manila only the
   real used space in HSP.
-- Administrators should manage the tenant’s quota (``manila quota-update``)
+- Administrators should manage the tenant's quota (``manila quota-update``)
   to control the backend usage.

doc/source/configuration/shared-file-systems/drivers/hpe-3par-share-driver.rst

@@ -297,7 +297,7 @@ without share networks. The configuration option
 ``driver_handles_share_servers``( ``True`` or ``False`` ) indicated whether
 share networks could be used. When set to ``False``, the HPE 3PAR driver
 behaved as described earlier for Kilo. When set to ``True``, the share
-network’s subnet, segmentation ID and IP address range were used to allocate
+network's subnet, segmentation ID and IP address range were used to allocate
 an FSIP on the HPE 3PAR. There is a limit of four FSIPs per VFS. For clients
 to communicate with shares via this FSIP, the client must have access to the
 external network using the subnet and segmentation ID of the share network.
@@ -584,8 +584,8 @@ Implementation characteristics
    driver uses one File Store for multiple shares. In this case, the size of
    the File Store limit is set to the cumulative limit of its Manila share
    sizes. This can allow one tenant share to exceed the limit and affect the
-   space available for the same tenant’s other shares. One tenant cannot use
-   another tenant’s File Store.
+   space available for the same tenant's other shares. One tenant cannot use
+   another tenant's File Store.
 
 
 -  File removal
@@ -594,7 +594,7 @@ Implementation characteristics
    setting is used (the default), files may be left behind in the File Store.
    Prior to Mitaka, removal of obsolete share directories and files that have
    been stranded would require tools outside of OpenStack/Manila. In Mitaka
-   and later, the driver mounts the File Store to remove the deleted share’s
+   and later, the driver mounts the File Store to remove the deleted share's
    subdirectory and files. For SMB/CIFS share, it requires the
    ``hpe3par_cifs_admin_access_username`` and
    ``hpe3par_cifs_admin_access_password`` configuration. If the mount and