openstack/openstack-manuals
Code Issues Proposed changes

Typos and spell errors in admin-guide, arch-design and cli-reference

Browse Source 
While spell-checking some openstack-manuals guides, some typos were found and
this patch address those in the first three directories of the manuals repo.

Change-Id: Ibc2cb5a52679223cd903d2c4162cef98d5da8670
Closes-Bug: 1355720
This commit is contained in:
Sandro Tosi 2014-08-11 20:18:31 +01:00
parent 056398f678
commit 7bfea88d1e
14 changed files with 19 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/admin-guide-cloud/blockstorage/section_backup-block-storage-disks.xml
View File

@ -222,7 +222,7 @@ Block device 251:14</programlisting>
<substeps>
<step>
<para>Unmount the volume:</para>
<screen><userinput>unmount /mnt</userinput></screen>
<screen><userinput>umount /mnt</userinput></screen>
</step>
<step>
<para>Delete the partition table:</para>

2
doc/admin-guide-cloud/blockstorage/section_ts_cinder_config.xml
View File

@ -111,7 +111,7 @@
<para>Issues with <literal>state_path</literal> and
<literal>volumes_dir</literal> settings.</para>
<para>The OpenStack Block Storage uses <command>tgtd</command>
as the default iscsi helper and implements persistent targets.
as the default iSCSI helper and implements persistent targets.
This means that in the case of a tgt restart or even a
node reboot your existing volumes on that node will be
restored automatically with their original IQN.</para>

4
doc/admin-guide-cloud/ch_compute.xml
View File

@ -62,7 +62,7 @@
controllers, and the object store or image service. The state of the entire system is
stored in a database. The cloud controller communicates with the internal object store
using HTTP, but it communicates with the scheduler, network controller, and volume
controller using AMQP (advanced message queueing protocol). To avoid blocking a
controller using AMQP (advanced message queuing protocol). To avoid blocking a
component while waiting for a response, Compute uses asynchronous calls, with a callback
that is triggered when a response is received.</para>
<section xml:id="section_hypervisors">
@ -323,7 +323,7 @@
volume in the Cinder volume system. This gives a more
traditional persistent system that accumulates states,
which are preserved on the Cinder volume across the
deletion and re-creation of the virutal machine. To get a
deletion and re-creation of the virtual machine. To get a
list of available images on your system run:
<screen><prompt>$</prompt> <userinput>nova image-list</userinput>
<?db-font-size 50%?><computeroutput>+--------------------------------------+-------------------------------+--------+--------------------------------------+

2
doc/admin-guide-cloud/ch_identity_mgmt.xml
View File

@ -48,7 +48,7 @@ pipeline = stats_monitoring url_normalize token_auth admin_token_auth xml_body j
<screen><prompt>$</prompt> <userinput>curl -X PATCH http://localhost:5000/v2.0/OS-KSCRUD/users/<replaceable>USERID</replaceable> -H &quot;Content-type: application/json&quot; \
-H &quot;X_Auth_Token: <replaceable>AUTHTOKENID</replaceable>&quot; -d '{&quot;user&quot;: {&quot;password&quot;: &quot;ABCD&quot;, &quot;original_password&quot;: &quot;DCBA&quot;}}'</userinput></screen>
<para>In addition to changing their password, all current
tokens for the user are deleted (if the back end is KVS or sql).</para>
tokens for the user are deleted (if the back end is KVS or SQL).</para>
<note><para>Only use a KVS back end for tokens when testing.</para></note>
</section>
<section xml:id="keystone-logging">

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

@ -18,7 +18,7 @@
<itemizedlist>
<listitem>
<para><systemitem class="service">nova-api</systemitem>. Receives XML
requests and sends them to the rest of the system. It is a wsgi app that
requests and sends them to the rest of the system. It is a WSGI app that
routes and authenticate requests. It supports the EC2 and OpenStack
APIs. There is a <filename>nova-api.conf</filename> file created when
you install Compute.</para>

2
doc/admin-guide-cloud/networking/section_networking-adv-config.xml
View File

@ -9,7 +9,7 @@
<filename>/etc/neutron</filename>.</para>
<section xml:id="section_neutron_server">
<title>OpenStack Networking server with plug-in</title>
<para>This web server runs the OpenStack Networking API Web Server. It laods
<para>This web server runs the OpenStack Networking API Web Server. It loads
a plug-in and passes the API calls to the plug-in for processing. The
<systemitem class="service">neutron-server</systemitem> service receives one or more configuration files
as input. For example:</para>

2
doc/admin-guide-cloud/networking/section_networking-multi-dhcp-agents.xml
View File

@ -96,7 +96,7 @@ physical_interface_mappings = physnet1:eth0</programlisting>
</step>
</procedure>
<procedure>
<title>HostA and Hostb: L2 agent</title>
<title>HostA and HostB: L2 agent</title>
<step>
<para>Neutron configuration file
<filename>/etc/neutron/neutron.conf</filename>:</para>

