diff --git a/gpdb-doc/dita/ref_guide/sql_commands/COPY.xml b/gpdb-doc/dita/ref_guide/sql_commands/COPY.xml
index fa4b81dee6baf4e47de6ac4c2ac6f367570c0022..4b8af30b0e7814c51368489776f73f0a599a89fd 100644
--- a/gpdb-doc/dita/ref_guide/sql_commands/COPY.xml
+++ b/gpdb-doc/dita/ref_guide/sql_commands/COPY.xml
@@ -400,13 +400,13 @@ COPY {table [(<varname>column</varname> [, ...])] | (<varname>query</varname>)}
         with the <codeph>COPY TO</codeph> command. The <codeph>COPY</codeph> command might return
         table distribution policy errors, if you attempt to restore table data and the table
         distribution policy was changed after the <codeph>COPY FROM...ON SEGMENT</codeph> was
-        run.</p><note>If you run <codeph>COPY FROM...ON SEGMENT</codeph>and the server configuration
-        parameter <codeph>gp_enable_segment_copy_checking</codeph> is <codeph>false</codeph>, manual
-        redistribution of table data might be required. See the <codeph>ALTER TABLE</codeph> clause
-          <codeph>WITH REORGANIZE</codeph>.</note><p>When you specify the <codeph>LOG
-          ERRORS</codeph> clause, Greenplum Database captures errors that occur while reading the
-        external table data. You can view and manage the captured error log data. </p><ul
-        id="ul_wk3_jdj_bp">
+        run.</p><note>If you run <codeph>COPY FROM...ON SEGMENT</codeph> and the server
+        configuration parameter <codeph>gp_enable_segment_copy_checking</codeph> is
+          <codeph>false</codeph>, manual redistribution of table data might be required. See the
+          <codeph>ALTER TABLE</codeph> clause <codeph>WITH REORGANIZE</codeph>.</note><p>When you
+        specify the <codeph>LOG ERRORS</codeph> clause, Greenplum Database captures errors that
+        occur while reading the external table data. You can view and manage the captured error log
+        data. </p><ul id="ul_wk3_jdj_bp">
         <li>Use the built-in SQL function
             <codeph>gp_read_error_log('<varname>table_name</varname>')</codeph>. It requires
             <codeph>SELECT</codeph> privilege on <varname>table_name</varname>. This example