[svnbook commit] r1874 - trunk/src/en/book

[maxb]

Author: maxb
Date: Thu Dec  1 13:07:34 2005
New Revision: 1874

Modified:
   trunk/src/en/book/appb.xml
   trunk/src/en/book/ch01.xml
   trunk/src/en/book/ch07.xml
   trunk/src/en/book/ch09.xml

Log:
Typo fixes.

Patch by: Jens Seidel

* en/book/appb.xml
* en/book/ch01.xml
* en/book/ch07.xml
* en/book/ch09.xml


Modified: trunk/src/en/book/appb.xml
==============================================================================
--- trunk/src/en/book/appb.xml	(original)
+++ trunk/src/en/book/appb.xml	Thu Dec  1 13:07:34 2005
@@ -37,7 +37,7 @@
         universal read/write medium.  The basic idea is that a
         WebDAV-compliant web server can act like a generic file
         server; clients can mount shared folders that behave much like
-        NFS or SMB filesystems..</para>
+        NFS or SMB filesystems.</para>
       
       <para>The tragedy, though, is that the RFC 2518 WebDAV
         specification does not provide any sort of model for version

Modified: trunk/src/en/book/ch01.xml
==============================================================================
--- trunk/src/en/book/ch01.xml	(original)
+++ trunk/src/en/book/ch01.xml	Thu Dec  1 13:07:34 2005
@@ -101,7 +101,7 @@
       he'd already come up with not only the name
       <quote>Subversion</quote>, but also with the basic design of the
       Subversion repository.  When CollabNet called, Karl immediately
-      agreed to work on the project, and Jim got his employer, RedHat
+      agreed to work on the project, and Jim got his employer, Red Hat
       Software, to essentially donate him to the project for an
       indefinite period of time.  CollabNet hired Karl and Ben
       Collins-Sussman, and detailed design work began in May.  With

Modified: trunk/src/en/book/ch07.xml
==============================================================================
--- trunk/src/en/book/ch07.xml	(original)
+++ trunk/src/en/book/ch07.xml	Thu Dec  1 13:07:34 2005
@@ -1361,7 +1361,7 @@
           order for the keyword to be expanded.  You should consider the
           value of the <literal>svn:keywords</literal> property to be
           case-sensitive too—certain keyword names will be recognized
-          regardless of case, but this behaviour is deprecated.</para>
+          regardless of case, but this behavior is deprecated.</para>
 
         <para>Subversion defines the list of keywords available for
           substitution.  That list contains the following five keywords, 
@@ -2357,7 +2357,7 @@
       manipulating your unversioned ones.  But that flexibility means
       that across the lifetime of your repository, a given versioned
       resource might have many paths, and a given path might represent
-      serveral entirely different versioned resources.</para>
+      several entirely different versioned resources.</para>
 
     <para>Subversion is pretty smart about noticing when an object's
       version history includes such <quote>changes of address</quote>.

Modified: trunk/src/en/book/ch09.xml
==============================================================================
--- trunk/src/en/book/ch09.xml	(original)
+++ trunk/src/en/book/ch09.xml	Thu Dec  1 13:07:34 2005
@@ -3887,8 +3887,7 @@
       <refentry id="svn.ref.svn.c.unlock">
         <refnamediv>
           <refname>svn unlock</refname> 
-            <refpurpose>Unlock working copy paths or
-              URLs..</refpurpose>
+            <refpurpose>Unlock working copy paths or URLs.</refpurpose>
         </refnamediv>
         <refsect1>
           <title>Synopsis</title>