aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMagnus Hagander <magnus@hagander.net>2014-03-25 11:16:57 +0100
committerMagnus Hagander <magnus@hagander.net>2014-03-25 11:16:57 +0100
commit36f7c3a1e019d16a83a363958c3f3927692821d9 (patch)
tree1c3b579d7eb4d3a7c4ed070ed5f689a4aaa6bd11
parent6c5ced1526b189ed98baa0d195a7078d1afd112e (diff)
downloadpostgresql-36f7c3a1e019d16a83a363958c3f3927692821d9.tar.gz
postgresql-36f7c3a1e019d16a83a363958c3f3927692821d9.zip
Fix typos in pg_basebackup documentation
Joshua Tolley
-rw-r--r--doc/src/sgml/ref/pg_basebackup.sgml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/ref/pg_basebackup.sgml b/doc/src/sgml/ref/pg_basebackup.sgml
index ede68db9388..6ce0c8c387f 100644
--- a/doc/src/sgml/ref/pg_basebackup.sgml
+++ b/doc/src/sgml/ref/pg_basebackup.sgml
@@ -41,9 +41,9 @@ PostgreSQL documentation
<para>
<application>pg_basebackup</application> makes a binary copy of the database
- cluster files, while making sure the system is automatically put in and
+ cluster files, while making sure the system is put in and
out of backup mode automatically. Backups are always taken of the entire
- database cluster, it is not possible to back up individual databases or
+ database cluster; it is not possible to back up individual databases or
database objects. For individual database backups, a tool such as
<xref linkend="APP-PGDUMP"> must be used.
</para>