From nobody Mon Apr 29 21:55:48 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zoho.com: domain of redhat.com designates 209.132.183.28 as permitted sender) client-ip=209.132.183.28; envelope-from=libvir-list-bounces@redhat.com; helo=mx1.redhat.com; Authentication-Results: mx.zohomail.com; dkim=fail; spf=pass (zoho.com: domain of redhat.com designates 209.132.183.28 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mx.zohomail.com with SMTPS id 15253462489161007.266627542107; Thu, 3 May 2018 04:17:28 -0700 (PDT) Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 325AA30BA36A; Thu, 3 May 2018 11:17:27 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 7F6A530012AA; Thu, 3 May 2018 11:17:26 +0000 (UTC) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id F1EF6180BADA; Thu, 3 May 2018 11:17:24 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id w43BEgwR021278 for ; Thu, 3 May 2018 07:14:42 -0400 Received: by smtp.corp.redhat.com (Postfix) id CC63060BEB; Thu, 3 May 2018 11:14:42 +0000 (UTC) Received: from mx1.redhat.com (ext-mx11.extmail.prod.ext.phx2.redhat.com [10.5.110.40]) by smtp.corp.redhat.com (Postfix) with ESMTPS id C474B60BE2 for ; Thu, 3 May 2018 11:14:39 +0000 (UTC) Received: from mail-wm0-f47.google.com (mail-wm0-f47.google.com [74.125.82.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id F37D932DC83F for ; Thu, 3 May 2018 11:14:26 +0000 (UTC) Received: by mail-wm0-f47.google.com with SMTP id l1so29716475wmb.2 for ; Thu, 03 May 2018 04:14:26 -0700 (PDT) Received: from localhost.localdomain ([5.92.141.214]) by smtp.gmail.com with ESMTPSA id o101-v6sm20739218wrb.44.2018.05.03.04.14.23 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 May 2018 04:14:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=l+6d3jP2MQabeTFy1G9JCR6UiObcnQybdZ/hh+JYRtI=; b=d0OenZW7OyRZa0Y2peezuW9R6OVs77KU7Q5g/mG+mY7Q9TJEXSFc4xTfL3GZ0e0LPt fUj17zij1Ro15vZ7ELvVaycvIKYPdTfY4KKEbNXCirlgq1KyyoiLoRirh+y3wAtkJrke osl7YbdfXnp5y+vWreGEAZJ9J7P6/yH0Z3BZLwPnEcbmZgrfIs08NsC+EImqfLbzf/bv 0BaHZSw+x8eTt05+UMbtG3cMHWdrUyJar/cYOD8NZnKDKtZgc4rVpSEJw9l2JKKlMU6H 7Q9sehvGusOmCMrRL+qyLvoGRENVIyfjK/HCgsfoWGOepclFIPg3TsvtXs0jFAdAkOR2 lG/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:subject:date:message-id :mime-version:content-transfer-encoding; bh=l+6d3jP2MQabeTFy1G9JCR6UiObcnQybdZ/hh+JYRtI=; b=gj3ddvLj9anTpJKeAMN9R1r5EbiSG8w34+xuZPTPUKVNwT2XbZxKXPLneZNOX9GNu8 SG+kcEIQ/m8+9W5FxBhrYVN4wYgpr+C+03d3gvmQwrOjNaETJZ7TudAHChUtwafTjOAP C0rSNifIi+PZL5qCi2az4yOJzykb23XisPoPQpsrYz66pQLKrLBsKmTDV8RDWpe4frh7 5Tdd3LmQJfmsULfRE/pJaJOF82OjrsiygWpGA4XuTU4KNtWK9qhH85jgi4m5cpZigbSG ZXUVtOglO4tNmoBO9zVORRrNiRKMxl0cSQ2hAHCdVZQFXbZNLhPjL9STaLrFdMxpuCNG YrlA== X-Gm-Message-State: ALQs6tDkvpth26WVj8A+HWE+Yo5zj1W0G/RFFqa3X5EMyWeUQtu1CgQJ bB5ROoc2+6c7m5zxqPYPgoy4Hcbx X-Google-Smtp-Source: AB8JxZoGRoKToLOJzQkwuYKxF3C/jVaywkQ6zYi4aFkM0llF7t8MFfrn3DDiOhJxrIkxN5UqSO10NQ== X-Received: by 10.28.74.133 with SMTP id n5mr16253750wmi.31.1525346064999; Thu, 03 May 2018 04:14:24 -0700 (PDT) From: =?UTF-8?q?Ville=20Skytt=C3=A4?= To: libvir-list@redhat.com Date: Thu, 3 May 2018 13:14:19 +0200 Message-Id: <20180503111419.13435-1-ville.skytta@iki.fi> MIME-Version: 1.0 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.40]); Thu, 03 May 2018 11:14:27 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.40]); Thu, 03 May 2018 11:14:27 +0000 (UTC) for IP:'74.125.82.47' DOMAIN:'mail-wm0-f47.google.com' HELO:'mail-wm0-f47.google.com' FROM:'vskytta@gmail.com' RCPT:'' X-RedHat-Spam-Score: 0.58 (DKIM_SIGNED, FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_PASS, T_DKIM_INVALID) 74.125.82.47 mail-wm0-f47.google.com 74.125.82.47 mail-wm0-f47.google.com X-Scanned-By: MIMEDefang 2.84 on 10.5.110.40 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-loop: libvir-list@redhat.com Subject: [libvirt] [PATCH] docs: Grammar and spelling fixes X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Sender: libvir-list-bounces@redhat.com Errors-To: libvir-list-bounces@redhat.com X-Scanned-By: MIMEDefang 2.84 on 10.5.11.24 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.49]); Thu, 03 May 2018 11:17:28 +0000 (UTC) X-ZohoMail-DKIM: fail (Header signature does not verify) X-ZohoMail: RDKM_2 RSF_0 Z_629925259 SPT_0 Signed-off-by: Ville Skytt=C3=A4 --- docs/aclpolkit.html.in | 2 +- docs/api.html.in | 2 +- docs/contribute.html.in | 2 +- docs/downloads.html.in | 2 +- docs/drvbhyve.html.in | 2 +- docs/drvesx.html.in | 2 +- docs/drvlxc.html.in | 2 +- docs/errors.html.in | 2 +- docs/firewall.html.in | 2 +- docs/formatdomain.html.in | 12 ++++++------ docs/formatdomaincaps.html.in | 2 +- docs/internals/rpc.html.in | 2 +- docs/locking-sanlock.html.in | 2 +- docs/news.xml | 2 +- docs/storage.html.in | 2 +- docs/support.html.in | 2 +- 16 files changed, 21 insertions(+), 21 deletions(-) diff --git a/docs/aclpolkit.html.in b/docs/aclpolkit.html.in index 0e3c8e9..98d06da 100644 --- a/docs/aclpolkit.html.in +++ b/docs/aclpolkit.html.in @@ -396,7 +396,7 @@ polkit.addRule(function(action, subject) { To achieve this we need to write a rule which checks whether the connect_driver attribute is LXC and the domain_name - attribute is demo, and match on a action + attribute is demo, and match on action name of org.libvirt.api.domain.getattr. Using the javascript rules format, this ends up written as

diff --git a/docs/api.html.in b/docs/api.html.in index 27abed6..288b9ec 100644 --- a/docs/api.html.in +++ b/docs/api.html.in @@ -155,7 +155,7 @@
  • Enumeration [virConnectList..., virConnectNumOf...] -

    Used to enumerate a set of object available to an given +

    Used to enumerate a set of object available to a given hypervisor connection such as:

    • diff --git a/docs/contribute.html.in b/docs/contribute.html.in index 158c91c..42a1b2f 100644 --- a/docs/contribute.html.in +++ b/docs/contribute.html.in @@ -80,7 +80,7 @@ and future growth of the project, that there are a people who evangalise the work created by the project. This can take many forms, writing blog posts (about usage of features, - personal user experiances, areas for future work, and more), + personal user experiences, areas for future work, and more), syndicating docs and blogs via social media, giving user group and/or conference talks about libvirt.
    • User assistance. Since documentation diff --git a/docs/downloads.html.in b/docs/downloads.html.in index 8cca203..2956a4f 100644 --- a/docs/downloads.html.in +++ b/docs/downloads.html.in @@ -457,7 +457,7 @@ (first release in the middle of Jan, then skip the Feb release), giv= ing a total of 11 releases a year. The Python and Perl modules will aim = to release at the same time as the core libvirt module. Other modules h= ave - independant ad-hoc releases with no fixed time schedle. + independent ad-hoc releases with no fixed time schedule.

      =20

      Release numbering

      diff --git a/docs/drvbhyve.html.in b/docs/drvbhyve.html.in index 63260af..bde8298 100644 --- a/docs/drvbhyve.html.in +++ b/docs/drvbhyve.html.in @@ -239,7 +239,7 @@ to let a guest boot or start a guest using:

      =20 
      start --console domname
      =20 -

      NB: An bootloader configured to require user interaction will pr= event +

      NB: A bootloader configured to require user interaction will pre= vent the domain from starting (and thus virsh console or sta= rt --console from functioning) until the user interacts with it manual= ly on the VM host. Because users typically do not have access to the VM host, diff --git a/docs/drvesx.html.in b/docs/drvesx.html.in index 417aca4..901d659 100644 --- a/docs/drvesx.html.in +++ b/docs/drvesx.html.in @@ -437,7 +437,7 @@ ethernet0.checkMACAddress =3D "false"

      auto
      - This isn't a actual controller model. If specified the ESX dri= ver + This isn't an actual controller model. If specified the ESX dr= iver tries to detect the SCSI controller model referenced in the .vmdk file and use it. Autodetection fails when a SCSI controller has multiple disks attached and the SCSI contr= oller diff --git a/docs/drvlxc.html.in b/docs/drvlxc.html.in index 44c4960..6ee9ee8 100644 --- a/docs/drvlxc.html.in +++ b/docs/drvlxc.html.in @@ -429,7 +429,7 @@ be considered secure against exploits of the host OS. T= he sVirt SELinux driver provides a way to secure containers even when the "user" namespace is not used. The cost is that writing a policy to allow execution of arbitrary OS is not practical. The SELinux sVirt policy is typically -tailored to work with an simpler application confinement use case, +tailored to work with a simpler application confinement use case, as provided by the "libvirt-sandbox" project.

      =20 diff --git a/docs/errors.html.in b/docs/errors.html.in index 8f4f7d4..ea42728 100644 --- a/docs/errors.html.in +++ b/docs/errors.html.in @@ -29,7 +29,7 @@ set specifically to a connection with

      call it with the error information
    • otherwise call virDefaultErrorFunc which is the default error function of the library issuing the err= or on stderr
    • save the error in the connection for later retri= eval with virCo= nnGetLastError
      • -
    • otherwise like when failing to create an hypervisor connection: +
    • otherwise like when failing to create a hypervisor connection:
      1. if there is a global callback set with virSetErrorFunc, call it with the error information
      2. otherwise call virDefaultErrorFunc which is the default error function of the library issuing the err= or diff --git a/docs/firewall.html.in b/docs/firewall.html.in index 11c3c81..0a50687 100644 --- a/docs/firewall.html.in +++ b/docs/firewall.html.in @@ -11,7 +11,7 @@
        • The virtual network driver

          - This provides a isolated bridge device (ie no physical NICs + This provides an isolated bridge device (ie no physical NICs enslaved). Guest TAP devices are attached to this bridge. Guests can talk to each other and the host, and optionally the wider world. diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index 8e864f7..b65fea0 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -622,7 +622,7 @@ =20 order allows to specify the order to add the online v= cpus. For hypervisors/platforms that require to insert multiple vcpus at= once - the order may be duplicated accross all vcpus that need to be + the order may be duplicated across all vcpus that need to be enabled at once. Specifying order is not necessary, vcpus are then added in an arbitrary order. If order info is used, it must be use= d for all online vcpus. Hypervisors may clear or update ordering informa= tion @@ -4058,7 +4058,7 @@ pcie-switch-upstream-port, and of course for this to work properly, you will need to decrease the pcie-expander-bus' busNr accordingly so that there are enough unused bus - numbers above it to accomodate giving out one bus number for + numbers above it to accommodate giving out one bus number for the upstream-port and one for each downstream-port (in addition to the pcie-root-port and the pcie-expander-bus itself). @@ -4212,7 +4212,7 @@
          This is the fully qualified path of the file associated with the lockspace. The offset specifies where the lease is stored within the file. If the lock manager does not - require a offset, just pass 0. + require an offset, just pass 0.
          =20 @@ -4867,7 +4867,7 @@ (Since 0.10.0). For example, in order to work properly with both an 802.1Qbh switch and an Open vSwitch switch, you may choose to specify no type, but both - an profileid (in case the switch is 802.1Qbh) and + a profileid (in case the switch is 802.1Qbh) and an interfaceid (in case the switch is Open vSwitch) (you may also omit the other attributes, such as managerid, typeid, or profileid, to be filled in from the @@ -6174,7 +6174,7 @@ qemu-kvm -net nic,model=3D? /dev/null set to an empty string, then VNC access is disabled. The keymap attribute specifies the keymap to use. I= t is possible to set a limit on the validity of the password by g= iving - an timestamp passwdValidTo=3D'2010-04-09T15:51:00' + a timestamp passwdValidTo=3D'2010-04-09T15:51:00' assumed to be in UTC. The connected attribute a= llows control of connected client during password changes. VNC acc= epts keep value only since 0.9= .3. @@ -6216,7 +6216,7 @@ qemu-kvm -net nic,model=3D? /dev/null passwd attribute is set to an empty string, then SPICE access is disabled. The keymap attribute specifies the keymap to use. It is possible to set a limit on - the validity of the password by giving an timestamp + the validity of the password by giving a timestamp passwdValidTo=3D'2010-04-09T15:51:00' assumed t= o be in UTC.

          diff --git a/docs/formatdomaincaps.html.in b/docs/formatdomaincaps.html.in index 6bfcaf6..027e115 100644 --- a/docs/formatdomaincaps.html.in +++ b/docs/formatdomaincaps.html.in @@ -81,7 +81,7 @@ =20

          CPU Allocation

          =20 -

          Before any devices capability occurs, there might be a info on doma= in +

          Before any devices capability occurs, there might be info on domain wide capabilities, e.g. virtual CPUs:

          =20 
          diff --git a/docs/internals/rpc.html.in b/docs/internals/rpc.html.in
index fca9cb7..048192f 100644
--- a/docs/internals/rpc.html.in
+++ b/docs/internals/rpc.html.in
@@ -133,7 +133,7 @@
       
       
          serial
          
       
          
-        This is an number that starts from 1 and increases
+        This is a number that starts from 1 and increases
         each time a method call packet is sent. A reply or
         stream packet will have a serial number matching the
         original method call packet serial. Events always
diff --git a/docs/locking-sanlock.html.in b/docs/locking-sanlock.html.in
index 9b36561..3ee9849 100644
--- a/docs/locking-sanlock.html.in
+++ b/docs/locking-sanlock.html.in
@@ -76,7 +76,7 @@ SANLOCKOPTS=3D"-w 0"
       configuration file for each libvirt driver that is using
       sanlock. For QEMU, we will edit /etc/libvirt/qemu-sanlock.conf=

       There is one mandatory parameter that needs to be set,
-      the host_id. This is a integer between
+      the host_id. This is an integer between
       1 and 2000, which must be set to a unique
       value on each host running virtual machines.
     
          
diff --git a/docs/news.xml b/docs/news.xml
index d67d5a7..8018141 100644
--- a/docs/news.xml
+++ b/docs/news.xml
@@ -1206,7 +1206,7 @@
         
           The vgaconf attribute was added to video's
           driver element. Possible values are: on,
-          off, and io. It controlls the way how
+          off, and io. It controls the way how
           bhyve exposes video devices to its guests; various guest OSes mi=
ght
           require different settings to boot properly.
         
diff --git a/docs/storage.html.in b/docs/storage.html.in
index 3f1aec1..1906aa6 100644
--- a/docs/storage.html.in
+++ b/docs/storage.html.in
@@ -759,7 +759,7 @@
       This provides a pool based on Virtuozzo storage. Virtuozzo Storage is
       a highly available distributed software-defined storage with built-in
       replication and disaster recovery. More detailed information about
-      Virtuozzo storage and its managment can be found here:
+      Virtuozzo storage and its management can be found here:
=20
       Virtuozzo Storage).
     
          
diff --git a/docs/support.html.in b/docs/support.html.in
index 1a9438f..38f2f90 100644
--- a/docs/support.html.in
+++ b/docs/support.html.in
@@ -199,7 +199,7 @@
       return an error indicating it is not supported. Likewise libvirt will
       make reasonable efforts to keep API calls working across hypervisor
       releases even if the underlying implementation changes. In cases whe=
re
-      this is impossible, an suitable error will be reported. The list of
+      this is impossible, a suitable error will be reported. The list of
       APIs which have implementations           is detail=
ed separately.
     
          
=20
--=20
2.14.1

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