From 1b5cd6dcdc6b8447920cb4db7c13dbf451353477 Mon Sep 17 00:00:00 2001
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
Date: Sat, 15 Oct 2005 01:15:33 +0000
Subject: [PATCH] Fix typo.

---
 doc/src/sgml/backup.sgml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 4dbeae9fd6..f4dc252780 100644
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.70 2005/10/13 17:32:42 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.71 2005/10/15 01:15:33 alvherre Exp $
 -->
 <chapter id="backup">
  <title>Backup and Restore</title>
@@ -722,7 +722,7 @@ SELECT pg_stop_backup();
     segments with names numerically less are no longer needed to recover
     the file system backup and may be deleted. However, you should
     consider keeping several backup sets to be absolutely certain that
-    you are can recover your data. Keep in mind that only completed WAL
+    you can recover your data. Keep in mind that only completed WAL
     segment files are archived, so there will be delay between running
     <function>pg_stop_backup</> and the archiving of all WAL segment
     files needed to make the file system backup consistent.
-- 
2.40.0