Docs: Fix typo postgres.conf -> postgresql.conf

gpdb-doc/dita/admin_guide/managing/gpcopy-migrate.xml

@@ -16,7 +16,7 @@
       schema, table data, indexes, views, roles, user-defined functions, resource queues, and
       resource groups. If a copied table or database does not exist in the destination cluster,
         <codeph>gpcopy</codeph> creates it automatically, along with indexes as necessary.</p>
-    <p>Configuration files, including <codeph>postgres.conf</codeph> and
+    <p>Configuration files, including <codeph>postgresql.conf</codeph> and
         <codeph>pg_hba.conf</codeph>, must be transferred manually by an administrator. Extensions
       installed in the database with <codeph>gppkg</codeph>, such as MADlib and programming language
       extensions, must be installed in the destination database by an administrator. </p>

gpdb-doc/dita/utility_guide/admin_utilities/gptransfer.xml

@@ -159,7 +159,7 @@
                     <codeph>gptransfer</codeph> command line increases the <codeph>gpfdist</codeph>
                 logging level.</p>
             <p>The <codeph>gptransfer</codeph> utility does not move configuration files such as
-                    <codeph>postgres.conf</codeph> and <codeph>pg_hba.conf</codeph>. You must set up
+                    <codeph>postgresql.conf</codeph> and <codeph>pg_hba.conf</codeph>. You must set up
                 the destination system configuration separately. </p>
             <p>The <codeph>gptransfer</codeph> utility does not move external objects such as
                 Greenplum Database extensions, third party jar files, and shared object files. You