diff --git a/docs/api.html.in b/docs/api.html.in
index f77e9db70bb5ca833f2ae4700ef26c52457e4b57..eae7657f09af6f5e90d0dc13c2cbb4ae39ea8f16 100644
--- a/docs/api.html.in
+++ b/docs/api.html.in
@@ -207,7 +207,7 @@
     virtualization <a href="#Functions">functions</a>. Depending upon the
     driver being used, calls will be routed through the remote driver to
     the libvirtd daemon. The daemon will reference the connection specific
-    driver in order to retreive the requested information and then pass
+    driver in order to retrieve the requested information and then pass
     back status and/or data through the connection back to the application.
     The application can then decide what to do with that data, such as
     display, write log data, etc. <a href="migration.html">Migration</a>
diff --git a/docs/bugs.html.in b/docs/bugs.html.in
index 2295ae99fdce08076cf616ba1791d15f1535f86d..140d1b41caa1830fad95e678c43ad4952cd84b8c 100644
--- a/docs/bugs.html.in
+++ b/docs/bugs.html.in
@@ -148,7 +148,7 @@
 ... note the process id from the output
 # gdb /usr/sbin/libvirtd
 .... some information about gdb and loading debug data
-(gdb) attach $the_damon_process_id
+(gdb) attach $the_daemon_process_id
 ....
 (gdb) thread apply all bt
 .... information to attach to the bug
diff --git a/docs/drvlxc.html.in b/docs/drvlxc.html.in
index d5a441018461253cc7055cde85bc8925afe0c493..7494eb3880c3fef45eb4eecf5d8285883a344186 100644
--- a/docs/drvlxc.html.in
+++ b/docs/drvlxc.html.in
@@ -620,7 +620,7 @@ to PID 1 inside the container.
 
 <p>
 If the container does not respond to the graceful shutdown
-request, it can be forceably stopped using the <code>virsh destroy</code>
+request, it can be forcibly stopped using the <code>virsh destroy</code>
 </p>
 
 <pre>
diff --git a/docs/firewall.html.in b/docs/firewall.html.in
index 42642bc5926417020b71f82db7af80b902d4473d..5bb6dc1437e7af8f334236653904bb45da707d2d 100644
--- a/docs/firewall.html.in
+++ b/docs/firewall.html.in
@@ -142,7 +142,7 @@ MASQUERADE all  --  *      *       192.168.122.0/24    !192.168.122.0/24</pre>
     <p><a href="http://www.dmtf.org/standards/cim/cim_schema_v2230/CIM_Network.pdf">http://www.dmtf.org/standards/cim/cim_schema_v2230/CIM_Network.pdf</a></p>
     <p>The filters are managed in libvirt as a top level, standalone object.
        This allows the filters to then be referenced by any libvirt object
-       that requires their functionality, instead tieing them only to use
+       that requires their functionality, instead tying them only to use
        by guest NICs. In the current implementation, filters can be associated
        with individual guest NICs via the libvirt domain XML format. In the
        future we might allow filters to be associated with the virtual network
@@ -272,7 +272,7 @@ f5c78134-9da4-0c60-a9f0-fb37bc21ac1f  no-other-rarp-traffic
        to update them. This ensures the guests have their iptables/ebtables
        rules recreated.
     </p>
-    <p>To associate the clean-trafffic filter with a guest, edit the
+    <p>To associate the clean-traffic filter with a guest, edit the
        guest XML config and change the <code>&lt;interface&gt;</code> element
        to include a <code>&lt;filterref&gt;</code> and also specify the
        whitelisted <code>&lt;ip address/&gt;</code> the guest is allowed to
diff --git a/docs/internals/rpc.html.in b/docs/internals/rpc.html.in
index 40fb59df6c8fbafc22d5847c93c610c4fed0057f..627d7aabbc4aebcb407d2f8f66850dbfacb79cb8 100644
--- a/docs/internals/rpc.html.in
+++ b/docs/internals/rpc.html.in
@@ -743,7 +743,7 @@
 
     <p>
       The main libvirt event loop thread is responsible for performing all
-      socket I/O. It will read incoming packets from clients and willl
+      socket I/O. It will read incoming packets from clients and will
       transmit outgoing packets to clients. It will handle the I/O to/from
       streams associated with client API calls. When doing client I/O it
       will also pass the data through any applicable encryption layer
diff --git a/docs/remote.html.in b/docs/remote.html.in
index 25ae30edd0eb14d5a6204ff4bd9ccbc345bfd38d..dc9b354de5f1b0e66ab42f8c1449155d498a08ff 100644
--- a/docs/remote.html.in
+++ b/docs/remote.html.in
@@ -376,7 +376,7 @@ Note that parameter values must be
         <td> libssh2 </td>
         <td>
   A comma separated list of authentication methods to use. Default (is
-  "agent,privkey,keyboard-interactive". The order of the methods is perserved.
+  "agent,privkey,keyboard-interactive". The order of the methods is preserved.
   Some methods may require additional parameters.
 </td>
       </tr>
diff --git a/docs/storage.html.in b/docs/storage.html.in
index 6a32c95e891b2b8d2a710d547b71beb127d85fec..2706bc546d23fd624396f7a32c1c4fe737207561 100644
--- a/docs/storage.html.in
+++ b/docs/storage.html.in
@@ -581,7 +581,7 @@
          &lt;/target&gt;
        &lt;/volume&gt;</pre>
 
-    <h3>Example disk attachement</h3>
+    <h3>Example disk attachment</h3>
     <p>RBD images can be attached to Qemu guests when Qemu is built
     with RBD support. Information about attaching a RBD image to a
     guest can be found