Author: depesz
Date: 2011-01-14 16:58:42 -0500 (Fri, 14 Jan 2011)
New Revision: 216

Modified:
   trunk/omnipitr/doc/omnipitr-backup-master.pod
   trunk/omnipitr/doc/omnipitr-backup-slave.pod
Log:
fix language

Modified: trunk/omnipitr/doc/omnipitr-backup-master.pod
===================================================================
--- trunk/omnipitr/doc/omnipitr-backup-master.pod	2011-01-14 21:51:17 UTC (rev 215)
+++ trunk/omnipitr/doc/omnipitr-backup-master.pod	2011-01-14 21:58:42 UTC (rev 216)
@@ -296,15 +296,15 @@
 
 =head2 TABLESPACES
 
-If I<omnipitr-backup-master> will detect additional tablespaces, they will be
+If I<omnipitr-backup-master> detects additional tablespaces, they will be
 also compressed to generated tarball.
 
-Since full path to tablespace directory is important, and should be preserved,
+Since the full path to the tablespace directory is important, and should be preserved,
 and normally tar doesn't let you store files which path starts with "/" (as it
-would be dangerous), I<omnipitr-backup-master> uses following approach:
+would be dangerous), I<omnipitr-backup-master> uses the following approach:
 
 all tablespaces will be stored in tar, and upon extraction they will be put in
-directory "tablespaces", and under it - there will be full path to tablespace
+the directory "tablespaces", and under it - there will be the full path to the tablespace
 directory.
 
 For example:
@@ -342,7 +342,7 @@
 
 Thanks to this approach, if you'll create symlink "tablespaces" pointing to root
 directory (I<ln -s / tablespaces>) B<before> exploding tarball - all tablespace
-files will be created already in correct places. This is of course not
+files will be created already in the correct places. This is of course not
 necessary, but will help if you'd ever need to recover from such backup.
 
 =head2 EXAMPLES

Modified: trunk/omnipitr/doc/omnipitr-backup-slave.pod
===================================================================
--- trunk/omnipitr/doc/omnipitr-backup-slave.pod	2011-01-14 21:51:17 UTC (rev 215)
+++ trunk/omnipitr/doc/omnipitr-backup-slave.pod	2011-01-14 21:58:42 UTC (rev 216)
@@ -277,15 +277,15 @@
 
 =head2 TABLESPACES
 
-If I<omnipitr-backup-master> will detect additional tablespaces, they will be
+If I<omnipitr-backup-master> detects additional tablespaces, they will be
 also compressed to generated tarball.
 
-Since full path to tablespace directory is important, and should be preserved,
+Since the full path to the tablespace directory is important, and should be preserved,
 and normally tar doesn't let you store files which path starts with "/" (as it
-would be dangerous), I<omnipitr-backup-master> uses following approach:
+would be dangerous), I<omnipitr-backup-master> uses the following approach:
 
 all tablespaces will be stored in tar, and upon extraction they will be put in
-directory "tablespaces", and under it - there will be full path to tablespace
+the directory "tablespaces", and under it - there will be the full path to the tablespace
 directory.
 
 For example:
@@ -323,7 +323,7 @@
 
 Thanks to this approach, if you'll create symlink "tablespaces" pointing to root
 directory (I<ln -s / tablespaces>) B<before> exploding tarball - all tablespace
-files will be created already in correct places. This is of course not
+files will be created already in the correct places. This is of course not
 necessary, but will help if you'd ever need to recover from such backup.
 
 =head2 EXAMPLES