* docs/architecture.html docs/errors.html docs/format.html

docs/libvir.html: fixing typos spotted by Eduardo Pereira
Daniel

ChangeLog

@@ -1,3 +1,8 @@
+Mon Sep 10 17:15:29 CEST 2007 Daniel Veillard <veillard@redhat.com>
+
+	* docs/architecture.html docs/errors.html docs/format.html
+	  docs/libvir.html: fixing typos spotted by Eduardo Pereira
+
 Mon Sep 10 13:46:05 CEST 2007 Daniel Veillard <veillard@redhat.com>
 
 	* src/xend_internal.c: applied patch from Hugh Brock to allow

docs/architecture.html

@@ -48,7 +48,7 @@ Store one, the Hypervisor hypercall are all isolated in separate C modules
 implementing at least a subset of the common operations defined by the
 drivers present in driver.h:</p><ul><li>xend_internal: implements the driver functions though the Xen
   Daemon</li>
-  <li>xs_internal: implements the subset of the driver availble though the
+  <li>xs_internal: implements the subset of the driver available though the
     Xen Store</li>
   <li>xen_internal: provide the implementation of the functions possible via
     direct hypervisor access</li>

docs/errors.html

@@ -65,5 +65,5 @@ this point, see the error.py example about it:</p><pre>def handler(ctxt, err):
     errno = err
 
 libvirt.registerErrorHandler(handler, 'context') </pre><p>the second argument to the registerErrorHandler function is passed as the
-fist argument of the callback like in the C version. The error is a tuple
+first argument of the callback like in the C version. The error is a tuple
 containing the same field as a virError in C, but cast to Python.</p></div></div><div class="linkList2"><div class="llinks2"><h3 class="links2"><span>main menu</span></h3><ul><li><a href="index.html">Home</a></li><li><a href="news.html">Releases</a></li><li><a href="intro.html">Introduction</a></li><li><a href="architecture.html">libvirt architecture</a></li><li><a href="downloads.html">Downloads</a></li><li><a href="format.html">XML Format</a></li><li><a href="python.html">Binding for Python</a></li><li><a href="errors.html">Handling of errors</a></li><li><a href="FAQ.html">FAQ</a></li><li><a href="bugs.html">Reporting bugs and getting help</a></li><li><a href="remote.html">Remote support</a></li><li><a href="uri.html">Connection URIs</a></li><li><a href="hvsupport.html">Hypervisor support</a></li><li><a href="html/index.html">API Menu</a></li><li><a href="examples/index.html">C code examples</a></li><li><a href="ChangeLog.html">Recent Changes</a></li></ul></div><div class="llinks2"><h3 class="links2"><span>related links</span></h3><ul><li><a href="https://www.redhat.com/archives/libvir-list/">Mail archive</a></li><li><a href="https://bugzilla.redhat.com/bugzilla/buglist.cgi?product=Fedora+Core&amp;component=libvirt&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_status=MODIFIED&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;long_desc_type=allwordssubstr">Open bugs</a></li><li><a href="http://virt-manager.et.redhat.com/">virt-manager</a></li><li><a href="http://search.cpan.org/~danberr/Sys-Virt-0.1.0/">Perl bindings</a></li><li><a href="http://et.redhat.com/~rjones/ocaml-libvirt/">OCaml bindings</a></li><li><a href="http://www.cl.cam.ac.uk/Research/SRG/netos/xen/index.html">Xen project</a></li><li><form action="search.php" enctype="application/x-www-form-urlencoded" method="get"><input name="query" type="text" size="12" value="Search..." /><input name="submit" type="submit" value="Go" /></form></li><li><a href="http://xmlsoft.org/"><img src="Libxml2-Logo-90x34.gif" alt="Made with Libxml2 Logo" /></a></li></ul><p class="credits">Graphics and design by <a href="mail:dfong@redhat.com">Diana Fong</a></p></div></div><div id="bottom"><p class="p1"></p></div></div></body></html>

docs/format.html

@@ -59,7 +59,7 @@ significant:</p><ul><li>name: the domain name, preferably ASCII based</li>
 </ul><p>The format of the devices and their type may grow over time, but the
 following should be sufficient for basic use:</p><p>A <code>disk</code> device indicates a block device, it can have two
 values for the type attribute either 'file' or 'block' corresponding to the 2
-options availble at the Xen layer. It has two mandatory children, and one
+options available at the Xen layer. It has two mandatory children, and one
 optional one in no specific order:</p><ul><li>source with a file attribute containing the path in Domain 0 to the
     file or a dev attribute if using a block device, containing the device
     name ('hda5' or '/dev/hda5')</li>
@@ -72,7 +72,7 @@ guest, it also has a type whose value is currently 'bridge', it also have a
 number of children in no specific order:</p><ul><li>source: indicating the bridge name</li>
   <li>mac: the optional mac address provided in the address attribute</li>
   <li>ip: the optional IP address provided in the address attribute</li>
-  <li>script: the script used to bridge the interfcae in the Domain 0</li>
+  <li>script: the script used to bridge the interface in the Domain 0</li>
   <li>target: and optional target indicating the device name.</li>
 </ul><p>A <code>console</code> element describes a serial console connection to
 the guest. It has no children, and a single attribute <code>tty</code> which
@@ -237,11 +237,11 @@ support a variety of options:</p><ol><li>Userspace SLIRP stack
   <li>Virtual network
     <p>Provides a virtual network using a bridge device in the host.
     Depending on the virtual network configuration, the network may be
