@@ -472,7 +472,7 @@ doc/src/sgml/pgprobackup.sgml
472472 </listitem >
473473 <listitem >
474474 <para >
475- <literal >backupdb</literal > — database usedused to connect to the
475+ <literal >backupdb</literal > — database used to connect to the
476476 <productname >PostgreSQL</productname > cluster.
477477 </para >
478478 </listitem >
@@ -1473,7 +1473,7 @@ GRANT SELECT ON TABLE pg_catalog.pg_database TO backup;
14731473 <title >Configuring the Remote Mode</title >
14741474 <para >
14751475 <application >pg_probackup</application > supports the remote mode that
1476- allows to perform backup, restore and WAL archiving operations remotely.
1476+ allowsyou to perform backup, restore and WAL archiving operations remotely.
14771477 In this mode, the backup catalog is stored on a local system, while
14781478 <productname >PostgreSQL</productname > instance to backup and/or to restore
14791479 is located on a remote system. Currently the only supported remote
@@ -1556,7 +1556,7 @@ GRANT SELECT ON TABLE pg_catalog.pg_database TO backup;
15561556 Make sure <application >pg_probackup</application > on <literal >postgres_host</literal >
15571557 can be located when a connection via SSH is made. For example, for <application >Bash</application >, you can
15581558 modify <literal >PATH</literal > in <filename >~/.bashrc</filename > of the <literal >postgres</literal > user
1559- (above the line in <filename >bashrc</filename >which exits the script for non-interactive shells).
1559+ (above the line in <filename >bashrc</filename >that exits the script for non-interactive shells).
15601560 Alternatively, for <application >pg_probackup</application > commands, specify the path to the directory
15611561 containing the <application >pg_probackup</application > binary on <literal >postgres_host</literal > via
15621562 the <link linkend =" pbk-remote-server-opts" link > option.
@@ -2188,7 +2188,7 @@ pg_probackup restore -B <replaceable>backup_dir</replaceable> --instance <replac
21882188 <listitem >
21892189 <para >
21902190 LSN — read the <replaceable >pg_control</replaceable > in the
2191- data directory to obtain redo LSN and redo TLI, which allows
2191+ data directory to obtain redo LSN and redo TLI, which allows you
21922192 to determine a point in history(shiftpoint), where data directory
21932193 state shifted from target backup chain history. If shiftpoint is not within
21942194 reach of backup chain history, then restore is aborted.
@@ -2417,7 +2417,7 @@ pg_probackup restore -B <replaceable>backup_dir</replaceable> --instance <replac
24172417 <refsect2 id =" pbk-remote-backup"
24182418 <title >Using <application >pg_probackup</application > in the Remote Mode</title >
24192419 <para >
2420- <application >pg_probackup</application > supports the remote mode that allows to perform
2420+ <application >pg_probackup</application > supports the remote mode that allowsyou to perform
24212421 <literal >backup</literal > and <literal >restore</literal >
24222422 operations remotely via SSH. In this mode, the backup catalog is
24232423 stored on a local system, while <productname >PostgreSQL</productname > instance to be backed
@@ -3782,7 +3782,7 @@ pg_probackup merge -B <replaceable>backup_dir</replaceable> --instance <replacea
37823782 between them. Once the merge is complete, the full backup takes in all
37833783 the merged data, and the incremental backups are removed as redundant.
37843784 Thus, the merge operation is virtually equivalent to retaking a full
3785- backup and removing all the outdated backups, but it allows to save much
3785+ backup and removing all the outdated backups, but it allowsyou to save much
37863786 time, especially for large data volumes, as well as I/O and network
37873787 traffic if you are using <application >pg_probackup</application > in the
37883788 <link linkend =" pbk-remote-backup" link > mode.