[libvirt] [PATCH] virsh: fix doc typos
by Nehal J Wani
Fix 6 minor spelling errors in virsh doc
---
tools/virsh.pod | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/tools/virsh.pod b/tools/virsh.pod
index dac9a08..f51060f 100644
--- a/tools/virsh.pod
+++ b/tools/virsh.pod
@@ -560,7 +560,7 @@ exits.
If I<--pass-fds> is specified, the argument is a comma separated list
of open file descriptors which should be pass on into the guest. The
-file descriptors will be re-numered in the guest, starting from 3. This
+file descriptors will be re-numbered in the guest, starting from 3. This
is only supported with container based virtualization.
B<Example>
@@ -889,7 +889,7 @@ also B<domblklist> for listing these names).
If I<--abort> is specified, the active job on the specified disk will
be aborted. If I<--async> is also specified, this command will return
-immediately, rather than waiting for the cancelation to complete. If
+immediately, rather than waiting for the cancellation to complete. If
I<--pivot> is specified, this requests that an active copy job
be pivoted over to the new copy.
If I<--info> is specified, the active job information on the specified
@@ -1158,7 +1158,7 @@ hostname which will not resolve to match one of its public IP addresses, then
libvirt will generate an incorrect URI. In this case I<migrateuri> should be
explicitly specified, using an IP address, or a correct hostname.
-=item * The host has multiple network interaces. If a host has multiple network
+=item * The host has multiple network interfaces. If a host has multiple network
interfaces, it might be desirable for the migration data stream to be sent over
a specific interface for either security or performance reasons. In this case
I<migrateuri> should be explicitly specified, using an IP address associated
@@ -1739,8 +1739,8 @@ hypervisor.
Suspend a running domain into one of these states (possible I<target>
values):
- mem equivallent of S3 ACPI state
- disk equivallent of S4 ACPI state
+ mem equivalent of S3 ACPI state
+ disk equivalent of S4 ACPI state
hybrid RAM is saved to disk but not powered off
The I<--duration> argument specifies number of seconds before the domain is
@@ -2740,7 +2740,7 @@ B<Supported algorithms>
sanitizing removable and non-removable hard disks:
random x2, 0x00, verify.
dod - 4-pass DoD 5220.22-M section 8-306 procedure for
- sanitizing removeable and non-removeable rigid
+ sanitizing removable and non-removable rigid
disks: random, 0x00, 0xff, verify.
bsi - 9-pass method recommended by the German Center of
Security in Information Technologies
--
1.8.1.4
11 years, 8 months
- 2
- 1
[libvirt] [PATCH] Fix typos in various docs
by Nehal J Wani
Fix 8 minor spelling errors in docs/*.html.in
---
docs/api.html.in | 2 +-
docs/bugs.html.in | 2 +-
docs/drvlxc.html.in | 2 +-
docs/firewall.html.in | 4 ++--
docs/internals/rpc.html.in | 2 +-
docs/remote.html.in | 2 +-
docs/storage.html.in | 2 +-
7 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/docs/api.html.in b/docs/api.html.in
index f77e9db..eae7657 100644
--- a/docs/api.html.in
+++ b/docs/api.html.in
@@ -207,7 +207,7 @@
virtualization <a href="#Functions">functions</a>. Depending upon the
driver being used, calls will be routed through the remote driver to
the libvirtd daemon. The daemon will reference the connection specific
- driver in order to retreive the requested information and then pass
+ driver in order to retrieve the requested information and then pass
back status and/or data through the connection back to the application.
The application can then decide what to do with that data, such as
display, write log data, etc. <a href="migration.html">Migration</a>
diff --git a/docs/bugs.html.in b/docs/bugs.html.in
index 2295ae9..140d1b4 100644
--- a/docs/bugs.html.in
+++ b/docs/bugs.html.in
@@ -148,7 +148,7 @@
... note the process id from the output
# gdb /usr/sbin/libvirtd
.... some information about gdb and loading debug data
-(gdb) attach $the_damon_process_id
+(gdb) attach $the_daemon_process_id
....
(gdb) thread apply all bt
.... information to attach to the bug
diff --git a/docs/drvlxc.html.in b/docs/drvlxc.html.in
index d5a4410..7494eb3 100644
--- a/docs/drvlxc.html.in
+++ b/docs/drvlxc.html.in
@@ -620,7 +620,7 @@ to PID 1 inside the container.
<p>
If the container does not respond to the graceful shutdown
-request, it can be forceably stopped using the <code>virsh destroy</code>
+request, it can be forcibly stopped using the <code>virsh destroy</code>
</p>
<pre>
diff --git a/docs/firewall.html.in b/docs/firewall.html.in
index 42642bc..5bb6dc1 100644
--- a/docs/firewall.html.in
+++ b/docs/firewall.html.in
@@ -142,7 +142,7 @@ MASQUERADE all -- * * 192.168.122.0/24 !192.168.122.0/24</pre>
<p><a href="http://www.dmtf.org/standards/cim/cim_schema_v2230/CIM_Network.pdf">http://www.dmtf.org/standards/cim/cim_schema_v2230/CIM_Network.pdf</a></p>
<p>The filters are managed in libvirt as a top level, standalone object.
This allows the filters to then be referenced by any libvirt object
- that requires their functionality, instead tieing them only to use
+ that requires their functionality, instead tying them only to use
by guest NICs. In the current implementation, filters can be associated
with individual guest NICs via the libvirt domain XML format. In the
future we might allow filters to be associated with the virtual network
@@ -272,7 +272,7 @@ f5c78134-9da4-0c60-a9f0-fb37bc21ac1f no-other-rarp-traffic
to update them. This ensures the guests have their iptables/ebtables
rules recreated.
</p>
- <p>To associate the clean-trafffic filter with a guest, edit the
+ <p>To associate the clean-traffic filter with a guest, edit the
guest XML config and change the <code><interface></code> element
to include a <code><filterref></code> and also specify the
whitelisted <code><ip address/></code> the guest is allowed to
diff --git a/docs/internals/rpc.html.in b/docs/internals/rpc.html.in
index 40fb59d..627d7aa 100644
--- a/docs/internals/rpc.html.in
+++ b/docs/internals/rpc.html.in
@@ -743,7 +743,7 @@
<p>
The main libvirt event loop thread is responsible for performing all
- socket I/O. It will read incoming packets from clients and willl
+ socket I/O. It will read incoming packets from clients and will
transmit outgoing packets to clients. It will handle the I/O to/from
streams associated with client API calls. When doing client I/O it
will also pass the data through any applicable encryption layer
diff --git a/docs/remote.html.in b/docs/remote.html.in
index 25ae30e..dc9b354 100644
--- a/docs/remote.html.in
+++ b/docs/remote.html.in
@@ -376,7 +376,7 @@ Note that parameter values must be
<td> libssh2 </td>
<td>
A comma separated list of authentication methods to use. Default (is
- "agent,privkey,keyboard-interactive". The order of the methods is perserved.
+ "agent,privkey,keyboard-interactive". The order of the methods is preserved.
Some methods may require additional parameters.
</td>
</tr>
diff --git a/docs/storage.html.in b/docs/storage.html.in
index 6a32c95..2706bc5 100644
--- a/docs/storage.html.in
+++ b/docs/storage.html.in
@@ -581,7 +581,7 @@
</target>
</volume></pre>
- <h3>Example disk attachement</h3>
+ <h3>Example disk attachment</h3>
<p>RBD images can be attached to Qemu guests when Qemu is built
with RBD support. Information about attaching a RBD image to a
guest can be found
--
1.8.1.4
11 years, 8 months
- 2
- 1