[svnbook commit] r1247 - in trunk/src/en: . book

maxb svnbook-dev at red-bean.com
Wed Apr 27 16:25:48 CDT 2005

Author: maxb
Date: Wed Apr 27 16:25:47 2005
New Revision: 1247

Change 'use-case' to 'use case' throughout, on the basis the second form being
completely dominant in the top few pages of Google results.

* en/TODO: Remove to-do.

* en/book/appc.xml:
* en/book/ch00.xml:
* en/book/ch03.xml:
* en/book/ch05.xml:
* en/book/ch07.xml:

Modified: trunk/src/en/TODO
--- trunk/src/en/TODO	(original)
+++ trunk/src/en/TODO	Wed Apr 27 16:25:47 2005
@@ -27,8 +27,6 @@
     /usr/local/svn/ or /usr/local/repositories/ throughout the book.
     We ought to consistify.
-  - Use either 'use case' or 'use-case', not a mixture of both.
   - Chapter 8 Section 1.1 "Repository Layer" documents the pre-FSFS state
     of affairs.

Modified: trunk/src/en/book/appc.xml
--- trunk/src/en/book/appc.xml	(original)
+++ trunk/src/en/book/appc.xml	Wed Apr 27 16:25:47 2005
@@ -361,7 +361,7 @@
       <para>Because so many operating systems already have integrated
-        WebDAV abilities, the use-case for this feature borders on
+        WebDAV abilities, the use case for this feature borders on
         fantastical: imagine an office of ordinary users running
         Microsoft Windows or Mac OS.  Each computer
         <quote>mounts</quote> the Subversion repository, which appears

Modified: trunk/src/en/book/ch00.xml
--- trunk/src/en/book/ch00.xml	(original)
+++ trunk/src/en/book/ch00.xml	Wed Apr 27 16:25:47 2005
@@ -269,7 +269,7 @@
             <para>Discusses branches, merges, and tagging, including
               best practices for branching and merging, common
-              use-cases, how to undo changes, and how to easily swing
+              use cases, how to undo changes, and how to easily swing
               from one branch to the next.</para>

Modified: trunk/src/en/book/ch03.xml
--- trunk/src/en/book/ch03.xml	(original)
+++ trunk/src/en/book/ch03.xml	Wed Apr 27 16:25:47 2005
@@ -708,7 +708,7 @@
         <para>Earlier in this chapter, we said that you have to commit
           any changes that you make in order for the repository to
           reflect these changes. That's not entirely true—there
-          <emphasis>are</emphasis> some use-cases that immediately
+          <emphasis>are</emphasis> some use cases that immediately
           commit tree changes to the repository.  This only happens
           when a subcommand is operating directly on a URL, rather
           than on a working-copy path. In particular, specific uses

Modified: trunk/src/en/book/ch05.xml
--- trunk/src/en/book/ch05.xml	(original)
+++ trunk/src/en/book/ch05.xml	Wed Apr 27 16:25:47 2005
@@ -1756,7 +1756,7 @@
           <command>svnadmin list-dblogs</command> perform a
           subset of what is provided by the Berkeley
           <command>db_archive</command> command, and <command>svnadmin
-          recover</command> reflects the common use-cases of the
+          recover</command> reflects the common use cases of the
           <command>db_recover</command> utility.</para>
         <para>There are still a few Berkeley DB utilities that you

Modified: trunk/src/en/book/ch07.xml
--- trunk/src/en/book/ch07.xml	(original)
+++ trunk/src/en/book/ch07.xml	Wed Apr 27 16:25:47 2005
@@ -925,7 +925,7 @@
             <para>Fixing spelling errors, grammatical gotchas, and
               <quote>just-plain-wrongness</quote> in commit log
-              messages is perhaps the most common use-case for the
+              messages is perhaps the most common use case for the
               <option>--revprop</option> option.</para>
@@ -2062,7 +2062,7 @@
-      <para>In the trivial use-case, the new version of our
+      <para>In the trivial use case, the new version of our
         third-party tool would look, from a files-and-directories
         point of view, just like the previous version.  None of the
         libcomplex source files would have been deleted, renamed or

More information about the svnbook-dev mailing list