Replace curly quotes with straight quotes

Curly quotes usually input from Chinese input method.
When read from english context, it makes some confusion.

Change-Id: I7224650e2a52e813077bb84ad3ceddb9d87f934e

api-ref/source/parameters.yaml

@@ -398,7 +398,7 @@ pre_signed_queue_methods:
   required: False
   description: |
     A list of HTTP methods. The HTTP method(s) this URL was created for. By
-    selecting the HTTP method, it’s possible to give either read or read/write
+    selecting the HTTP method, it's possible to give either read or read/write
     access to a specific resource.
 
 pre_signed_queue_paths:

api-ref/source/queues.inc

@@ -283,11 +283,11 @@ Create a pre-signed URL for a given queue.
 
    In the case of pre-signed URLs, the queue cannot be created lazily. This
    is to prevent cases where queues are deleted and users still have a valid
-   URL. This is not a big issues in cases where there’s just 1 pool. However,
-   if there’s a deployment using more than 1 type of pool, the lazily created
-   queue may end up in an undesired pool and it’d be possible for an attacker
+   URL. This is not a big issues in cases where there's just 1 pool. However,
+   if there's a deployment using more than 1 type of pool, the lazily created
+   queue may end up in an undesired pool and it'd be possible for an attacker
    to try a DoS on that pool. Therefore, whenever a pre-signed URL is created,
-   if a pool doesn’t exist, it needs to be created.
+   if a pool doesn't exist, it needs to be created.
 
 Normal response codes: 200
 

doc/source/glossary.rst

@@ -19,7 +19,7 @@ Messaging Service Concepts
 ==========================
 The Messaging Service is a multi-tenant, message queue implementation that
 utilizes a RESTful HTTP interface to provide an asynchronous communications
-protocol, which is one of the main requirements in today’s scalable
+protocol, which is one of the main requirements in today's scalable
 applications.
 
 .. glossary::