Fix up a few typos in the tree.

Signed-off-by: Chris Lalancette <clalance@redhat.com>

diff --git a/daemon/THREADING.txt b/daemon/THREADING.txt
index 4c7a6166142d6b5c07ee2dbcc6caf04f54e58f68..4be71d63ad4b8ebab5b8b35e233442d646204670 100644 (file)
--- a/daemon/THREADING.txt
+++ b/daemon/THREADING.txt
@@ -59,4 +59,4 @@ for the associated RPC call.
 While the helper method is executing, no locks are held on either
 the client or server, but the ref count on the 'struct qemud_client'
 object is incremented to ensure its not deleted. The helper can
-now safely invoke the neccessary libvirt API call.
+now safely invoke the necessary libvirt API call.

diff --git a/docs/drvqemu.html.in b/docs/drvqemu.html.in
index dd89fc3279a7d484f22fced70167a7b29fa20bf5..024835cfdb3f613287c48825265bbe834c810790 100644 (file)
--- a/docs/drvqemu.html.in
+++ b/docs/drvqemu.html.in
@@ -208,7 +208,7 @@
       Thus, if a vendor / distributor has configured their libvirt package
       to run as 'qemu' by default, a number of changes will be required
       before an administrator can change a host to run guests as root.
-      In particular it will be neccessary to change ownership on the
+      In particular it will be necessary to change ownership on the
       directories <code>/var/run/libvirt/qemu/</code>,
       <code>/var/lib/libvirt/qemu/</code> and
       <code>/var/cache/libvirt/qemu/</code> back to root, in addition

diff --git a/libvirt.spec.in b/libvirt.spec.in
index 7b5c4d77cc198e239d609e3326230091ea9d8eae..e02e58897a940b1ee66937f898d23bce890ad366 100644 (file)
--- a/libvirt.spec.in
+++ b/libvirt.spec.in
@@ -22,7 +22,7 @@
 %endif
 
 
-# Now set the defaults for all the important features, independant
+# Now set the defaults for all the important features, independent
 # of any particular OS
 
 # First the daemon itself

diff --git a/src/esx/esx_driver.c b/src/esx/esx_driver.c
index 5754b24aa13c0346d740d370943f784ca8abd641..ec0cc146a94a02cd96923e2a6a5af8ab4a9868ff 100644 (file)
--- a/src/esx/esx_driver.c
+++ b/src/esx/esx_driver.c
@@ -1486,7 +1486,7 @@ esxDomainDestroy(virDomainPtr domain)
 
     if (taskInfoState != esxVI_TaskInfoState_Success) {
         ESX_ERROR(domain->conn, VIR_ERR_INTERNAL_ERROR,
-                  "Could not destory domain");
+                  "Could not destroy domain");
         goto failure;
     }
 

diff --git a/src/libvirt.c b/src/libvirt.c
index 27d761d5dde2951c1c7ef8dcc647dfb87dd841c9..4cc19ec311dd627b354df1d285f1242529f4baee 100644 (file)
--- a/src/libvirt.c
+++ b/src/libvirt.c
@@ -9423,7 +9423,7 @@ virStreamRef(virStreamPtr stream)
  * Write a series of bytes to the stream. This method may
  * block the calling application for an arbitrary amount
  * of time. Once an application has finished sending data
- * it should call virStreamFinish to wait for succesful
+ * it should call virStreamFinish to wait for successful
  * confirmation from the driver, or detect any error
  *
  * This method may not be used if a stream source has been

diff --git a/src/openvz/openvz_driver.c b/src/openvz/openvz_driver.c
index 54bcaa9fd533af49faa0c7cc8b7ec6d6be3b6acf..d577be1d2e30fefac33df440761316565fa87621 100644 (file)
--- a/src/openvz/openvz_driver.c
+++ b/src/openvz/openvz_driver.c
@@ -780,7 +780,7 @@ openvzDomainDefineXML(virConnectPtr conn, const char *xml)
 
     if (openvzSetInitialConfig(conn, vm->def) < 0) {
         openvzError(conn, VIR_ERR_INTERNAL_ERROR,
-                "%s", _("Error creating intial configuration"));
+                "%s", _("Error creating initial configuration"));
         goto cleanup;
     }
 
@@ -847,7 +847,7 @@ openvzDomainCreateXML(virConnectPtr conn, const char *xml,
 
     if (openvzSetInitialConfig(conn, vm->def) < 0) {
         openvzError(conn, VIR_ERR_INTERNAL_ERROR,
-                "%s", _("Error creating intial configuration"));
+                "%s", _("Error creating initial configuration"));
         goto cleanup;
     }
 

diff --git a/src/remote/remote_driver.c b/src/remote/remote_driver.c
index 135b0d6c65f85fb9e9e907e39ccced5e26dc3fa7..731b2139ec6ea6e7e125822f9169de2eafac62f2 100644 (file)
--- a/src/remote/remote_driver.c
+++ b/src/remote/remote_driver.c
@@ -7915,7 +7915,7 @@ error:
  * NB(4) This is very complicated. Due to connection cloning, multiple
  * threads can want to use the socket at once. Obviously only one of
  * them can. So if someone's using the socket, other threads are put
