Fix typos in various docs

Fix 8 minor spelling errors in docs/*.html.in

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>

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

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>

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

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

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>

docs/storage.html.in

@@ -581,7 +581,7 @@
          </target>
        &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