Fix none-ascii char in doc

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

Change-Id: I1ebf83fb4e8cc853fd7f3065ecf420a064c9983f

api-guide/source/faults.rst

@@ -144,7 +144,7 @@ API status code. The system also returns additional
 information about the fault in the body of the response.
 
 
-**Example: Fault: JSON response**
+**Example: Fault: JSON response**
 
 .. code::
 
@@ -158,7 +158,7 @@ information about the fault in the body of the response.
 The error ``code`` is returned in the body of the response for convenience.
 The ``message`` section returns a human-readable message that is appropriate
 for display to the end user. The ``details`` section is optional and may
-contain information—for example, a stack trace—to assist in tracking
+contain information--for example, a stack trace--to assist in tracking
 down an error. The ``details`` section might or might not be appropriate for
 display to an end user.
 
@@ -189,7 +189,7 @@ faults may also contain a ``created`` timestamp that specifies when the fault
 occurred.
 
 
-**Example: Server in error state: JSON response**
+**Example: Server in error state: JSON response**
 
 .. code::
 

api-guide/source/links_and_references.rst

@@ -30,7 +30,7 @@ exists in the current OpenStack deployment.
     }
 
 
-**Example: Full image reference: JSON request**
+**Example: Full image reference: JSON request**
 
 .. code::
 
@@ -97,7 +97,7 @@ following types of link relations are associated with resources:
     }
 
 
-**Example: Server with alternate link: JSON**
+**Example: Server with alternate link: JSON**
 
 .. code::
 

api-guide/source/paginated_collections.rst

@@ -32,7 +32,7 @@ links to traverse a paginated collection without having to input the
 *``marker``* parameter.
 
 
-**Example: Servers collection: JSON (first page)**
+**Example: Servers collection: JSON (first page)**
 
 .. code::
 

api-guide/source/versions.rst

@@ -12,7 +12,7 @@ A version MIME type is always linked to a base MIME type, such as
 application/json. If conflicting versions are specified using both an HTTP
 header and a URI, the URI takes precedence.
 
-**Example: Request with MIME type versioning**
+**Example: Request with MIME type versioning**
 
 .. code::
 
@@ -22,7 +22,7 @@ header and a URI, the URI takes precedence.
     X-Auth-Token: eaaafd18-0fed-4b3a-81b4-663c99ec1cbb
 
 
-**Example: Request with URI versioning**
+**Example: Request with URI versioning**
 
 .. code::
 
@@ -44,7 +44,7 @@ headers, then a multiple-choices response (300) follows that provides
 links and MIME types to available versions.
 
 
-**Example: Multiple choices: JSON response**
+**Example: Multiple choices: JSON response**
 
 .. code::