[Doc]: Added fixes for RN and sr_plan.sgml

Author: dmpgpro

doc/src/sgml/release-pro-9.6.sgml

@@ -8,34 +8,37 @@
   </note>
   <sect2>
     <title>Overview</title>
-    <para>This release is based on <productname>PostgresPro</productname>
-      9.6.1.2 and <productname>PostgreSQL</productname> 9.6.2.</para>
+    <para>This release is based on <productname>Postgres Pro</productname>
+      <link linkend="release-pro-9-6-1-2">9.6.1.2</link> and
+      <productname>PostgreSQL</productname> <link linkend="release-9-6-2">9.6.2</link>.</para>
     <para>Major enhancements over <productname>Postgres Pro</productname>
       9.6.1.2 include:</para>
-    
+
     <itemizedlist>
       <listitem>
-        <para>Module <application>pg_pathman</application> has been updated to
-        version 1.3 (See <xref linkend="pg-pathman"> and <xref linkend="pg-pathman-how-to-update">).</para>
+        <para>Module <link linkend="pg-pathman"><application>pg_pathman</application></link> has been updated to
+        version 1.3 (see <xref linkend="pg-pathman-how-to-update">).</para>
       </listitem>
       <listitem>
-        <para>The <application>sr_plan</application> module is now initialized independently for each database instance (See <xref linkend="sr-plan">).</para>
+        <para>The <link linkend="sr-plan"><application>sr_plan</application></link> module
+        is now initialized independently for each database instance.</para>
       </listitem>
       <listitem>
-        <para>Applied fixes for covering indexes.</para>
+        <para>Applied fixes for covering indexes. Now the keyword <literal>INCLUDING</literal> is
+          replaced by <literal>INCLUDE</literal> (see <xref linkend="indexes-unique">).</para>
       </listitem>
       <listitem>
         <para>RHEL-based distributions are installed in a separate location,
-          so the product can be installed in parallel with an existing
-          <productname>PostgreSQL</productname>.</para>
+          so the <productname>Postgres Pro</productname> database can be installed in parallel with an existing
+          <productname>PostgreSQL</productname> database.</para>
       </listitem>
       <listitem>
         <para>Improved the algorithm of automatic TCP-port selection for the case
           of parallel installation of different versions of the product on
           Windows systems.</para>
       </listitem>
       <listitem>
-        <para>Updated the <application>pg_probackup</application> backup manager:</para>
+        <para>Updated the <link linkend="app-pgprobackup"><application>pg_probackup</application></link> backup manager:</para>
         <itemizedlist>
           <listitem>
             <para>
@@ -54,7 +57,7 @@
           <listitem>
             <para>
               Fixed <command>validate</command> command.
-              The <emphasis role="strong">backup_id</emphasis> parameter is
+              The <replaceable>backup_id</replaceable> parameter is
               optional now.
             </para>
           </listitem>
@@ -95,8 +98,9 @@
   </note>
   <sect2>
     <title>Overview</title>
-    <para>This release is based on <productname>PostgresPro</productname>
-      9.6.1.1 and upstream PostgreSQL patches.</para>
+    <para>This release is based on <productname>Postgres Pro</productname>
+      <link linkend="release-pro-9-6-1-1">9.6.1.1</link> and upstream PostgreSQL patches.
+    </para>
     <para>Major enhancements over <productname>Postgres Pro</productname>
       9.6.1.1 include:</para>
 
@@ -133,7 +137,7 @@
     <itemizedlist>
       <listitem><para><application>pg_pathman</application> to version 1.2.2 (See <xref linkend="pg-pathman">)</para></listitem>
     </itemizedlist>
-    
+
     <para>
       Backup manager <application>pg_arman</application> has been replaced
       to <application>pg_probackup</application> (Version 1.0).
@@ -148,7 +152,7 @@
     <para>A dump/restore is not required for those running 9.6.1.1.</para>
     <para>However, if you are upgrading from vanilla PostgreSQL 9.6.x, some
       catalog changes should be applied.
-    </para>    
+    </para>
     <para>If you use binary packages, and your database is in the default
       location, this upgrade should be performed automatically. If you've
       compiled Postgres Pro from source or create your database in
@@ -172,9 +176,9 @@
   <sect2>
     <title>Overview</title>
     <para>This release is based on <productname>PostgreSQL</productname>
-      9.6.1</para>
+      <link linkend="release-9-6-1">9.6.1</link>.</para>
     <para>Major enhancements over <productname>Postgres Pro</productname>
-      9.6.0.1 include:</para>
+      <link linkend="release-pro-9-6-0-1">9.6.0.1</link> include:</para>
     <para>Added fix for <application>pg_buffercache</application> module,
       which improves database response in the case of connected
       monitoring tools.</para>
@@ -192,7 +196,7 @@
     <para>A dump/restore is not required for those running 9.6.0.1.</para>
     <para>However, if you are upgrading from vanilla PostgreSQL 9.6.x, some
       catalog changes should be applied.
-    </para>    
+    </para>
     <para>If you use binary packages, and your database is in the default
       location, this upgrade should be performed automatically. If you've
       compiled Postgres Pro from source or create your database in
@@ -216,7 +220,7 @@
   <sect2>
     <title>Overview</title>
     <para>This release is based on <productname>PostgreSQL</productname>
-      9.6.0</para>
+      <link linkend="release-9-6">9.6.0</link>.</para>
     <para>Major enhancements over <productname>PostgreSQL</productname>
       9.6.0 include:</para>
     <para>Core patches from Postgres Pro 9.5 has been applied:</para>
@@ -248,7 +252,7 @@
       <listitem>
         <para><application>pg_arman</application></para>
       </listitem>
-    </itemizedlist>    
+    </itemizedlist>
   </sect2>
   <sect2>
     <title>Migration to Version 9.6.0.1</title>
@@ -262,15 +266,15 @@
 
     <para>When upgrading from previous releases of Postgres Pro or from
       vanilla PostgreSQL 9.6.x, some catalog changes should be applied.</para>
-    
+
     <para>If you use binary packages, and your database is in the default
       location, this upgrade should be performed automatically. If you've
       compiled Postgres Pro from source or create your database in
       non-default location, running <literal>initdb</literal> manually, you
       should run <literal>pgpro_upgrade</literal> script provided in this
       distribution.
     </para>
-    
+
     <para>Before running script, you should stop postgres service. Script
       should be run as user, owning the database (typically postgres) and
       PGDATA environment variable should be set to the directory where

doc/src/sgml/sr_plan.sgml

@@ -1,6 +1,6 @@
 <!-- doc/src/sgml/sr_plan.sgml -->
 
-<sect1 id="sr-plan" xreflabel="sr-plan">
+<sect1 id="sr-plan" xreflabel="sr_plan">
   <title>sr_plan</title>
   <indexterm zone="sr-plan">
   <primary>sr_plan</primary>