Fix common misspellings

Wikipedia's list of common misspellings [1] has a machine-readable
version.  This patch fixes those misspellings mentioned in the list
which don't have multiple right variants (as e.g. "accension", which can
be both "accession" and "ascension"), such misspellings are left
untouched.  The list of changes was manually re-checked for false
positives.

[1] https://en.wikipedia.org/wiki/Wikipedia:Lists_of_common_misspellings/For_machinesSigned-off-by: NMartin Kletzander <mkletzan@redhat.com>

docs/bugs.html.in

@@ -11,7 +11,7 @@
 
     <p>
       If you think that an issue with libvirt may have security
-      implications, <strong>please do not</strong> publically
+      implications, <strong>please do not</strong> publicly
       report it in the bug tracker, mailing lists, or irc. Libvirt
       has <a href="securityprocess.html">a dedicated process for handling (potential) security issues</a>
       that should be used instead. So if your issue has security

docs/contact.html.in

@@ -10,7 +10,7 @@
 
     <p>
       If you think that an issue with libvirt may have security
-      implications, <strong>please do not</strong> publically
+      implications, <strong>please do not</strong> publicly
       report it in the bug tracker, mailing lists, or irc. Libvirt
       has <a href="securityprocess.html">a dedicated process for handling (potential) security issues</a>
       that should be used instead. So if your issue has security

docs/schemas/basictypes.rng

@@ -115,7 +115,7 @@
   <!--interface on a device (system).  The duid is often used by servers  -->
   <!--such as dnsmasq to assign a specific IP address (and optionally a   -->
   <!--name to an interface.  The applicable standards are RFC3315 and     -->
-  <!--RFC6355.  These standards actualy require the duid to be fixed for  -->
+  <!--RFC6355.  These standards actually require the duid to be fixed for -->
   <!--the hardward device and applicable to all network interfaces on     -->
   <!--that device.  It is not clear that any software currently enforces  -->
   <!--this requirement although it could be implemented manually.         -->

docs/schemas/interface.rng

@@ -4,7 +4,7 @@
          xmlns:v="http://netcf.org/xml/version/1.0"
          datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">
   <!-- Versions for this schema are simple integers that are incremented
-       everytime a changed (but backwards compatible) version
+       every time a changed (but backwards compatible) version
        is released. The current version is indicated with the v:serial
        attribute on the start element.
   -->

docs/securityprocess.html.in

@@ -66,9 +66,9 @@
     <p>
       The libvirt security team operates a policy of
       <a href="http://en.wikipedia.org/wiki/Responsible_disclosure">responsible disclosure</a>.
-      As such any security issue reported, that is not already publically disclosed
+      As such any security issue reported, that is not already publicly disclosed
       elsewhere, will have an embargo date assigned. Members of the security team agree
-      not to publically disclose any details of the security issue until the embargo
+      not to publicly disclose any details of the security issue until the embargo
       date expires.
     </p>
 
@@ -77,7 +77,7 @@
       are two weeks or less in duration. If a problem is identified
       with a proposed patch for a security issue, requiring further
       investigation and bug fixing, the embargo clock may be restarted.
-      In exceptional circumstances longer initial embargos may be
+      In exceptional circumstances longer initial embargoes may be
       negotiated by mutual agreement between members of the security
       team and other relevant parties to the problem. Any such extended
       embargoes will aim to be at most one month in duration.

examples/systemtap/lock-debug.stp

@@ -49,7 +49,7 @@ probe unlock = library.function("virMutexUnlock")
 probe begin
 {
     %( $# > 1 %? println("error: Too many parameters"); exit();
-       %: print("Started, press ^C when the proccess hangs\n"); %)
+       %: print("Started, press ^C when the process hangs\n"); %)
 }
 
 probe lock.call

include/libvirt/libvirt-host.h

