Various typos and misspellings

docs/api.html.in

@@ -64,13 +64,13 @@
     <p> Most kind of object can also be named in various ways:</p>
     <ul>
       <li>by their <code>name</code>, an user friendly identifier but
-      whose unicity cannot be garanteed between two nodes.</li>
+      whose unicity cannot be guaranteed between two nodes.</li>
       <li>by their <code>ID</code>, which is a runtime unique identifier
       provided by the hypervisor for one given activation of the object,
       but it becomes invalid once the resource is deactivated.</li >
       <li>by their <code>UUID</code>, a 16 bytes unique identifier
       as defined in <a href="http://www.ietf.org/rfc/rfc4122.txt">RFC 4122</a>,
-      which is garanteed to be unique for long term usage and across a
+      which is guaranteed to be unique for long term usage and across a
       set of nodes.</li>
     </ul>
 

docs/apibuild.py

@@ -2474,7 +2474,7 @@ class docBuilder:
 
 def rebuild(name):
     if name not in ["libvirt", "libvirt-qemu"]:
-        self.warning("rebuild() failed, unkown module %s") % name
+        self.warning("rebuild() failed, unknown module %s") % name
         return None
     builder = None
     srcdir = os.environ["srcdir"]

docs/apps.html.in

@@ -188,7 +188,7 @@
         A general purpose desktop management tool, able to manage
         virtual machines across both local and remotely accessed
         hypervisors. It is targeted at home and small office usage
-        upto managing 10-20 hosts and their VMs.
+        up to managing 10-20 hosts and their VMs.
       </dd>
       <dt><a href="http://virt-manager.org/">virt-viewer</a></dt>
       <dd>

docs/firewall.html.in

@@ -317,7 +317,7 @@ Bridge chain: PREROUTING, entries: 1, policy: ACCEPT
 
 Bridge chain: POSTROUTING, entries: 1, policy: ACCEPT
 -o vnet0 -j libvirt-O-vnet0</pre>
-    <p>To keep things managable and easy to follow, the driver will then
+    <p>To keep things manageable and easy to follow, the driver will then
        create further sub-chains for each protocol then it needs to match
        against:
     </p>

docs/formatdomain.html.in

@@ -425,7 +425,7 @@
        <dd>
          The optional <code>emulatorpin</code> element specifies which of host
          physical CPUs the "emulator", a subset of a domain not including vcpu,
-         will be pinned to. If this is ommitted, "emulator" is pinned to all
+         will be pinned to. If this is omitted, "emulator" is pinned to all
          the physical CPUs by default. It contains one required attribute
          <code>cpuset</code> specifying which physical CPUs to pin to.
        </dd>

docs/hacking.html.in

@@ -18,7 +18,7 @@
           or:
         </p>
 <pre>
-  git diff > libvirt-myfeature.patch
+  git diff &gt; libvirt-myfeature.patch
 </pre>
         <p>However, the usual workflow of libvirt developer is:</p>
 <pre>
@@ -554,8 +554,8 @@
     <p>
       Usage of the <code>fdopen()</code>, <code>close()</code>, <code>fclose()</code>
       APIs is deprecated in libvirt code base to help avoiding double-closing of files
-      or file descriptors, which is particulary dangerous in a multi-threaded
-      applications. Instead of these APIs, use the macros from virfile.h
+      or file descriptors, which is particularly dangerous in a multi-threaded
+      application. Instead of these APIs, use the macros from virfile.h
     </p>
 
    <ul>

docs/internals/locking.html.in

@@ -150,7 +150,7 @@
     <h2><a name="usagePatterns">Lock usage patterns</a></h2>
 
     <p>
-      The following psuedo code illustrates the common
+      The following pseudo code illustrates the common
       patterns of operations invoked on the lock
       manager plugin callbacks.
     </p>

docs/remote.html.in

@@ -356,7 +356,7 @@ Note that parameter values must be
         </td>
         <td> libssh2 </td>
         <td>
-  Path to the known_hosts file to verify the host key agains. LibSSH2
+  Path to the known_hosts file to verify the host key against. LibSSH2
   supports OpenSSH-style known_hosts files, although it does not support
   all key types, so using files created by the OpenSSH binary may result
   into truncating the known_hosts file. It's recommended to use the default