[svnbook] r5975 committed - trunk/en/book

wuzhouhui at users.sourceforge.net wuzhouhui at users.sourceforge.net
Sun Sep 1 05:50:03 CDT 2019

Revision: 5975
Author:   wuzhouhui
Date:     2019-09-01 10:50:01 +0000 (Sun, 01 Sep 2019)
Log Message:
* en/book/appa-quickstart.xml
* en/book/appb-svn-for-cvs-users.xml
* en/book/appc-webdav.xml
* en/book/ch05-repository-admin.xml
  Fix some typos.

Modified Paths:

Modified: trunk/en/book/appa-quickstart.xml
--- trunk/en/book/appa-quickstart.xml	2019-09-01 10:45:13 UTC (rev 5974)
+++ trunk/en/book/appa-quickstart.xml	2019-09-01 10:50:01 UTC (rev 5975)
@@ -150,7 +150,7 @@
       creation and maintenance, see
       <xref linkend="svn.reposadmin"/>.</para>
-    <para>Subversion has no concept of a <quote>project.</quote> The
+    <para>Subversion has no concept of a <quote>project</quote>. The
       repository is just a virtual versioned filesystem, a large tree
       that can hold anything you wish.  Some administrators prefer to
       store only one project in a repository, and others prefer to
@@ -159,7 +159,7 @@
       in <xref linkend="svn.reposadmin.projects.chooselayout"/>.
       Either way, the repository manages only files and directories,
       so it's up to humans to interpret particular directories as
-      <quote>projects.</quote>  So while you might see references to
+      <quote>projects</quote>.  So while you might see references to
       projects throughout this book, keep in mind that we're only ever
       talking about some directory (or collection of directories) in
       the repository.</para>

Modified: trunk/en/book/appb-svn-for-cvs-users.xml
--- trunk/en/book/appb-svn-for-cvs-users.xml	2019-09-01 10:45:13 UTC (rev 5974)
+++ trunk/en/book/appb-svn-for-cvs-users.xml	2019-09-01 10:50:01 UTC (rev 5975)
@@ -49,15 +49,15 @@
     <para>Similarly, in CVS, a tag or branch is an annotation on the
       file or on the version information for that individual file,
       whereas in Subversion, a tag or branch is a copy of an entire
-      tree (by convention, into the <filename>/branches</filename>
-      or <filename>/tags</filename> directories that appear at the top
-      level of the repository, beside <filename>/trunk</filename>).  In
+      tree (by convention, into the <filename>branches/</filename>
+      or <filename>tags/</filename> directories that appear at the top
+      level of the repository, beside <filename>trunk/</filename>).  In
       the repository as a whole, many versions of each file may be
       visible: the latest version on each branch, every tagged
       version, and of course the latest version on the trunk
       itself.  So, to refine the terms even further, one would often
       say <quote><filename>foo.c</filename> as it appears in
-      <filename>/branches/REL1</filename> in revision
+      <filename>branches/REL1</filename> in revision
     <para>For more details on this topic, see <xref
@@ -363,7 +363,7 @@
       associated with files and directories in your working
-    <para>To set or get a property name, use the <command>svn
+    <para>To set or get a property value, use the <command>svn
       propset</command> and <command>svn propget</command>
       subcommands.  To list all properties on an object, use
       <command>svn proplist</command>.</para>

Modified: trunk/en/book/appc-webdav.xml
--- trunk/en/book/appc-webdav.xml	2019-09-01 10:45:13 UTC (rev 5974)
+++ trunk/en/book/appc-webdav.xml	2019-09-01 10:50:01 UTC (rev 5975)
@@ -44,7 +44,7 @@
       committee was left with the responsibility of writing RFC 3253 a
       few years later.  The new RFC adds versioning concepts to
       WebDAV, placing the <quote>V</quote> back in
-      <quote>DAV</quote>—hence the term <quote>DeltaV.</quote>
+      <quote>DAV</quote>—hence the term <quote>DeltaV</quote>.
       WebDAV/DeltaV clients and servers are often called just
       <quote>DeltaV</quote> programs, since DeltaV implies the
       existence of basic WebDAV.</para>
@@ -98,7 +98,7 @@
     <para>A long-held debate in the Subversion developer community
-      about whether it was worthfile to remedy either of these
+      about whether it was worthwhile to remedy either of these
       situations eventually reached closure, with the Subversion
       developers officially deciding to abandon plans to fully support
       DeltaV.  As of Subversion 1.7, Subversion clients and servers

Modified: trunk/en/book/ch05-repository-admin.xml
--- trunk/en/book/ch05-repository-admin.xml	2019-09-01 10:45:13 UTC (rev 5974)
+++ trunk/en/book/ch05-repository-admin.xml	2019-09-01 10:50:01 UTC (rev 5975)
@@ -724,8 +724,8 @@
         <para>The syntax of the <filename>hooks-env</filename> file is
           pretty straightforward: each section name is the name of a
-          hook script (such as <literal>pre-commit</literal>
-          or <literal>post-revprop-change</literal>), and the
+          hook script (such as <literal>[pre-commit]</literal>
+          or <literal>[post-revprop-change]</literal>), and the
           configuration items inside that section are treated as
           mappings of environment variable names to desired values.
           Additionally, there is a

More information about the svnbook-dev mailing list