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

[BOOK] [PATCH] Niggles in Chapter 2

From: Chris Pepper <pepper_at_reppep.com>
Date: 2004-10-02 06:20:59 CEST

        Inhibits isn't doesn't match the sentence subject.

        Remove spaces before </para>.

        "locations on the same server as the client" implies there
are two servers. Better to just refer to the client, as there may be
no network server at all (I know there's still arguably a repository
server, but this is still less confusing).

        In the previous section, Sally's change to integer.c was singular.

                                                Regards,

                                                Chris Pepper

Index: ch02.xml
===================================================================
--- ch02.xml (revision 11198)
+++ ch02.xml (working copy)
@@ -157,7 +157,7 @@
              powerless to prevent the problem&mdash;yet it somehow
              provided a false sense of security. It's easy for Harry and
              Sally to imagine that by locking files, each is beginning a
- safe, insulated task, and thus inhibits them from
+ safe, insulated task, and thus not bother
              discussing their incompatible changes early
              on.</para></listitem>
        </itemizedlist>
@@ -306,7 +306,7 @@
          with locking or reserving resources, but it doesn't; it simply
          creates a private copy of the project for you.) For example,
          if you check out <filename>/calc</filename>, you will get a
- working copy like this: </para>
+ working copy like this:</para>

  <screen>
  $ svn checkout http://svn.example.com/repos/calc
@@ -378,7 +378,7 @@
            syntax, allowing for server names and port numbers to be
            specified as part of the URL. Remember that the
            <literal>file:</literal> access method is valid only for
- locations on the same server as the client&mdash;in fact, in
+ locations on the client&mdash;in fact, in
            accordance with convention, the server name portion of the
            URL is required to be either absent or
            <literal>localhost</literal>:</para>
@@ -503,7 +503,7 @@
          numbers, starting at 0, stretching from left to right. Each
          revision number has a filesystem tree hanging below it, and
          each tree is a <quote>snapshot</quote> of the way the
- repository looked after each commit. </para>
+ repository looked after a commit.</para>

        <figure id="svn-ch-2-dia-7">
          <title>The repository</title>
@@ -565,7 +565,7 @@
       button.c:6
  </screen>

- <para>Sally's changes to <filename>integer.c</filename> will
+ <para>Sally's change to <filename>integer.c</filename> will
          appear in your working copy, and your change will still be
          present in <filename>button.c</filename>. In this example,
          the text of <filename>Makefile</filename> is identical in
@@ -608,7 +608,7 @@
            to the repository since its working revision. A
            <command>svn commit</command> of the file will do nothing,
            and an <command>svn update</command> of the file will do
- nothing. </para></listitem>
+ nothing.</para></listitem>
          </varlistentry>

          <varlistentry>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 2 06:21:57 2004

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