Update FAQ_DEV.

diff --git a/doc/FAQ_DEV b/doc/FAQ_DEV
index 5f9f0788348de4088b231faba2d3341c4aee3c27..e8f046d0fa529a238cd6863f7bb213606ed6f2e8 100644 (file)
--- a/doc/FAQ_DEV
+++ b/doc/FAQ_DEV
@@ -426,4 +426,4 @@ c-mode)
    using a Command Counter. Incrementing the counter allows transactions
    to be broken into pieces so each piece can see rows modified by
    previous pieces. CommandCounterIncrement() increments the Command
-   Counter, creating a new piece of the transaction.
+   Counter, creating a new part of the transaction.

diff --git a/doc/src/FAQ/FAQ_DEV.html b/doc/src/FAQ/FAQ_DEV.html
index 4da26a9d3a2c67ad6aa18ad40b974b1da47f82a1..e62d0c3533acdb21b0b6b93688a6946236b5626b 100644 (file)
--- a/doc/src/FAQ/FAQ_DEV.html
+++ b/doc/src/FAQ/FAQ_DEV.html
@@ -482,7 +482,7 @@ appropriate values.  Hopefully, there is already locking code in
 There is a <I>backend/port</I> directory if you need special files for
 your OS.<P>
 
-<H3><a name="13">13</a>)   What is CommandCounterIncrement()?</H3><P>
+<H3><a name="13">13</a>) What is CommandCounterIncrement()?</H3><P>
 
 Normally, transactions can not see the rows they modify.  This allows <CODE>
 UPDATE foo SET x = x + 1</CODE> to work correctly. 
@@ -493,7 +493,7 @@ in previous parts of the transaction. This is accomplished using a
 Command Counter. Incrementing the counter allows transactions to be
 broken into pieces so each piece can see rows modified by previous
 pieces. <I>CommandCounterIncrement()</I> increments the Command
-Counter, creating a new piece of the transaction. <P>
+Counter, creating a new part of the transaction. <P>
 
 </BODY>
 </HTML>