@@ -4055,10 +4055,10 @@ pg_probackup archive-push -B <replaceable>backup_dir</replaceable> --instance <r
40554055 corruption.
40564056 </para >
40574057 <para >
4058- To speed up archiving, you can specify the <option >-j </option > option
4059- torun < command >archive-push</ command > on multiple threads .
4060- Ifyou provide the <option >--batch-size</option > option, WAL files
4061- will be copied in batches ofthe specified size .
4058+ To speed up archiving, you can specify the <option >--batch-size </option > option
4059+ tocopy WAL segments in batches of the specified size .
4060+ If <option >--batch-size</option > option is used, then you can also specify
4061+ the < option >-j</ option > option to copy the batch ofWAL segments on multiple threads .
40624062 </para >
40634063 <para >
40644064 WAL segments copied to the archive are synced to disk unless
@@ -4096,10 +4096,10 @@ pg_probackup archive-get -B <replaceable>backup_dir</replaceable> --instance <re
40964096 </para >
40974097
40984098 <para >
4099- To speed up recovery, you can specify the <option >-j </option > option
4100- torun < command >archive-get</ command > on multiple threads .
4101- Ifyou provide the <option >--batch-size</option > option, WAL segments
4102- will be copied in batches ofthe specified size .
4099+ To speed up recovery, you can specify the <option >--batch-size </option > option
4100+ tocopy WAL segments in batches of the specified size .
4101+ If <option >--batch-size</option > option is used, then you can also specify
4102+ the < option >-j</ option > option to copy the batch ofWAL segments on multiple threads .
41034103 </para >
41044104
41054105 <para >