openstack/openstack-manuals
Code Issues Proposed changes

s/the the/the/g

Browse Source 
Change-Id: I94364e19380025d140b2e2cd041b162c00d1905e
This commit is contained in:
Rich Bowen 2015-06-15 16:44:51 -04:00
parent 07e0ada343
commit b90c1e40b3
5 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/admin-guide-cloud/compute/section_compute-networking-nova.xml
View File

@ -652,7 +652,7 @@ auto eth1
iface eth1 inet dhcp</programlisting> iface eth1 inet dhcp</programlisting>
<para>If the Virtual Network Service Neutron is installed, you can <para>If the Virtual Network Service Neutron is installed, you can
specify the networks to attach to the interfaces by using the specify the networks to attach to the interfaces by using the
<literal>--nic</literal> flag with the the <command>nova</command> <literal>--nic</literal> flag with the <command>nova</command>
command:</para> command:</para>
<screen><prompt>$</prompt> <userinput>nova boot --image ed8b2a37-5535-4a5f-a615-443513036d71 --flavor 1 --nic net-id=<replaceable>NETWORK1_ID</replaceable> --nic net-id=<replaceable>NETWORK2_ID</replaceable> test-vm1</userinput></screen> <screen><prompt>$</prompt> <userinput>nova boot --image ed8b2a37-5535-4a5f-a615-443513036d71 --flavor 1 --nic net-id=<replaceable>NETWORK1_ID</replaceable> --nic net-id=<replaceable>NETWORK2_ID</replaceable> test-vm1</userinput></screen>
</section> </section>

2
doc/arch-design/specialized/section_multi_hypervisor_specialized.xml
View File

@ -46,7 +46,7 @@
than spawning directly on a hypervisor by calling than spawning directly on a hypervisor by calling
a specific host aggregate using the metadata of the image, the a specific host aggregate using the metadata of the image, the
VMware host aggregate compute nodes communicate with vCenter VMware host aggregate compute nodes communicate with vCenter
which then requests scheduling for the the instance to run on which then requests scheduling for the instance to run on
an ESXi hypervisor. As of the Icehouse release, this an ESXi hypervisor. As of the Icehouse release, this
functionality requires that VMware Distributed Resource functionality requires that VMware Distributed Resource
Scheduler (DRS) is enabled on a cluster and set to "Fully Scheduler (DRS) is enabled on a cluster and set to "Fully

2
doc/install-guide/section_neutron-initial-networks.xml
View File

@ -249,7 +249,7 @@
<procedure> <procedure>
<title>To verify network connectivity</title> <title>To verify network connectivity</title>
<step> <step>
<para>From a host on the the external network, ping the tenant router <para>From a host on the external network, ping the tenant router
gateway:</para> gateway:</para>
<screen><prompt>$</prompt> <userinput>ping -c 4 203.0.113.101</userinput> <screen><prompt>$</prompt> <userinput>ping -c 4 203.0.113.101</userinput>
<computeroutput>PING 203.0.113.101 (203.0.113.101) 56(84) bytes of data. <computeroutput>PING 203.0.113.101 (203.0.113.101) 56(84) bytes of data.

2
doc/user-guide/source/cli_swift_large_object_creation.rst
View File

@ -260,7 +260,7 @@ describes their differences:
- Dynamic large object - Dynamic large object
* - End-to-end integrity * - End-to-end integrity
- Assured. The list of segments includes the MD5 checksum - Assured. The list of segments includes the MD5 checksum
(``ETag``) of each segment. You cannot upload the the manifest (``ETag``) of each segment. You cannot upload the manifest
object if the ``ETag`` in the list differs from the uploaded object if the ``ETag`` in the list differs from the uploaded
segment object. If a segment is somehow lost, an attempt to segment object. If a segment is somehow lost, an attempt to
download the manifest object results in an error. download the manifest object results in an error.

2
doc/user-guide/source/set_up_clustering.rst
View File

@ -128,7 +128,7 @@ Set up clustering
- **Instance name. **\ This name consists of the replication set - **Instance name. **\ This name consists of the replication set
name followed by the string -*n*, where *n* is 1 for the name followed by the string -*n*, where *n* is 1 for the
first instance in a replication set, 2 for the the second first instance in a replication set, 2 for the second
instance, and so on. In this example, the instance names are instance, and so on. In this example, the instance names are
``cluster1-rs1-1``, ``cluster1-rs1-2``, and ``cluster1-rs1-3``. ``cluster1-rs1-1``, ``cluster1-rs1-2``, and ``cluster1-rs1-3``.