[svnbook commit] r1433 - trunk/src/en/book
sunny256
svnbook-dev at red-bean.com
Tue Jun 7 06:28:31 CDT 2005
Author: sunny256
Date: Tue Jun 7 06:28:29 2005
New Revision: 1433
Modified:
trunk/src/en/book/ch02.xml
trunk/src/en/book/ch05.xml
trunk/src/en/book/ch06.xml
trunk/src/en/book/ch09.xml
Log:
Typo fixes in the English book.
* src/en/book/ch02.xml
(svn.basic.vsn-models.copy-merge.sb-1): Moved period outside
parentheses.
* src/en/book/ch05.xml
(svn.reposadmin.create.hooks): Replace "" with <quote></quote>.
(svn.reposadmin.maint.tk.svnadmin): Replace "lstxns" with "lslocks" in
varlistentry about svnadmin subcommands.
* src/en/book/ch06.xml
(svn.serverconfig.netmodel.credcache): Replace [...] with … in
<screen> example.
* src/en/book/ch09.xml
(svn.ref.svn.c.add): Replace [...] with … in <screen> example.
Modified: trunk/src/en/book/ch02.xml
==============================================================================
--- trunk/src/en/book/ch02.xml (original)
+++ trunk/src/en/book/ch02.xml Tue Jun 7 06:28:29 2005
@@ -252,7 +252,7 @@
<para>The copy-modify-merge model is based on the assumption
that files are contextually mergeable: that is, that the
majority of the files in the repository are line-based text
- files (such as program source code.) But for files with
+ files (such as program source code). But for files with
binary formats, such as artwork or sound, it's often
impossible to merge conflicting changes. In these
situations, it really is necessary to users to take strict
Modified: trunk/src/en/book/ch05.xml
==============================================================================
--- trunk/src/en/book/ch05.xml (original)
+++ trunk/src/en/book/ch05.xml Tue Jun 7 06:28:29 2005
@@ -802,13 +802,13 @@
create a more complex policy specifying exactly which
users are allowed to lock particular paths. If the hook
notices a pre-existing lock, then it can also decide
- whether a user is allowed to "steal" the existing lock.
- The repository passes three arguments to the hook: the
- path to the repository, the path being locked, and the
- user attempting to perform the lock. If the program
- returns a non-zero exit value, the lock action is
- aborted and anything printed to stderr is marshalled
- back to the client.</para>
+ whether a user is allowed to <quote>steal</quote> the
+ existing lock. The repository passes three arguments to
+ the hook: the path to the repository, the path being
+ locked, and the user attempting to perform the lock. If
+ the program returns a non-zero exit value, the lock
+ action is aborted and anything printed to stderr is
+ marshalled back to the client.</para>
</listitem>
</varlistentry>
@@ -1350,7 +1350,7 @@
</varlistentry>
<varlistentry>
- <term><literal>lstxns</literal></term>
+ <term><literal>lslocks</literal></term>
<listitem>
<para>List and describe any locks that exist in the
repository.</para>
Modified: trunk/src/en/book/ch06.xml
==============================================================================
--- trunk/src/en/book/ch06.xml (original)
+++ trunk/src/en/book/ch06.xml Tue Jun 7 06:28:29 2005
@@ -255,7 +255,7 @@
$ svn commit -F new_msg.txt
Authentication realm: <svn://host.example.com:3690> example realm
Username: joe
-[...]
+…
</screen>
<para>Or, if you want to disable credential caching permanently,
Modified: trunk/src/en/book/ch09.xml
==============================================================================
--- trunk/src/en/book/ch09.xml (original)
+++ trunk/src/en/book/ch09.xml Tue Jun 7 06:28:29 2005
@@ -577,7 +577,7 @@
A foo.c
A somedir/bar.c
A otherdir/docs/baz.doc
-[...]
+…
</screen>
</refsect1>
More information about the svnbook-dev
mailing list