[ops-guide] Remove unnecessary strings

It seems unnecessary strings are imported
during ops-guide RST conversion.

Change-Id: I728a49a66e3c8c85ae7bf3e1f9b0e6e5070a5f21

doc/ops-guide/source/arch_example_nova_network.rst

@@ -247,8 +247,7 @@ diagram:
 Optional Extensions
 -------------------
 
-You can extend this reference architecture aslegacy networking (nova)
-optional extensions follows:
+You can extend this reference architecture as follows:
 
 -  Add additional cloud controllers (see :doc:`ops_maintenance`).
 

doc/ops-guide/source/arch_scaling.rst

@@ -123,8 +123,7 @@ caveats.
 You must also consider key hardware specifications for the performance
 of user VMs, as well as budget and performance needs, including storage
 performance (spindles/core), memory availability (RAM/core), network
-bandwidthbandwidth hardware specifications and (Gbps/core), and overall
-CPU performance (CPU/core).
+bandwidth (Gbps/core), and overall CPU performance (CPU/core).
 
 .. tip::
 

doc/ops-guide/source/arch_storage.rst

@@ -92,12 +92,11 @@ Another fact that's often forgotten is that when a new file is being
 uploaded, the proxy server must write out as many streams as there are
 replicas—giving a multiple of network traffic. For a three-replica
 cluster, 10 Gbps in means 30 Gbps out. Combining this with the previous
-high bandwidth bandwidth private vs. public network recommendations
-demands of replication is what results in the recommendation that your
-private network be of significantly higher bandwidth than your public
-need be. Oh, and OpenStack Object Storage communicates internally with
-unencrypted, unauthenticated rsync for performance—you do want the
-private network to be private.
+high bandwidth demands of replication is what results in the
+recommendation that your private network be of significantly higher
+bandwidth than your public need be. Oh, and OpenStack Object Storage
+communicates internally with unencrypted, unauthenticated rsync for
+performance—you do want the private network to be private.
 
 The remaining point on bandwidth is the public-facing portion. The
 ``swift-proxy`` service is stateless, which means that you can easily

doc/ops-guide/source/ops_lay_of_the_land.rst

@@ -85,8 +85,7 @@ Administrative Command-Line Tools
 
 There are also several :command:`*-manage` command-line tools. These are
 installed with the project's services on the cloud controller and do not
-need to be installed\*-manage command-line toolscommand-line tools
-administrative separately:
+need to be installed separately:
 
 * :command:`glance-manage`
 * :command:`keystone-manage`

doc/ops-guide/source/ops_logging.rst

@@ -205,8 +205,7 @@ RabbitMQ Web Management Interface or rabbitmqctl
 
 Aside from connection failures, RabbitMQ log files are generally not
 useful for debugging OpenStack related issues. Instead, we recommend you
-use the RabbitMQ web management interface.RabbitMQlogging/monitoring
-RabbitMQ web management interface Enable it on your cloud
+use the RabbitMQ web management interface. Enable it on your cloud
 controller:
 
 .. code-block:: console

doc/ops-guide/source/ops_network_troubleshooting.rst

@@ -1015,7 +1015,7 @@ To see whether you are using namespaces, run :command:`ip netns`:
    qrouter-8a4ce760-ab55-4f2f-8ec5-a2e858ce0d39
 
 L3-agent router namespaces are named ``qrouter-<router_uuid>``, and
-dhcp-agent name spaces are named ``qdhcp-``\ ``<net_uuid>``. This output
+dhcp-agent name spaces are named ``qdhcp-<net_uuid>``. This output
 shows a network node with four networks running dhcp-agents, one of
 which is also running an l3-agent router. It's important to know which
 network you need to be working in. A list of existing networks and their

doc/ops-guide/source/ops_quotas.rst

@@ -72,7 +72,7 @@ Set Compute Service Quotas
 
 As an administrative user, you can update the Compute service quotas for
 an existing tenant, as well as update the quota defaults for a new
-tenant.Compute Compute service See :ref:`table_compute_quota`.
+tenant. See :ref:`table_compute_quota`.
 
 .. _table_compute_quota:
 

doc/ops-guide/source/ops_user_facing_operations.rst

@@ -24,8 +24,7 @@ Adding Images
 
 Several pre-made images exist and can easily be imported into the Image
 service. A common image to add is the CirrOS image, which is very small
-and used for testing purposes.images adding To add this image, simply
-do:
+and used for testing purposes. To add this image, simply do:
 
 .. code-block:: console
 
@@ -198,9 +197,8 @@ Sharing Images Between Projects
 -------------------------------
 
 In a multi-tenant cloud environment, users sometimes want to share their
-personal images or snapshots with other projects.projects sharing images
-betweenimages sharing between projects This can be done on the command
-line with the ``glance`` tool by the owner of the image.
+personal images or snapshots with other projects. This can be done on
+the command line with the ``glance`` tool by the owner of the image.
 
 To share an image or snapshot with another project, do the following:
 
@@ -236,7 +234,7 @@ To share an image or snapshot with another project, do the following:
 Deleting Images
 ---------------
 
-To delete an image,images deleting just execute:
+To delete an image, just execute:
 
 .. code-block:: console
 
@@ -250,7 +248,7 @@ To delete an image,images deleting just execute:
 Other CLI Options
 -----------------
 
-A full set of options can be found using:images CLI options for
+A full set of options can be found using:
 
 .. code-block:: console
 
@@ -279,7 +277,7 @@ Example Image service Database Queries
 
 One interesting example is modifying the table of images and the owner
 of that image. This can be easily done if you simply display the unique
-ID of the owner. Image service database queriesThis example goes one
+ID of the owner. This example goes one
 step further and displays the readable name of the owner:
 
 .. code-block:: mysql
@@ -362,7 +360,7 @@ size of RAM, CPU, and Disk.
      - Number of virtual CPUs presented to the instance.
    * - RXTX_Factor
      - Optional property that allows created servers to have a different
-       bandwidthbandwidth capping cap from that defined in the network
+       bandwidth cap from that defined in the network
        they are attached to. This factor is multiplied by the rxtx\_base
        property of the network.
        Default value is 1.0 (that is, the same as the attached network).