From 5478f991c9f73066d27d75b31876f9977af61db5 Mon Sep 17 00:00:00 2001
From: Itagaki Takahiro <itagaki.takahiro@gmail.com>
Date: Thu, 10 Feb 2011 10:58:18 +0900
Subject: [PATCH] Fix typo in the documentation.
by Kevin Grittner
---
doc/src/sgml/mvcc.sgml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
index c5d33091001..f42bb091c13 100644
--- a/doc/src/sgml/mvcc.sgml
+++ b/doc/src/sgml/mvcc.sgml
@@ -604,7 +604,7 @@ ERROR: could not serialize access due to read/write dependencies among transact
Consistent use of Serializable transactions can simplify development.
The guarantee that any set of concurrent serializable transactions will
have the same effect as if they were run one at a time means that if
- you can demonstrate that a singe transaction, as written, will do the
+ you can demonstrate that a single transaction, as written, will do the
right thing when run by itself, you can have confidence that it will
do the right thing in any mix of serializable transactions, even without
any information about what those other transactions might do. It is
--
GitLab