@@ -39,16 +39,16 @@ PostgreSQL documentation
3939 <application>pg_checksums</application> checks, enables or disables data
4040 checksums in a <productname>PostgreSQL</productname> cluster. The server
4141 must be shut down cleanly before running
42- <application>pg_checksums</application>.The exit status is zero if there
43- are no checksum errors when checking them , and nonzero if at least one
44- checksum failure is detected.If enabling or disabling checksums, the
42+ <application>pg_checksums</application>.When verifying checksums, the exit
43+ status is zero if there are no checksum errors, and nonzero if at least one
44+ checksum failure is detected.When enabling or disabling checksums, the
4545 exit status is nonzero if the operation failed.
4646 </para>
4747
4848 <para>
49- While checking or enabling checksums needs to scan or write every file in
50- the cluster, disabling checksums will only update the file
51- <filename>pg_control</filename>.
49+ When verifying checksums, every file in the cluster is scanned. When
50+ enabling checksums, every file in the cluster is rewritten. Disabling
51+ checksums only updates the file <filename>pg_control</filename>.
5252 </para>
5353 </refsect1>
5454
@@ -218,10 +218,9 @@ PostgreSQL documentation
218218 </para>
219219 <para>
220220 If <application>pg_checksums</application> is aborted or killed while
221- enabling or disabling checksums, the cluster will keep the same
222- configuration for data checksums as before the operation attempted.
223- <application>pg_checksums</application> can be restarted to
224- attempt again the same operation.
221+ enabling or disabling checksums, the cluster's data checksum configuration
222+ remains unchanged, and <application>pg_checksums</application> can be
223+ re-run to perform the same operation.
225224 </para>
226225 </refsect1>
227226</refentry>