- * to sleep on condition variables. THe existing thread may completely
+ * to sleep on condition variables. The existing thread may completely
  * send & receive their RPC call/reply while they're asleep. Or it
  * may only get around to dealing with sending the call. Or it may
  * get around to neither. So upon waking up from slumber, the other

diff --git a/src/security/security_selinux.c b/src/security/security_selinux.c
index 670fcb28dd4f961e51b369230e2908967ba462c3..bdd9eb2a93f4c0bc1bff324056025dd24f34e76e 100644 (file)
--- a/src/security/security_selinux.c
+++ b/src/security/security_selinux.c
@@ -329,7 +329,7 @@ SELinuxSetFilecon(virConnectPtr conn, const char *path, char *tcon)
         /* if the error complaint is related to an image hosted on
          * an nfs mount, or a usbfs/sysfs filesystem not supporting
          * labelling, then just ignore it & hope for the best.
-         * The user hopefully set one of the neccessary SELinux
+         * The user hopefully set one of the necessary SELinux
          * virt_use_{nfs,usb,pci}  boolean tunables to allow it...
          */
         if (setfilecon_errno != EOPNOTSUPP) {

diff --git a/src/util/util.c b/src/util/util.c
index ef07a6a57c037549e83e448428ed70c2835270e5..f474ead9d6bad23ebf64e2de93ef7e4cd563ea91 100644 (file)
--- a/src/util/util.c
+++ b/src/util/util.c
@@ -297,7 +297,7 @@ static int virClearCapabilities(void)
 /*
  * @conn Connection to report errors against
  * @argv argv to exec
- * @envp optional enviroment to use for exec
+ * @envp optional environment to use for exec
  * @keepfd options fd_ret to keep open for child process
  * @retpid optional pointer to store child process pid
  * @infd optional file descriptor to use as child input, otherwise /dev/null

diff --git a/src/vbox/vbox_tmpl.c b/src/vbox/vbox_tmpl.c
index 154859a3e74c8cbe7fc0d576d0c02835ba847c0c..72220e10fd0b6d7a1588be112b082e610522ffda 100644 (file)
--- a/src/vbox/vbox_tmpl.c
+++ b/src/vbox/vbox_tmpl.c
@@ -4761,7 +4761,7 @@ static virDrvOpenStatus vboxNetworkOpen(virConnectPtr conn,
         (data->vboxSession == NULL))
         goto cleanup;
 
-    DEBUG0("network intialized");
+    DEBUG0("network initialized");
     /* conn->networkPrivateData = some network specific data */
     return VIR_DRV_OPEN_SUCCESS;
 
@@ -4770,7 +4770,7 @@ cleanup:
 }
 
 static int vboxNetworkClose(virConnectPtr conn) {
-    DEBUG0("network unintialized");
+    DEBUG0("network uninitialized");
     conn->networkPrivateData = NULL;
     return 0;
 }
@@ -5606,7 +5606,7 @@ static virDrvOpenStatus vboxStorageOpen (virConnectPtr conn,
         (data->vboxSession == NULL))
         goto cleanup;
 
-    DEBUG0("vbox storage intialized");
+    DEBUG0("vbox storage initialized");
     /* conn->storagePrivateData = some storage specific data */
     return VIR_DRV_OPEN_SUCCESS;
 
@@ -5615,7 +5615,7 @@ cleanup:
 }
 
 static int vboxStorageClose (virConnectPtr conn) {
-    DEBUG0("vbox storage unintialized");
+    DEBUG0("vbox storage uninitialized");
     conn->storagePrivateData = NULL;
     return 0;
 }

diff --git a/tests/object-locking.ml b/tests/object-locking.ml
index 0c66fc7cf9b14608f8c5fd82f808a0422c176674..a4cd77d7e7306f2010319e14f45a693d25491c9a 100644 (file)
--- a/tests/object-locking.ml
+++ b/tests/object-locking.ml
@@ -332,7 +332,7 @@ let isLockableDriverNull exp =
 
 
 (*
- * Prior to validating a function, intialize these
+ * Prior to validating a function, initialize these
  * to VS.empty
  *
  * They contain the list of driver and object variables

diff --git a/tools/virt-pki-validate.in b/tools/virt-pki-validate.in
index f3d32184819bb2f03817abfa658404cac35d8e5a..a428a9647461207aa00c306d43884e6f7d8c3975 100755 (executable)
--- a/tools/virt-pki-validate.in
+++ b/tools/virt-pki-validate.in
@@ -275,10 +275,10 @@ exit 0
 
 =head1 DESCRIPTION
 
-This tool validates that the neccessary PKI files are configured for
+This tool validates that the necessary PKI files are configured for
 a secure libvirt server or client using the TLS encryption protocol.
 It will report any missing certificate or key files on the host. It
-should be run as root to ensure it can read all the neccessary files
+should be run as root to ensure it can read all the necessary files
 
 =head1 EXIT STATUS