From b87b2f4bda1a3b98f8dea867b8bc419ace7a9ea9 Mon Sep 17 00:00:00 2001
From: Peter Eisentraut <peter_e@gmx.net>
Date: Sat, 23 Apr 2016 14:48:02 -0400
Subject: [PATCH] doc: Fix typos
From: Erik Rijkers <er@xs4all.nl>
---
doc/src/sgml/ref/pgbench.sgml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/src/sgml/ref/pgbench.sgml b/doc/src/sgml/ref/pgbench.sgml
index 06cd5db32ed..a6c69ff344d 100644
--- a/doc/src/sgml/ref/pgbench.sgml
+++ b/doc/src/sgml/ref/pgbench.sgml
@@ -1174,7 +1174,7 @@ END;
0 84 4142 0 1412881037 918023 2333
0 85 2465 0 1412881037 919759 740
</screen>
- In this example, transaction 82 was late, because it's latency (6.173 ms) was
+ In this example, transaction 82 was late, because its latency (6.173 ms) was
over the 5 ms limit. The next two transactions were skipped, because they
were already late before they were even started.
</para>
@@ -1215,7 +1215,7 @@ END;
</para>
<para>
- Here is example outputs:
+ Here is example output:
<screen>
1345828501 5601 1542744 483552416 61 2573
1345828503 7884 1979812 565806736 60 1479
@@ -1225,8 +1225,8 @@ END;
</screen></para>
<para>
- Notice that while the plain (unaggregated) log file contains index
- of the custom script files, the aggregated log does not. Therefore if
+ Notice that while the plain (unaggregated) log file contains a reference
+ to the custom script files, the aggregated log does not. Therefore if
you need per script data, you need to aggregate the data on your own.
</para>
--
GitLab