Index: docs/bindings.html =================================================================== RCS file: /data/cvs/libvirt/docs/bindings.html,v retrieving revision 1.1 diff -u -r1.1 bindings.html --- docs/bindings.html 23 Apr 2008 17:08:31 -0000 1.1 +++ docs/bindings.html 24 Apr 2008 00:35:13 -0000 @@ -27,7 +27,7 @@
Libvirt comes with bindings to support other languages than pure C. First the headers embeds the necessary declarations to -allow direct acces from C++ code, but also we have bindings for +allow direct access from C++ code, but also we have bindings for higher level kind of languages:
- When building from CVS it is neccessary to generate the autotools
+ When building from CVS it is necessary to generate the autotools
support files. This requires having autoconf
,
automake
, libtool
and intltool
installed. The process can be automated with the autogen.sh
Index: docs/downloads.html
===================================================================
RCS file: /data/cvs/libvirt/docs/downloads.html,v
retrieving revision 1.32
diff -u -r1.32 downloads.html
--- docs/downloads.html 23 Apr 2008 17:08:31 -0000 1.32
+++ docs/downloads.html 24 Apr 2008 00:35:13 -0000
@@ -33,14 +33,14 @@
Once an hour, an automated snapshot is made from the latest CVS server - source tree. These snapshots should be usable, but we make no guarentees + source tree. These snapshots should be usable, but we make no guarantees about their stability:
The master source repository uses CVS
- and anonymous access is provided. Prior to accessing the server is it neccessary
+ and anonymous access is provided. Prior to accessing the server is it necessary
to authenticate using the password anoncvs
. This can be accomplished with the
cvs login
command:
The libvirt build process uses GNU autotools, so after obtaining a checkout
- it is neccessary to generate the configure script and Makefile.in templates
+ it is necessary to generate the configure script and Makefile.in templates
using the autogen.sh
command. As an example, to do a complete
build and install it into your home directory run:
Once an hour, an automated snapshot is made from the latest CVS server - source tree. These snapshots should be usable, but we make no guarentees + source tree. These snapshots should be usable, but we make no guarantees about their stability:
@@ -31,7 +31,7 @@
The master source repository uses CVS
- and anonymous access is provided. Prior to accessing the server is it neccessary
+ and anonymous access is provided. Prior to accessing the server is it necessary
to authenticate using the password anoncvs
. This can be accomplished with the
cvs login
command:
The libvirt build process uses GNU autotools, so after obtaining a checkout
- it is neccessary to generate the configure script and Makefile.in templates
+ it is necessary to generate the configure script and Makefile.in templates
using the autogen.sh
command. As an example, to do a complete
build and install it into your home directory run:
- The hypervisor drivers currently supported by livirt are: + The hypervisor drivers currently supported by libvirt are:
Index: docs/drivers.html.in =================================================================== RCS file: /data/cvs/libvirt/docs/drivers.html.in,v retrieving revision 1.1 diff -u -r1.1 drivers.html.in --- docs/drivers.html.in 23 Apr 2008 17:08:31 -0000 1.1 +++ docs/drivers.html.in 24 Apr 2008 00:35:13 -0000 @@ -13,7 +13,7 @@- The hypervisor drivers currently supported by livirt are: + The hypervisor drivers currently supported by libvirt are:
/dev/
may seem
like the logical choice, however, devices nodes there are not
guaranteed stable across reboots, since they are allocated on
-demand. It is preferrable to use a stable location such as one
+demand. It is preferable to use a stable location such as one
of the /dev/disk/by-{path,id,uuid,label
locations.
/dev/
may seem
like the logical choice, however, devices nodes there are not
guaranteed stable across reboots, since they are allocated on
-demand. It is preferrable to use a stable location such as one
+demand. It is preferable to use a stable location such as one
of the /dev/disk/by-{path,id,uuid,label
locations.
Index: docs/index.html.in =================================================================== RCS file: /data/cvs/libvirt/docs/index.html.in,v retrieving revision 1.1 diff -u -r1.1 index.html.in --- docs/index.html.in 23 Apr 2008 17:08:31 -0000 1.1 +++ docs/index.html.in 24 Apr 2008 00:35:13 -0000 @@ -57,7 +57,7 @@