updated some weird whitespace character to a normal one

Change-Id: I187fb8fc8d10f950bbebc586999eced0bc117432

doc/source/api/form_post_middleware.rst

@@ -27,7 +27,7 @@ request.
 
 The format of the form **POST** request is:
 
-**Example 1.14. Form POST format**
+**Example 1.14. Form POST format**
 
 .. code::
 
@@ -140,7 +140,7 @@ Form **POST** middleware uses an HMAC-SHA1 cryptographic signature. This
 signature includes these elements from the form:
 
 -  The path. Starting with ``/v1/`` onwards and including a container
-   name and, optionally, an object prefix. In `Example 1.15`, “HMAC-SHA1
+   name and, optionally, an object prefix. In `Example 1.15`, “HMAC-SHA1
    signature for form
    POST” the path is
    ``/v1/my_account/container/object_prefix``. Do not URL-encode the
@@ -148,15 +148,15 @@ signature includes these elements from the form:
 
 -  A redirect URL. If there is no redirect URL, use the empty string.
 
--  Maximum file size. In `Example 1.15`, “HMAC-SHA1 signature for form
+-  Maximum file size. In `Example 1.15`, “HMAC-SHA1 signature for form
    POST” the
    ``max_file_size`` is ``104857600`` bytes.
 
--  The maximum number of objects to upload. In `Example 1.15`, “HMAC-SHA1
+-  The maximum number of objects to upload. In `Example 1.15`, “HMAC-SHA1
    signature for form
    POST” ``max_file_count`` is ``10``.
 
--  Expiry time. In `Example 1.15, “HMAC-SHA1 signature for form
+-  Expiry time. In `Example 1.15, “HMAC-SHA1 signature for form
    POST” the expiry time
    is set to ``600`` seconds into the future.
 
@@ -167,7 +167,7 @@ signature includes these elements from the form:
 The following example code generates a signature for use with form
 **POST**:
 
-**Example 1.15. HMAC-SHA1 signature for form POST**
+**Example 1.15. HMAC-SHA1 signature for form POST**
 
 .. code::
 

doc/source/api/large_objects.rst

@@ -2,7 +2,7 @@
 Large objects
 =============
 
-By default, the content of an object cannot be greater than 5 GB.
+By default, the content of an object cannot be greater than 5 GB.
 However, you can use a number of smaller objects to construct a large
 object. The large object is comprised of two types of objects:
 
@@ -40,9 +40,9 @@ Note
 
 If you make a **COPY** request by using a manifest object as the source,
 the new object is a normal, and not a segment, object. If the total size
-of the source segment objects exceeds 5 GB, the **COPY** request fails.
+of the source segment objects exceeds 5 GB, the **COPY** request fails.
 However, you can make a duplicate of the manifest object and this new
-object can be larger than 5 GB.
+object can be larger than 5 GB.
 
 Static large objects
 ~~~~~~~~~~~~~~~~~~~~
@@ -74,7 +74,7 @@ list, where each element contains the following attributes:
 -  ``size_bytes``. The size of the segment object. This value must match
    the ``Content-Length`` of that object.
 
-**Example Static large object manifest list**
+**Example Static large object manifest list**
 
 This example shows three segment objects. You can use several containers
 and the object names do not have to conform to a specific pattern, in
@@ -142,7 +142,7 @@ way.
 Dynamic large objects
 ~~~~~~~~~~~~~~~~~~~~~
 
-You must segment objects that are larger than 5 GB before you can upload
+You must segment objects that are larger than 5 GB before you can upload
 them. You then upload the segment objects like you would any other
 object and create a dynamic large manifest object. The manifest object
 tells Object Storage how to find the segment objects that comprise the
@@ -168,7 +168,7 @@ of segments to a second location and update the manifest to point to
 this new location. During the upload of the new segments, the original
 manifest is still available to download the first set of segments.
 
-**Example Upload segment of large object request: HTTP**
+**Example Upload segment of large object request: HTTP**
 
 .. code::
 
@@ -190,7 +190,7 @@ Unprocessable Entity response is returned.
 You can continue uploading segments like this example shows, prior to
 uploading the manifest.
 
-**Example Upload next segment of large object request: HTTP**
+**Example Upload next segment of large object request: HTTP**
 
 .. code::
 
@@ -220,7 +220,7 @@ subsequent additional segments.
     X-Object-Manifest: {container}/{prefix}
 
 
-**Example Upload manifest response: HTTP**
+**Example Upload manifest response: HTTP**
 
 .. code::
 

doc/source/api/object_api_v1_overview.rst

@@ -68,7 +68,7 @@ The Object Storage system organizes data in a hierarchy, as follows:
    With the Object Storage API, you can:
 
    -  Store an unlimited number of objects. Each object can be as large
-      as 5 GB, which is the default. You can configure the maximum
+      as 5 GB, which is the default. You can configure the maximum
       object size.
 
    -  Upload and store objects of any size with large object creation.
@@ -154,11 +154,11 @@ Your service provider might use different default values.
 Item                         Maximum value Notes
 ============================ ============= =====
 Number of HTTP headers       90
-Length of HTTP headers       4096 bytes
-Length per HTTP request line 8192 bytes
-Length of HTTP request       5 GB
-Length of container names    256 bytes     Cannot contain the ``/`` character.
-Length of object names       1024 bytes    By default, there are no character restrictions.
+Length of HTTP headers       4096 bytes
+Length per HTTP request line 8192 bytes
+Length of HTTP request       5 GB
+Length of container names    256 bytes     Cannot contain the ``/`` character.
+Length of object names       1024 bytes    By default, there are no character restrictions.
 ============================ ============= =====
 
 You must UTF-8-encode and then URL-encode container and object names

doc/source/api/use_content-encoding_metadata.rst

@@ -7,7 +7,7 @@ the ``Content-Encoding`` metadata. This metadata enables you to indicate
 that the object content is compressed without losing the identity of the
 underlying media type (``Content-Type``) of the file, such as a video.
 
-**Example Content-Encoding header request: HTTP**
+**Example Content-Encoding header request: HTTP**
 
 This example assigns an attachment type to the ``Content-Encoding``
 header that indicates how the file is downloaded: