dbus/doc dbus-specification.xml,1.41,1.42

[Rob McQueen]

Update of /cvs/dbus/dbus/doc
In directory kemper:/tmp/cvs-serv21760/doc

Modified Files:
	dbus-specification.xml 
Log Message:
2006-08-17  Alp Toker  <alp at atoker.com>

	* doc/dbus-specification.xml: Fix some minor typos.

Index: dbus-specification.xml
===================================================================
RCS file: /cvs/dbus/dbus/doc/dbus-specification.xml,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -d -r1.41 -r1.42
--- dbus-specification.xml	3 Aug 2006 20:34:36 -0000	1.41
+++ dbus-specification.xml	17 Aug 2006 21:20:13 -0000	1.42
@@ -139,7 +139,7 @@
       think of a message as a package, the header is the address, and the body
       contains the package contents. The message delivery system uses the header
       information to figure out where to send the message and how to interpret
-      it; the recipient inteprets the body of the message.
+      it; the recipient interprets the body of the message.
     </para>
     
     <para>
@@ -1261,7 +1261,7 @@
         protocol or spec violations should result in immediately dropping the
         connection without notice to the other end. Exceptions should be
         carefully considered, e.g. an exception may be warranted for a
-        well-understood idiosyncracy of a widely-deployed implementation.  In
+        well-understood idiosyncrasy of a widely-deployed implementation.  In
         cases where the other end of a connection is 100% trusted and known to
         be friendly, skipping validation for performance reasons could also make
         sense in certain cases.
@@ -2049,7 +2049,7 @@
               <para>
                 The client locates the cookie, and generates its own hex-encoded
                 randomly-generated challenge string.  The client then
-                concatentates the server's hex-encoded challenge, a ":"
+                concatenates the server's hex-encoded challenge, a ":"
                 character, its own hex-encoded challenge, another ":" character,
                 and the hex-encoded cookie.  It computes the SHA-1 hash of this
                 composite string.  It sends back to the server the client's
@@ -2247,13 +2247,13 @@
       <title>Unix Domain Sockets</title>
       <para>
         Unix domain sockets can be either paths in the file system or on Linux 
-	kernels, they can be abstract which are similar to paths but i
+	kernels, they can be abstract which are similar to paths but
 	do not show up in the file system.  
       </para>
 
       <para>
         When a socket is opened by the D-Bus library it truncates the path 
-	name right befor the first trailing Nul byte.  This is true for both
+	name right before the first trailing Nul byte.  This is true for both
 	normal paths and abstract paths.  Note that this is a departure from
 	previous versions of D-Bus that would create sockets with a fixed 
 	length path name.  Names which were shorter than the fixed length