[jboss-svn-commits] JBL Code SVN: r35418 - labs/jbosstm/trunk/ArjunaCore/docs/ArjunaCore_Administration_Guide/en-US.

[jboss-svn-commits at lists.jboss.org]

Author: misty at redhat.com
Date: 2010-10-04 23:06:08 -0400 (Mon, 04 Oct 2010)
New Revision: 35418

Modified:
   labs/jbosstm/trunk/ArjunaCore/docs/ArjunaCore_Administration_Guide/en-US/Failure_Recovery_Administration.xml
   labs/jbosstm/trunk/ArjunaCore/docs/ArjunaCore_Administration_Guide/en-US/ObjectStore_Management.xml
   labs/jbosstm/trunk/ArjunaCore/docs/ArjunaCore_Administration_Guide/en-US/Starting_And_Stopping_Transaction_Manager.xml
Log:
Spell-checking and last minute changes, as well as fixing the revision history.

Modified: labs/jbosstm/trunk/ArjunaCore/docs/ArjunaCore_Administration_Guide/en-US/Failure_Recovery_Administration.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/docs/ArjunaCore_Administration_Guide/en-US/Failure_Recovery_Administration.xml	2010-10-05 01:16:13 UTC (rev 35417)
+++ labs/jbosstm/trunk/ArjunaCore/docs/ArjunaCore_Administration_Guide/en-US/Failure_Recovery_Administration.xml	2010-10-05 03:06:08 UTC (rev 35418)
@@ -43,7 +43,7 @@
     </screen>
     <para>
       If the <parameter>-test</parameter> flag is used with the Recovery Manager then it will display a
-      <literal>Ready</literal> message when initialised, i.e.,
+      <literal>Ready</literal> message when initialized, i.e.,
     </para>
     <screen>
       <command>java com.arjuna.ats.arjuna.recovery.RecoveryManager -test</command>
@@ -143,7 +143,7 @@
     </para>
     <note>
       <para>
-        In previous versions of <application>ArjunaCore</application>, there was no contact mechanism, and the backoff
+        In previous versions of <application>ArjunaCore</application>, there was no contact mechanism, and the back-off
         period needed to be long enough to avoid catching transactions in flight at all. From 3.0, there is no such
         risk.
       </para>

Modified: labs/jbosstm/trunk/ArjunaCore/docs/ArjunaCore_Administration_Guide/en-US/ObjectStore_Management.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/docs/ArjunaCore_Administration_Guide/en-US/ObjectStore_Management.xml	2010-10-05 01:16:13 UTC (rev 35417)
+++ labs/jbosstm/trunk/ArjunaCore/docs/ArjunaCore_Administration_Guide/en-US/ObjectStore_Management.xml	2010-10-05 03:06:08 UTC (rev 35418)
@@ -15,7 +15,7 @@
     However, if failures occur, transaction logs may remain in the object store until crash recovery facilities have
     resolved the transactions they represent. As such it is very important that the contents of the object store are not
     deleted without due care and attention, as this will make it impossible to resolve in doubt transactions. In
-    addition, if multiple users share the same object store it is important that they realise this and do not simply
+    addition, if multiple users share the same object store it is important that they realize this and do not simply
     delete the contents of the object store assuming it is an exclusive resource.
   </para>
 </chapter>

Modified: labs/jbosstm/trunk/ArjunaCore/docs/ArjunaCore_Administration_Guide/en-US/Starting_And_Stopping_Transaction_Manager.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/docs/ArjunaCore_Administration_Guide/en-US/Starting_And_Stopping_Transaction_Manager.xml	2010-10-05 01:16:13 UTC (rev 35417)
+++ labs/jbosstm/trunk/ArjunaCore/docs/ArjunaCore_Administration_Guide/en-US/Starting_And_Stopping_Transaction_Manager.xml	2010-10-05 03:06:08 UTC (rev 35418)
@@ -26,7 +26,7 @@
     reaper (see the Programmers Guide for information about what the reaper does.) In order to do this you may want to
     first prevent the creation of new transactions (if you are not creating transactions with timeouts then this step is
     not necessary) using method <methodname>TxControl.disable</methodname>. Then you should call method
-    <methodname>TransactionReaper.terminate</methodname>. This method takes a boolean parameter: if
+    <methodname>TransactionReaper.terminate</methodname>. This method takes a Boolean parameter: if
     <literal>true</literal> then the method will wait for the normal timeout periods associated with any transactions to
     expire before terminating the transactions; if <methodname>false</methodname> then transactions will be forced to
     terminate (rollback or have their outcome set such that they can only ever rollback) immediately.