[svnbook commit] r1446 - trunk/src/en/book
cmpilato
svnbook-dev at red-bean.com
Wed Jun 15 00:14:49 CDT 2005
Author: cmpilato
Date: Wed Jun 15 00:14:47 2005
New Revision: 1446
Modified:
trunk/src/en/book/ch05.xml
Log:
Minor fixes. Patch by Chris Pepper <pepper at reppep.com>.
* src/en/book/ch05.xml
(Berkeley DB): s/clean/cleans/ (subject-verb agreement);
s/BerkeleyDB/Berkeley DB/
(FSFS): s/time-out/time out/ (I believe this is more appropriate,
but both are common usage).
Modified: trunk/src/en/book/ch05.xml
==============================================================================
--- trunk/src/en/book/ch05.xml (original)
+++ trunk/src/en/book/ch05.xml Wed Jun 15 00:14:47 2005
@@ -352,7 +352,7 @@
Most SQL systems, for example, have a dedicated server
process that mediates all access to tables. If a program
accessing the database crashes for some reason, the database
- daemon notices the lost connection and clean up any mess
+ daemon notices the lost connection and cleans up any mess
left behind. And because the database daemon is the only
process accessing the tables, applications don't need to
worry about permission conflicts. These things are not the
@@ -365,7 +365,7 @@
Other things can cause a repository to <quote>wedge</quote>
besides crashed processes, such as programs conflicting over
ownership and permissions on the database files. So while a
- BerkeleyDB repository is quite fast and scalable, it's best
+ Berkeley DB repository is quite fast and scalable, it's best
used by a single server process running as one
user—such as Apache's <command>httpd</command> or
<command>svnserve</command> (see <xref
@@ -413,7 +413,7 @@
checking out the latest tree is a bit slower than fetching
the fulltexts stored in a Berkeley DB HEAD revision. FSFS
also has a longer delay when finalizing a commit, which
- could in extreme cases cause clients to time-out when
+ could in extreme cases cause clients to time out when
waiting for a response.</para>
<para>The most important distinction, however, is FSFS's
More information about the svnbook-dev
mailing list