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

[kfogel]

Author: kfogel
Date: Tue May  6 10:10:31 2008
New Revision: 3074

Log:
* src/en/book/foreword.xml
  (Foreword): Incorporate most of O'Reilly's copyedits.


Modified:
   trunk/src/en/book/foreword.xml

Modified: trunk/src/en/book/foreword.xml
==============================================================================
--- trunk/src/en/book/foreword.xml	(original)
+++ trunk/src/en/book/foreword.xml	Tue May  6 10:10:31 2008
@@ -16,9 +16,9 @@
   <title>Foreword</title>
 
   <para>A bad Frequently Asked Questions (FAQ) sheet is one that is
-    composed not of the questions people actually asked, but of the
-    questions the FAQ's author <emphasis>wished</emphasis> people
-    had asked.  Perhaps you've seen the type before:</para>
+    composed not of the questions people actually ask, but of the
+    questions the FAQ's author <emphasis>wish</emphasis> people
+    would ask.  Perhaps you've seen the type before:</para>
 
   <blockquote>
     <para>Q: How can I use Glorbosoft XYZ to maximize team
@@ -28,9 +28,9 @@
   <blockquote>
     <para>A: Many of our customers want to know how they can
       maximize productivity through our patented office groupware
-      innovations.  The answer is simple: first, click on the
-      <quote><literal>File</literal></quote> menu, scroll down to
-      <quote><literal>Increase Productivity</literal></quote>,
+      innovations.  The answer is simple.  First, click on the
+      <literal>File</literal> menu, scroll down to
+      <literal>Increase Productivity</literal>,
       then…</para>
   </blockquote>
 
@@ -38,7 +38,7 @@
     literal sense, FAQs at all.  No one ever called the tech support
     line and asked, <quote>How can we maximize
     productivity?</quote>.  Rather, people asked highly specific
-    questions, like, <quote>How can we change the calendaring system
+    questions, such as <quote>How can we change the calendaring system
     to send reminders two days in advance instead of one?</quote>
     and so on.  But it's a lot easier to make up imaginary
     Frequently Asked Questions than it is to discover the real ones.
@@ -62,16 +62,16 @@
 
   <para>Frustrated at seeing the same questions day after day, Ben
     worked intensely over a month in the summer of 2002 to write
-    <citetitle>The Subversion Handbook</citetitle>, a sixty page
+    <citetitle>The Subversion Handbook</citetitle>, a 60 page
     manual that covered all the basics of using Subversion.  The
     manual made no pretense of being complete, but it was
     distributed with Subversion and got users over that initial hump
-    in the learning curve.  When O'Reilly and Associates decided to
+    in the learning curve.  When O'Reilly decided to
     publish a full-length Subversion book, the path of least
     resistance was obvious: just expand the Subversion
     handbook.</para>
 
-  <para>The three co-authors of the new book were thus presented
+  <para>The three coauthors of the new book were thus presented
     with an unusual opportunity.  Officially, their task was to
     write a book top-down, starting from a table of contents and an
     initial draft.  But they also had access to a steady
@@ -106,18 +106,18 @@
     every question you have about Subversion.  Sometimes, the
     precision with which it anticipates your questions will seem
     eerily telepathic; yet occasionally, you will stumble into a
-    hole in the community's knowledge, and come away empty-handed.
+    hole in the community's knowledge and come away empty-handed.
     When this happens, the best thing you can do is email
     <email>users at subversion.tigris.org</email> and present your
-    problem.  The authors are still there, still watching, and they
-    include not just the three listed on the cover, but many others
+    problem.  The authors are still there and still watching, and the
+    authors include not just the three listed on the cover, but many others
     who contributed corrections and original material.  From the
     community's point of view, solving your problem is merely a
     pleasant side effect of a much larger project—namely,
     slowly adjusting this book, and ultimately Subversion itself, to
     more closely match the way people actually use it.  They are
-    eager to hear from you not merely because they can help you, but
-    because you can help them.  With Subversion as with all active
+    eager to hear from you, not only because they can help you, but
+    because you can help them.  With Subversion, as with all active
     free software projects, <emphasis>you are not
     alone</emphasis>.</para>