Skip to content

Rm extra comma #1673

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 4 commits into from
Closed

Rm extra comma #1673

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3dff2b7
Rm extra comma
stbrody Mar 20, 2014
c3d9067
Rm another extra comma
stbrody Mar 20, 2014
b50df84
owns->own
stbrody Mar 20, 2014
1a86c34
Small grammar fixes
stbrody Mar 20, 2014
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions source/tutorial/perform-two-phase-commits.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -275,7 +275,7 @@ the following:
Recovering from Failure Scenarios
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The most important part of the transaction procedure is not, the
The most important part of the transaction procedure is not the
prototypical example above, but rather the possibility for recovering
from the various failure scenarios when transactions do not complete
as intended. This section will provide an overview of possible
Expand Down Expand Up @@ -309,7 +309,7 @@ recovery operations every time the application starts to catch any
unfinished transactions. You may also wish run the recovery operation
at regular intervals to ensure that your data remains consistent.

The time required to reach a consistent state depends, on how long the
The time required to reach a consistent state depends on how long the
application needs to recover each transaction.

.. _2-phase-commits-rollback:
Expand Down Expand Up @@ -438,7 +438,7 @@ before applying the transaction.

If the application ``A1`` fails during transaction execution, you can
use the :ref:`recovery procedures <2-phase-commits-recovery>`, but
applications should ensure that they "owns" the transaction before
applications should ensure that they "own" the transaction before
applying the transaction. For example to resume pending jobs, use a
query that resembles the following:

Expand All @@ -461,13 +461,13 @@ Using Two-Phase Commits in Production Applications
The example transaction above is intentionally simple. For example, it
assumes that:

- it is always possible roll back operations an account.
- it is always possible to roll back operations an account.

- account balances can hold negative values.

Production implementations would likely be more complex. Typically
accounts need to information about current balance, pending credits,
pending debits. Then:
accounts need information about current balance, pending credits,
pending debits, etc. Then:

- when your application :ref:`switches the transaction state to
pending <2-phase-commits-step-2>` (i.e. step 2) it would also make
Expand Down