From: Atsushi SAKAI
Date: Thu, 24 Apr 2008 09:17:29 +0000 (+0000)
Subject: * proxy/libvirt_proxy.c and docs/* typo fixing
X-Git-Tag: LIBVIRT_0_4_4~167
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=2ef22ecee3843292f8743eed85308125288abe82;p=thirdparty%2Flibvirt.git
* proxy/libvirt_proxy.c and docs/* typo fixing
Atsushi
---
diff --git a/ChangeLog b/ChangeLog
index edd59e89b9..40b8a84bcf 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+Thu Apr 24 18:00:21 JST 2008 Atsushi SAKAI
+
+ * proxy/libvirt_proxy.c docs/* fixing typos
+
Thu Apr 24 09:54:19 CEST 2008 Daniel Veillard
* AUTHORS: indicate that the Logo is by Diana Fong
diff --git a/docs/bindings.html b/docs/bindings.html
index 4b0512e75d..ad4ccfbd89 100644
--- a/docs/bindings.html
+++ b/docs/bindings.html
@@ -27,7 +27,7 @@
Bindings for other languages
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:
- Python: Libvirt comes with direct support for the Python language
(just make sure you installed the libvirt-python package if not
diff --git a/docs/deployment.html b/docs/deployment.html
index e3601e8267..e9f1de2d4d 100644
--- a/docs/deployment.html
+++ b/docs/deployment.html
@@ -45,7 +45,7 @@
Built from CVS / GIT
- 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
diff --git a/docs/downloads.html b/docs/downloads.html
index 23c9240f3f..8bffb84cf1 100644
--- a/docs/downloads.html
+++ b/docs/downloads.html
@@ -33,14 +33,14 @@
Hourly development snapshots
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:
CVS repository access
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:
@@ -57,7 +57,7 @@
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:
diff --git a/docs/downloads.html.in b/docs/downloads.html.in
index e1aae438dc..a1d301ae44 100644
--- a/docs/downloads.html.in
+++ b/docs/downloads.html.in
@@ -18,7 +18,7 @@
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:
@@ -52,7 +52,7 @@
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:
diff --git a/docs/drivers.html b/docs/drivers.html
index 564a063abb..6481183b2e 100644
--- a/docs/drivers.html
+++ b/docs/drivers.html
@@ -34,7 +34,7 @@
Hypervisor drivers
- The hypervisor drivers currently supported by livirt are:
+ The hypervisor drivers currently supported by libvirt are:
diff --git a/docs/drivers.html.in b/docs/drivers.html.in
index a8298ca55e..344a89aebf 100644
--- a/docs/drivers.html.in
+++ b/docs/drivers.html.in
@@ -13,7 +13,7 @@
Hypervisor drivers
- The hypervisor drivers currently supported by livirt are:
+ The hypervisor drivers currently supported by libvirt are:
diff --git a/docs/formatstorage.html b/docs/formatstorage.html
index d9aaf3a09b..b03053e7bd 100644
--- a/docs/formatstorage.html
+++ b/docs/formatstorage.html
@@ -173,7 +173,7 @@ be created. For device based pools it will be the name of the directory in which
devices nodes exist. For the latter /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.
- format
- Provides information about the pool specific volume format.
For disk pools it will provide the partition type. For filesystem
diff --git a/docs/formatstorage.html.in b/docs/formatstorage.html.in
index 107d8abb64..d2a48f416d 100644
--- a/docs/formatstorage.html.in
+++ b/docs/formatstorage.html.in
@@ -209,7 +209,7 @@ be created. For device based pools it will be the name of the directory in which
devices nodes exist. For the latter
/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.
- format
diff --git a/docs/index.html b/docs/index.html
index 607408ea00..8778238c4d 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -56,7 +56,7 @@
Storage on IDE/SCSI/USB disks, FibreChannel, LVM, iSCSI, NFS and filesystems
libvirt provides:
- - Remote management using TLS encryption and x509 certificates
- Remote management authenticating with Kerberos and SASL
- Local access control using PolicyKit
- Zero-conf discovery using Avahi mulicast-DNS
- Management of virtual machines, virtual networks and storage
+ - Remote management using TLS encryption and x509 certificates
- Remote management authenticating with Kerberos and SASL
- Local access control using PolicyKit
- Zero-conf discovery using Avahi multicast-DNS
- Management of virtual machines, virtual networks and storage

diff --git a/docs/index.html.in b/docs/index.html.in
index 9decc38905..db3700363d 100644
--- a/docs/index.html.in
+++ b/docs/index.html.in
@@ -57,7 +57,7 @@
Remote management using TLS encryption and x509 certificates
Remote management authenticating with Kerberos and SASL
Local access control using PolicyKit
- Zero-conf discovery using Avahi mulicast-DNS
+ Zero-conf discovery using Avahi multicast-DNS
Management of virtual machines, virtual networks and storage
diff --git a/docs/sitemap.html b/docs/sitemap.html
index 523f4e981e..95c09baaaf 100644
--- a/docs/sitemap.html
+++ b/docs/sitemap.html
@@ -103,7 +103,7 @@
Driver for the Linux native container API
Test
- Psuedo-driver simulating APIs in memory for test suites
+ Pseudo-driver simulating APIs in memory for test suites
Remote
Driver providing secure remote to the libvirt APIs
diff --git a/proxy/libvirt_proxy.c b/proxy/libvirt_proxy.c
index 93b74ab350..87cff97189 100644
--- a/proxy/libvirt_proxy.c
+++ b/proxy/libvirt_proxy.c
@@ -151,7 +151,7 @@ proxyCloseUnixSocket(void) {
/**
* proxyListenUnixSocket:
- * @path: the fileame for the socket
+ * @path: the filename for the socket
*
* create a new abstract socket based on that path and listen on it
*
@@ -700,7 +700,7 @@ proxyProcessRequests(void) {
if (exit_timeout == 0) {
done = 1;
if (debug > 0) {
- fprintf(stderr, "Exitting after 30s without clients\n");
+ fprintf(stderr, "Exiting after 30s without clients\n");
}
}
} else