Re: [PATCH] Fix typos in various docs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Nov 30, 2013 at 11:57:15PM +0530, Nehal J Wani wrote:
> Fix 8 minor spelling errors in docs/*.html.in

  ACK, applied and pushed,

   thanks !

Daniel

> ---
>  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>&lt;interface&gt;</code> element
>         to include a <code>&lt;filterref&gt;</code> and also specify the
>         whitelisted <code>&lt;ip address/&gt;</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 @@
>           &lt;/target&gt;
>         &lt;/volume&gt;</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
> 
> --
> libvir-list mailing list
> libvir-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/libvir-list

-- 
Daniel Veillard      | Open Source and Standards, Red Hat
veillard@xxxxxxxxxx  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | virtualization library  http://libvirt.org/

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list




[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]