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

cmpilato svnbook-dev at red-bean.com
Fri Dec 9 11:53:26 CST 2005


Author: cmpilato
Date: Fri Dec  9 11:53:21 2005
New Revision: 1898

Modified:
   trunk/src/en/book/ch00.xml
   trunk/src/en/book/ch08.xml

Log:
* src/en/book/ch00.xml
* src/en/book/ch08.xml
  s/sysadmin/system administrator/.  Patch sorta kinda by Martin A. Brooks
  <martin at hinterlands.org>.

Modified: trunk/src/en/book/ch00.xml
==============================================================================
--- trunk/src/en/book/ch00.xml	(original)
+++ trunk/src/en/book/ch00.xml	Fri Dec  9 11:53:21 2005
@@ -70,13 +70,13 @@
       by running the examples inside the Cygwin Unix emulation
       environment.</para>
 
-    <para>Most readers are probably programmers or sysadmins who need
-      to track changes to source code.  This is the most common use
-      for Subversion, and therefore it is the scenario underlying all
-      of the book's examples.  But Subversion can be used to manage
-      changes to any sort of information: images, music, databases,
-      documentation, and so on.  To Subversion, all data is just
-      data.</para>
+    <para>Most readers are probably programmers or system
+      administrators who need to track changes to source code.  This
+      is the most common use for Subversion, and therefore it is the
+      scenario underlying all of the book's examples.  But Subversion
+      can be used to manage changes to any sort of information:
+      images, music, databases, documentation, and so on.  To
+      Subversion, all data is just data.</para>
     
     <para>While this book is written with the assumption that the
       reader has never used version control, we've also tried to make
@@ -95,14 +95,15 @@
 
     <para>This book aims to be useful to people of widely different
       backgrounds—from people with no previous experience in
-      version control to experienced sysadmins.  Depending on your own
-      background, certain chapters may be more or less important to
-      you.  The following can be considered a <quote>recommended
-      reading list</quote> for various types of readers:</para>
+      version control to experienced system administrators.  Depending
+      on your own background, certain chapters may be more or less
+      important to you.  The following can be considered a
+      <quote>recommended reading list</quote> for various types of
+      readers:</para>
 
     <variablelist>
       <varlistentry>
-        <term>Experienced sysadmins</term>
+        <term>Experienced System Administrators</term>
         <listitem>
           <para>The assumption here is that you've probably used CVS
             before, and are dying to get a Subversion server up and

Modified: trunk/src/en/book/ch08.xml
==============================================================================
--- trunk/src/en/book/ch08.xml	(original)
+++ trunk/src/en/book/ch08.xml	Fri Dec  9 11:53:21 2005
@@ -559,9 +559,9 @@
           optimizations like network pipelining and caching.  By using
           Apache as a server, Subversion gets all of these features
           for free.  And since most firewalls already allow HTTP
-          traffic to pass through, sysadmins typically don't even have
-          to change their firewall configurations to allow Subversion
-          to work.</para>
+          traffic to pass through, system administrators typically
+          don't even have to change their firewall configurations to
+          allow Subversion to work.</para>
   
         <para>Subversion uses HTTP and WebDAV (with DeltaV) to
           communicate with an Apache server.  You can read more about
@@ -652,15 +652,16 @@
 
         <para>This RA implementation lacks most of the advantages of
           Apache mentioned in the previous section; however, it may be
-          appealing to some sysadmins nonetheless.  It is dramatically
-          easier to configure and run; setting up an
+          appealing to some system administrators nonetheless.  It is
+          dramatically easier to configure and run; setting up an
           <filename>svnserve</filename> process is nearly
           instantaneous.  It is also much smaller (in terms of lines
           of code) than Apache, making it much easier to audit, for
-          security reasons or otherwise.  Furthermore, some sysadmins
-          may already have an SSH security infrastructure in place,
-          and want Subversion to use it.  Clients using ra_svn can
-          easily tunnel the protocol over SSH.</para>
+          security reasons or otherwise.  Furthermore, some system
+          administrators may already have an SSH security
+          infrastructure in place, and want Subversion to use it.
+          Clients using ra_svn can easily tunnel the protocol over
+          SSH.</para>
 
       </sect3>
 




More information about the svnbook-dev mailing list