-    totally isolated,NAT'ing to aan explicit network device, or NAT'ing to
+    totally isolated, NAT'ing to an explicit network device, or NAT'ing to
     the default route. DHCP and DNS are provided on the virtual network in
     all cases and the IP range can be determined by examining the virtual
     network config with '<code>virsh net-dumpxml &lt;network
-    name&gt;</code>'. There is one virtual network called'default' setup out
+    name&gt;</code>'. There is one virtual network called 'default' setup out
     of the box which does NAT'ing to the default route and has an IP range of
     <code>192.168.22.0/255.255.255.0</code>. Each guest will have an
     associated tun device created with a name of vnetN, which can also be
@@ -311,7 +311,7 @@ support a variety of options:</p><ol><li>Userspace SLIRP stack
   </li>
   <li>TCP tunnel
     <p>A TCP client/server architecture provides a virtual network. One VM
-    provides the server end of the netowrk, all other VMS are configured as
+    provides the server end of the network, all other VMS are configured as
     clients. All network traffic is routed between the VMs via the server.
     This mode is also available to unprivileged users. There is no default
     DNS or DHCP support and no outgoing network access. To provide outgoing
@@ -411,7 +411,7 @@ BIOS you will see</p><pre>&lt;capabilities&gt;
     &lt;/features&gt;
   &lt;/guest&gt;</span>
   ...
-&lt;/capabilities&gt;</pre><p>The fist block (in red) indicates the host hardware capbilities, currently
+&lt;/capabilities&gt;</pre><p>The first block (in red) indicates the host hardware capbilities, currently
 it is limited to the CPU properties but other information may be available,
 it shows the CPU architecture, and the features of the chip (the feature
 block is similar to what you will find in a Xen fully virtualized domain

docs/libvir.html

@@ -585,7 +585,7 @@ drivers present in driver.h:</p>
 <ul>
   <li>xend_internal: implements the driver functions though the Xen
   Daemon</li>
-  <li>xs_internal: implements the subset of the driver availble though the
+  <li>xs_internal: implements the subset of the driver available though the
     Xen Store</li>
   <li>xen_internal: provide the implementation of the functions possible via
     direct hypervisor access</li>
@@ -715,7 +715,7 @@ following should be sufficient for basic use:</p>
 
 <p>A <code>disk</code> device indicates a block device, it can have two
 values for the type attribute either 'file' or 'block' corresponding to the 2
-options availble at the Xen layer. It has two mandatory children, and one
+options available at the Xen layer. It has two mandatory children, and one
 optional one in no specific order:</p>
 <ul>
   <li>source with a file attribute containing the path in Domain 0 to the
@@ -734,7 +734,7 @@ number of children in no specific order:</p>
   <li>source: indicating the bridge name</li>
   <li>mac: the optional mac address provided in the address attribute</li>
   <li>ip: the optional IP address provided in the address attribute</li>
-  <li>script: the script used to bridge the interfcae in the Domain 0</li>
+  <li>script: the script used to bridge the interface in the Domain 0</li>
   <li>target: and optional target indicating the device name.</li>
 </ul>
 
@@ -944,11 +944,11 @@ support a variety of options:</p>
   <li>Virtual network
     <p>Provides a virtual network using a bridge device in the host.
     Depending on the virtual network configuration, the network may be
-    totally isolated,NAT'ing to aan explicit network device, or NAT'ing to
+    totally isolated, NAT'ing to an explicit network device, or NAT'ing to
     the default route. DHCP and DNS are provided on the virtual network in
     all cases and the IP range can be determined by examining the virtual
     network config with '<code>virsh net-dumpxml &lt;network
-    name&gt;</code>'. There is one virtual network called'default' setup out
+    name&gt;</code>'. There is one virtual network called 'default' setup out
     of the box which does NAT'ing to the default route and has an IP range of
     <code>192.168.22.0/255.255.255.0</code>. Each guest will have an
     associated tun device created with a name of vnetN, which can also be
@@ -1018,7 +1018,7 @@ support a variety of options:</p>
   </li>
   <li>TCP tunnel
     <p>A TCP client/server architecture provides a virtual network. One VM
-    provides the server end of the netowrk, all other VMS are configured as
+    provides the server end of the network, all other VMS are configured as
     clients. All network traffic is routed between the VMs via the server.
     This mode is also available to unprivileged users. There is no default
     DNS or DHCP support and no outgoing network access. To provide outgoing
@@ -1140,7 +1140,7 @@ BIOS you will see</p>
   ...
 &lt;/capabilities&gt;</pre>
 
-<p>The fist block (in red) indicates the host hardware capbilities, currently
+<p>The first block (in red) indicates the host hardware capbilities, currently
 it is limited to the CPU properties but other information may be available,
 it shows the CPU architecture, and the features of the chip (the feature
 block is similar to what you will find in a Xen fully virtualized domain
@@ -1361,7 +1361,7 @@ this point, see the error.py example about it:</p>
 libvirt.registerErrorHandler(handler, 'context') </pre>
 
 <p>the second argument to the registerErrorHandler function is passed as the
-fist argument of the callback like in the C version. The error is a tuple
+first argument of the callback like in the C version. The error is a tuple
 containing the same field as a virError in C, but cast to Python.</p>
 
 <h2><a name="FAQ" id="FAQ">FAQ</a></h2>