[libvirt] [PATCH] docs: fix typos

[Osier Yang]

于 2011年02月16日 04:51, Eric Blake 写道:
> * docs/drvopenvz.html.in: Spell administrator correctly.
> * docs/drvuml.html.in: Likewise.
> * src/qemu/qemu.conf: Likewise.  Fix other typos, too.
> ---
>
> Pushing under the obvious rule.
>
>   docs/drvopenvz.html.in |    2 +-
>   docs/drvuml.html.in    |    2 +-
>   src/qemu/qemu.conf     |   25 +++++++++++++------------
>   3 files changed, 15 insertions(+), 14 deletions(-)
>
> diff --git a/docs/drvopenvz.html.in b/docs/drvopenvz.html.in
> index 485d209..ddd6ac1 100644
> --- a/docs/drvopenvz.html.in
> +++ b/docs/drvopenvz.html.in
> @@ -55,7 +55,7 @@ openvz+ssh://root@example.com/system (remote access, SSH tunnelled)
>       OpenVZ releases later than 3.0.23 ship with a standard network device
>       setup script that is able to setup bridging, named
>       <code>/usr/sbin/vznetaddbr</code>. For releases prior to 3.0.23, this
> -    script must be created manually by the host OS adminstrator. The
> +    script must be created manually by the host OS administrator. The
>       simplest way is to just download the latest version of this script
>       from a newer OpenVZ release, or upstream source repository. Then
>       a generic configuration file<code>/etc/vz/vznetctl.conf</code>
> diff --git a/docs/drvuml.html.in b/docs/drvuml.html.in
> index 9e5db95..d18e9cc 100644
> --- a/docs/drvuml.html.in
> +++ b/docs/drvuml.html.in
> @@ -7,7 +7,7 @@
>       guests built for User Mode Linux. UML requires no special support in
>       the host kernel, so can be used by any user of any linux system, provided
>       they have enough free RAM for their guest's needs, though there are
> -    certain restrictions on network connectivity unless the adminstrator
> +    certain restrictions on network connectivity unless the administrator
>       has pre-created TAP devices.
>       </p>
>
> diff --git a/src/qemu/qemu.conf b/src/qemu/qemu.conf
> index 66310d4..8c6b996 100644
> --- a/src/qemu/qemu.conf
> +++ b/src/qemu/qemu.conf
> @@ -47,7 +47,7 @@
>
>   # The default TLS configuration only uses certificates for the server
>   # allowing the client to verify the server's identity and establish
> -# and encrypted channel.
> +# an encrypted channel.
>   #
>   # It is possible to use x509 certificates for authentication too, by
>   # issuing a x509 certificate to every client who needs to connect.
> @@ -62,9 +62,9 @@
>   # VNC passwords. This parameter is only used if the per-domain
>   # XML config does not already provide a password. To allow
>   # access without passwords, leave this commented out. An empty
> -# string will still enable passwords, but be rejected by QEMU
> +# string will still enable passwords, but be rejected by QEMU,
>   # effectively preventing any use of VNC. Obviously change this
> -# example here before you set this
> +# example here before you set this.
>   #
>   # vnc_password = "XYZ12345"
>
> @@ -115,7 +115,7 @@
>   #  server-cert.pem - the server certificate signed with ca-cert.pem
>   #  server-key.pem  - the server private key
>   #
> -# This option allows the certificate directory to be changed
> +# This option allows the certificate directory to be changed.
>   #
>   # spice_tls_x509_cert_dir = "/etc/pki/libvirt-spice"
>
> @@ -124,8 +124,8 @@
>   # per-domain XML config does not already provide a password. To
>   # allow access without passwords, leave this commented out. An
>   # empty string will still enable passwords, but be rejected by
> -# QEMU effectively preventing any use of SPICE. Obviously change
> -# this example here before you set this
> +# QEMU, effectively preventing any use of SPICE. Obviously change
> +# this example here before you set this.
>   #
>   # spice_password = "XYZ12345"
>
> @@ -134,15 +134,15 @@
>   # on the host, then the security driver will automatically disable
>   # itself. If you wish to disable QEMU SELinux security driver while
>   # leaving SELinux enabled for the host in general, then set this
> -# to 'none' instead
> +# to 'none' instead.
>   #
>   # security_driver = "selinux"
>
>
> -# The user ID for QEMU processes run by the system instance
> +# The user ID for QEMU processes run by the system instance.
>   #user = "root"
>
> -# The group ID for QEMU processes run by the system instance
> +# The group ID for QEMU processes run by the system instance.
>   #group = "root"
>
>   # Whether libvirt should dynamically change file ownership
> @@ -155,14 +155,15 @@
>   #
>   #  - 'cpu' - use for schedular tunables
>   #  - 'devices' - use for device whitelisting
> +#  - 'memory' - use for memory tunables
>   #
>   # NB, even if configured here, they won't be used unless
> -# the adminsitrator has mounted cgroups. eg
> +# the administrator has mounted cgroups, e.g.:
>   #
>   #  mkdir /dev/cgroup
>   #  mount -t cgroup -o devices,cpu,memory none /dev/cgroup
>   #
> -# They can be mounted anywhere, and different controlers
> +# They can be mounted anywhere, and different controllers
>   # can be mounted in different locations. libvirt will detect
>   # where they are located.
>   #
> @@ -175,7 +176,7 @@
>   # all sound device, and all PTY devices are allowed.
>   #
>   # This will only need setting if newer QEMU suddenly
> -# wants some device we don't already know a bout.
> +# wants some device we don't already know about.
>   #
>   #cgroup_device_acl = [
>   #    "/dev/null", "/dev/full", "/dev/zero",

ACK, quite carefully fixes.

Regards
Osier