[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[PATCH] typo fixes in doc/usr/manual

From: Nick Duffek <nick_at_duffek.com>
Date: 2002-06-27 21:08:46 CEST

I'm pretty sure these are all self-explanatory.

Nick

Index: ./doc/user/manual/model.texi
===================================================================
--- ./doc/user/manual/model.texi
+++ ./doc/user/manual/model.texi Thu Jun 27 13:56:13 2002
@@ -337,7 +337,7 @@
 properties in a property list; the term `property list' is historical.
 
 Each revision number, file, directory, and directory entry in the
-Subversion repository, has its own property list. Subversion puts these
+Subversion repository has its own property list. Subversion puts these
 property lists to several uses:
 @itemize @bullet
 @item
@@ -349,7 +349,7 @@
 property lists to record files' alternative names.
 @item
 The Subversion server uses properties to hold attributes of its own, and
-allow clients to read and modify them. For example, the @samp{svn-acl}
+it allows clients to read and modify them. For example, the @samp{svn-acl}
 property holds an access control list which the Subversion server uses
 to regulate access to repository files.
 @item
Index: ./doc/user/manual/dirversioning.texi
===================================================================
--- ./doc/user/manual/dirversioning.texi
+++ ./doc/user/manual/dirversioning.texi Thu Jun 27 14:54:47 2002
@@ -30,7 +30,7 @@
 Each tree represents the application of a new atomic commit, and is
 called a @dfn{revision}. This is very different from a CVS repository,
 which stores file histories in a collection of RCS files (and doesn't
-track tree-structure.)
+track tree-structure).
 
 So when we refer to "revision 4 of foo.c" (written @dfn{foo.c:4}) in
 CVS, this means the fourth distinct version of @file{foo.c} -- but in
@@ -224,7 +224,7 @@
 copy) in situations that aren't always perfectly, theoretically "safe"
 or pure.
 
-Second, the client tries to keep the working copy in correctly in sync
+Second, the client tries to keep the working copy correctly in sync
 with the repository using as little communication as possible. Of
 course, this is made much harder by the first goal!
 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 27 21:09:16 2002

This is an archived mail posted to the Subversion Dev mailing list.