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

sunny256 noreply at red-bean.com
Thu May 10 06:55:33 CDT 2007

Author: sunny256
Date: Thu May 10 06:55:32 2007
New Revision: 2792

* src/en/book/appa-quickstart.xml
* src/en/book/appc-webdav.xml
* src/en/book/ch03-advanced-topics.xml
* src/en/book/ch05-repository-admin.xml
* src/en/book/ch06-server-configuration.xml
* src/en/book/ch08-embedding-svn.xml
  Various typo fixes.


Modified: trunk/src/en/book/appa-quickstart.xml
--- trunk/src/en/book/appa-quickstart.xml	(original)
+++ trunk/src/en/book/appa-quickstart.xml	Thu May 10 06:55:32 2007
@@ -107,7 +107,7 @@
       <para><quote>Please make sure your seat backs are in their full,
-        upgright position, and that your tray tables are stored.
+        upright position, and that your tray tables are stored.
         Flight attendants, prepare for take-off….</quote></para>

Modified: trunk/src/en/book/appc-webdav.xml
--- trunk/src/en/book/appc-webdav.xml	(original)
+++ trunk/src/en/book/appc-webdav.xml	Thu May 10 06:55:32 2007
@@ -190,7 +190,7 @@
       property.  This might cause the file to appear as generic icon
       when viewed within a WebDAV shared folder, not having an
       association with any application.  One remedy is to have a
-      sysadmin (or other Subversion-knowledgable person) check out a
+      sysadmin (or other Subversion-knowledgeable person) check out a
       working copy and manually set
       the <literal>svn:mime-type</literal> property on necessary
       files. But there's potentially no end to such cleanup tasks.

Modified: trunk/src/en/book/ch03-advanced-topics.xml
--- trunk/src/en/book/ch03-advanced-topics.xml	(original)
+++ trunk/src/en/book/ch03-advanced-topics.xml	Thu May 10 06:55:32 2007
@@ -140,7 +140,7 @@
         <literal>COMMITTED</literal> revision keywords are used only
         when referring to a working copy path—they don't apply
         to repository URLs.  <literal>HEAD</literal>, on the other
-        hand, can be used in conjuction with both of these path
+        hand, can be used in conjunction with both of these path
       <para>Here are some examples of revision keywords in
@@ -300,7 +300,7 @@
       changes as easily as you can file content changes.  And the
       sending and receiving of property changes occurs as part of your
       typical commit and update operations—you don't have to
-      change your basic processes to accomodate them.</para>
+      change your basic processes to accommodate them.</para>
     <para>Properties show up elsewhere in Subversion, too.  Just as
       files and directories may have arbitrary property names and

Modified: trunk/src/en/book/ch05-repository-admin.xml
--- trunk/src/en/book/ch05-repository-admin.xml	(original)
+++ trunk/src/en/book/ch05-repository-admin.xml	Thu May 10 06:55:32 2007
@@ -1789,7 +1789,7 @@
         their repository data using the previous version of
         Subversion, and load it into a freshly created repository with
         the new version of Subversion.  Now, these types of schema
-        changes haven't occured since Subversion's 1.0 release, and
+        changes haven't occurred since Subversion's 1.0 release, and
         the Subversion developers promise not to force users to dump
         and load their repositories when upgrading between minor
         versions (such as from 1.3 to 1.4) of Subversion.  But there
@@ -2642,7 +2642,7 @@
         the user <literal>syncuser</literal>, and datestamped with the
         time as of that revision's creation.  Also, Subversion's
         underlying repository access interfaces don't provide a
-        mechanism for setting arbitary revision properties as part of
+        mechanism for setting arbitrary revision properties as part of
         a commit.  So <command>svnsync</command> follows up with an
         immediate series of property modifications which copy all the
         revision properties found for that revision in the source
@@ -2856,7 +2856,7 @@
         to be quicker to generate and smaller to store.  But the
         restoration process can be a pain, often involving applying
         multiple incremental backups.  And other methods have their
-        own peculiarities.  Administators need to find the balance
+        own peculiarities.  Administrators need to find the balance
         between the cost of making the backup and the cost of
         restoring it.</para>

Modified: trunk/src/en/book/ch06-server-configuration.xml
--- trunk/src/en/book/ch06-server-configuration.xml	(original)
+++ trunk/src/en/book/ch06-server-configuration.xml	Thu May 10 06:55:32 2007
@@ -2164,7 +2164,7 @@
         <sect4 id="svn.serverconfig.httpd.extra.browsing.reposlisting">
           <title>Listing Repositories</title>
-          <para>If you're serving a colllection of repositories from a
+          <para>If you're serving a collection of repositories from a
             single URL via the <literal>SVNParentPath</literal>
             directive, then it's also possible to have Apache display
             all available repositories to a web browser.  Just
@@ -2208,7 +2208,7 @@
           often live
           in <filename>/usr/local/apache2/logs/</filename>.)</para>
-        <para>The <filename>error_log</filename> describes any interal
+        <para>The <filename>error_log</filename> describes any internal
           errors that Apache runs into as it works.
           The <filename>access_log</filename> file records every
           incoming HTTP request received by Apache.  This makes it
@@ -2337,7 +2337,7 @@
       done over the entire repository: a user can read the repository
       (or not), and she can write to the repository (or not).  It's
       also possible, however, to define finer-grained access rules.
-      One set of users may have permssion to write to a certain
+      One set of users may have permission to write to a certain
       directory in the repository, but not others; another directory
       might not even be readable by all but a few special

Modified: trunk/src/en/book/ch08-embedding-svn.xml
--- trunk/src/en/book/ch08-embedding-svn.xml	(original)
+++ trunk/src/en/book/ch08-embedding-svn.xml	Thu May 10 06:55:32 2007
@@ -437,7 +437,7 @@
       <para>The public API exported by the RA Layer contains
-        functionality necessary for sending and recieving versioned
+        functionality necessary for sending and receiving versioned
         data to and from the repository.  And each of the available RA
         plugins is able to perform that task using a specific
         protocol—libsvn_ra_dav speaks HTTP/WebDAV (optionally
@@ -602,7 +602,7 @@
       time—a fact that the public APIs do a great job of
       successfully hiding from the average user.  In this section, we
       expose some of these implementation details sheerly to appease
-      your overwhelming curiousity.</para>
+      your overwhelming curiosity.</para>
     <!-- =============================================================== -->
     <sect2 id="svn.developer.insidewc.entries">

More information about the svnbook-dev mailing list