@@ -218,7 +218,7 @@ typedef enum {
  *
  * The types virSchedParameter, virBlkioParameter, and
  * virMemoryParameter are aliases of this type, for use when
- * targetting libvirt earlier than 0.9.2.
+ * targeting libvirt earlier than 0.9.2.
  */
 typedef struct _virTypedParameter virTypedParameter;
 

include/libvirt/virterror.h

@@ -304,7 +304,7 @@ typedef enum {
     VIR_ERR_STORAGE_VOL_EXIST = 90,     /* the storage vol already exists */
     VIR_ERR_CPU_INCOMPATIBLE = 91,      /* given CPU is incompatible with host
                                            CPU*/
-    VIR_ERR_XML_INVALID_SCHEMA = 92,    /* XML document doens't validate against schema */
+    VIR_ERR_XML_INVALID_SCHEMA = 92,    /* XML document doesn't validate against schema */
 } virErrorNumber;
 
 /**

src/bhyve/bhyve_driver.c

@@ -1160,14 +1160,14 @@ bhyveStateCleanup(void)
 }
 
 static int
-bhyveStateInitialize(bool priveleged,
+bhyveStateInitialize(bool privileged,
                      virStateInhibitCallback callback ATTRIBUTE_UNUSED,
                      void *opaque ATTRIBUTE_UNUSED)
 {
     virConnectPtr conn = NULL;
 
-    if (!priveleged) {
-        VIR_INFO("Not running priveleged, disabling driver");
+    if (!privileged) {
+        VIR_INFO("Not running privileged, disabling driver");
         return 0;
     }
 

src/cpu/cpu_powerpc.c

@@ -102,7 +102,7 @@ ppcModelFindPVR(const struct ppc_map *map,
     /* PowerPC Processor Version Register is interpreted as follows :
      * Higher order 16 bits : Power ISA generation.
      * Lower order 16 bits : CPU chip version number.
-     * If the exact CPU isnt found, return the nearest matching CPU generation
+     * If the exact CPU isn't found, return the nearest matching CPU generation
      */
     if (pvr & 0x0000FFFFul)
         return ppcModelFindPVR(map, (pvr & 0xFFFF0000ul));

src/datatypes.c

@@ -377,7 +377,7 @@ virInterfaceDispose(void *obj)
  * @name: pointer to the storage pool name
  * @uuid: pointer to the uuid
  * @privateData: pointer to driver specific private data
- * @freeFunc: private data cleanup function pointer specfic to driver
+ * @freeFunc: private data cleanup function pointer specific to driver
  *
  * Allocates a new storage pool object. When the object is no longer needed,
  * virObjectUnref() must be called in order to not leak data.
@@ -453,7 +453,7 @@ virStoragePoolDispose(void *obj)
  * @name: pointer to the storage vol name
  * @key: pointer to unique key of the volume
  * @privateData: pointer to driver specific private data
- * @freeFunc: private data cleanup function pointer specfic to driver
+ * @freeFunc: private data cleanup function pointer specific to driver
  *
  * Allocates a new storage volume object. When the object is no longer needed,
  * virObjectUnref() must be called in order to not leak data.

src/network/bridge_driver_linux.c

@@ -450,7 +450,7 @@ networkRemoveGeneralIPv4FirewallRules(virFirewallPtr fw,
 
 /* Add all once/network rules required for IPv6.
  * If no IPv6 addresses are defined and <network ipv6='yes'> is
- * specified, then allow IPv6 commuinications between virtual systems.
+ * specified, then allow IPv6 communications between virtual systems.
  * If any IPv6 addresses are defined, then add the rules for regular operation.
  */
 static void

src/qemu/THREADS.txt

@@ -29,7 +29,7 @@ There are a number of locks on various objects
     methods.  However, preferred method is qemuDomObjFromDomain() that uses
     virDomainFindByUUIDRef() which also increases the reference counter and
     finds the domain in the domain list without blocking all other lookups.
-    When the domain is locked and the reference increased, the prefered way of
+    When the domain is locked and the reference increased, the preferred way of
     decrementing the reference counter and unlocking the domain is using the
     qemuDomObjEndAPI() function.
 

src/qemu/qemu_capabilities.c

@@ -1266,7 +1266,7 @@ virQEMUCapsComputeCmdFlags(const char *help,
      * promises to keep the human interface stable, but requests that
      * we use QMP (the JSON interface) for everything.  If the user
      * forgot to include YAJL libraries when building their own
-     * libvirt but is targetting a newer qemu, we are better off
+     * libvirt but is targeting a newer qemu, we are better off
      * telling them to recompile (the spec file includes the
      * dependency, so distros won't hit this).  This check is
      * also in m4/virt-yajl.m4 (see $with_yajl).  */

src/qemu/qemu_driver.c

@@ -6357,7 +6357,7 @@ qemuDomainSaveImageUpdateDef(virQEMUDriverPtr driver,
  * @open_write: open the file for writing (for updates)
  * @unlink_corrupt: remove the image file if it is corrupted
  *
- * Returns the opened fd of the save image file and fills the apropriate fields
+ * Returns the opened fd of the save image file and fills the appropriate fields
  * on success. On error returns -1 on most failures, -3 if corrupt image was
  * unlinked (no error raised).
  */

src/util/virfirewall.c

@@ -945,7 +945,7 @@ virFirewallApply(virFirewallPtr firewall)
     VIR_DEBUG("Applying groups for %p", firewall);
     for (i = 0; i < firewall->ngroups; i++) {
         if (virFirewallApplyGroup(firewall, i) < 0) {
-            VIR_DEBUG("Rolling back groups upto %zu for %p", i, firewall);
+            VIR_DEBUG("Rolling back groups up to %zu for %p", i, firewall);
             size_t first = i;
             virErrorPtr saved_error = virSaveLastError();
 

src/util/virhostdev.c

@@ -569,7 +569,7 @@ virHostdevPreparePCIDevices(virHostdevManagerPtr hostdev_mgr,
 
         /* The device is in use by other active domain if
          * the dev is in list activePCIHostdevs. VFIO devices
-         * belonging to same iommu group cant be shared
+         * belonging to same iommu group can't be shared
          * across guests.
          */
         if (STREQ(virPCIDeviceGetStubDriver(dev), "vfio-pci")) {

src/util/virprocess.c

@@ -354,7 +354,7 @@ virProcessKillPainfully(pid_t pid, bool force)
     /* This loop sends SIGTERM, then waits a few iterations (10 seconds)
      * to see if it dies. If the process still hasn't exited, and
      * @force is requested, a SIGKILL will be sent, and this will
-     * wait upto 5 seconds more for the process to exit before
+     * wait up to 5 seconds more for the process to exit before
      * returning.
      *
      * Note that setting @force could result in dataloss for the process.

src/vbox/vbox_common.c

@@ -7413,7 +7413,7 @@ vboxConnectListAllDomains(virConnectPtr conn,
     /* filter out flag options that will produce 0 results in vbox driver:
      * - managed save: vbox guests don't have managed save images
      * - autostart: vbox doesn't support autostarting guests
-     * - persistance: vbox doesn't support transient guests
+     * - persistence: vbox doesn't support transient guests
      */
     if ((MATCH(VIR_CONNECT_LIST_DOMAINS_TRANSIENT) &&
          !MATCH(VIR_CONNECT_LIST_DOMAINS_PERSISTENT)) ||

src/vbox/vbox_common.h

@@ -32,7 +32,7 @@
  * vbox_CAPI_v*.h. It tells the vbox_common.c
  * how to treat with this symbols. This file
  * can't be included with files such as
- * vbox_CAPI_v*.h, or it would casue multiple
+ * vbox_CAPI_v*.h, or it would cause multiple
  * definitions.
  *
  * You can see the more informations in vbox_api.h

src/xen/xend_internal.c

@@ -523,7 +523,7 @@ xend_op_ext(virConnectPtr xend, const char *path, const char *key, va_list ap)
  * @ap: input values to pass to the operation
  * @...: input values to pass to the operation
  *
- * internal routine to run a POST RPC operation to the Xen Daemon targetting
+ * internal routine to run a POST RPC operation to the Xen Daemon targeting
  * a given domain.
  *
  * Returns 0 in case of success, -1 in case of failure.

src/xenconfig/xen_xm.c

@@ -469,7 +469,7 @@ xenFormatXMInputDevs(virConfPtr conf, virDomainDefPtr def)
 verify(MAX_VIRT_CPUS <= sizeof(1UL) * CHAR_BIT);
 
 /*
- * Convert a virDomainDef object inot an XM config record.
+ * Convert a virDomainDef object into an XM config record.
  */
 virConfPtr
 xenFormatXM(virConnectPtr conn,

tools/wireshark/samples/libvirt-sample.pdml

@@ -3,7 +3,7 @@
 <!-- ***
   This file has been reduced for ineffective packets.
   Real output contains more and more elements, but structure
-  and hierarchy of XML is same as this exmaple.
+  and hierarchy of XML is same as this example.
 *** -->
 <!-- You can find pdml2html.xsl in /usr/share/wireshark or at http://anonsvn.wireshark.org/trunk/wireshark/pdml2html.xsl. -->
 <pdml version="0" creator="wireshark/1.10.2" time="Thu Sep 19 18:09:24 2013" capture_file="">