2
doc/admin-guide-cloud/section_object-storage-monitoring.xml
View File

@ -290,7 +290,7 @@ def process_container(self, dbfile):
with a <link
xlink:href="https://github.com/sivy/py-statsd"
>similar-looking project</link> also hosted on
GitHub), but the released version on PyPi was missing two
GitHub), but the released version on PyPI was missing two
desired features the latest version in GitHub had: the
ability to configure a metrics prefix in the client object
and a convenience method for sending timing data between

4
doc/arch-design/compute_focus/section_architecture_compute_focus.xml
View File

@ -518,7 +518,7 @@
<para>The exclusion of certain OpenStack components might also limit or
constrain the functionality of other components. If a design opts to
include the Orchestration module but exclude the Telemetry module, then
the design will not be able to take advantage of Orchestration's aut
the design will not be able to take advantage of Orchestration's auto
scaling functionality (which relies on information from Telemetry). Due
to the fact that you can use Orchestration to spin up a large number of
instances to perform the compute-intensive processing, including
@ -592,7 +592,7 @@
information. Selection of an appropriate back-end database that will
satisfy the availability and fault tolerance requirements of the
OpenStack services is required. OpenStack services support connecting
to any database that is supported by the sqlalchemy Python drivers,
to any database that is supported by the SQLAlchemy Python drivers,
however most common database deployments make use of MySQL or some
variation of it. It is recommended that the database which provides
back-end service within a general purpose cloud be made highly

2
doc/arch-design/generalpurpose/section_architecture_general_purpose.xml
View File

@ -209,7 +209,7 @@
expandability) to match the requirements of selected scale-out
storage solution. For example, if a centralized storage
solution is required, such as a centralized storage array from
a storage vendor that has infiniBand or FDDI connections, the
a storage vendor that has InfiniBand or FDDI connections, the
server hardware will need to have appropriate network adapters
installed to be compatible with the storage array vendor's
specifications.</para>

6
doc/arch-design/network_focus/section_architecture_network_focus.xml
View File

@ -38,7 +38,7 @@
be required to fill in the functional gaps. Hardware load
balancers are an example of equipment that may be necessary to
distribute workloads or offload certain functions. Note that,
as of the icehouse release, dynamic routing is currently in
as of the Icehouse release, dynamic routing is currently in
its infancy within OpenStack and may need to be implemented
either by an external device or a specialized service instance
within OpenStack. Tunneling is a feature provided by OpenStack Networking,
@ -148,7 +148,7 @@
<para>A design decision that many overlook is a choice of layer 3
protocols. While OpenStack was initially built with only IPv4
support, Networking now supports IPv6 and dual-stacked networks.
Note that, as of the icehouse release, this only includes
Note that, as of the Icehouse release, this only includes
stateless address autoconfiguration but the work is in
progress to support stateless and stateful dhcpv6 as well as
IPv6 floating IPs without NAT. Some workloads become possible
@ -158,7 +158,7 @@
options are available. This will alter the requirements for
any address plan as single-stacked and transitional IPv6
deployments can alleviate the need for IPv4 addresses.</para>
<para>As of the icehouse release, OpenStack has limited support
<para>As of the Icehouse release, OpenStack has limited support
for dynamic routing, however there are a number of options
available by incorporating third party solutions to implement
routing within the cloud including network equipment, hardware

2
doc/arch-design/storage_focus/section_prescriptive_examples_storage_focus.xml
View File

@ -74,7 +74,7 @@
for large scale performance-oriented systems.</para>
<para>This example discusses an OpenStack Object Store with a high
performance requirement. OpenStack has integration with Hadoop
through the Data processing project (sahara), which is leveraged
through the Data processing project (Sahara), which is leveraged
to manage the Hadoop cluster within the cloud.
<mediaobject>
<imageobject>

2
doc/cli-reference/ch_cli_glance_property_keys.xml
View File

@ -310,7 +310,7 @@
<td>libvirt API driver</td>
<td>os_command_line</td>
<td>The kernel command line to be used by the libvirt driver, instead of the
default. For linux containers (LXC), the value is used as arguments for
default. For Linux Containers (LXC), the value is used as arguments for
initialization. This key is valid only for Amazon kernel, ramdisk,
or machine images (aki, ari, or ami).</td>
<td/>

4
doc/cli-reference/ch_cli_neutron-debug_commands.xml
View File

@ -191,7 +191,7 @@
&lt;ca-certificate&gt;</command></term>
<listitem>
<para>Specify a CA bundle file to use in verifying a TLS
(https) server certificate. Defaults to
(HTTPS) server certificate. Defaults to
<code>env[OS_CACERT]</code>
</para>
</listitem>
@ -200,7 +200,7 @@
<term><command>--insecure</command></term>
<listitem>
<para>Explicitly allow neutron-debug to perform "insecure"
SSL (https) requests. The server's certificate will not be
SSL (HTTPS) requests. The server's certificate will not be
verified against any certificate authorities. This option
should be used with caution.</para>
</listitem>