DOC: replaced remaining instances of slave with standby

Author: Liudmila Mantrova

doc/src/sgml/intro.sgml

@@ -255,7 +255,7 @@
       <simpara>Lazy placement of temporary tables on disk</simpara>
     </listitem>
     <listitem>
-      <simpara>Consistent read on slaves (wait for WAL apply, see <xref linkend="sql-waitlsn">)</simpara>
+      <simpara>Consistent read on standby servers (wait for WAL apply, see <xref linkend="sql-waitlsn">)</simpara>
     </listitem>
     <listitem>
       <simpara>Utility <link linkend="app-pgrepack"><application>pg_repack</application></link> has been added</simpara>

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

@@ -829,7 +829,7 @@
     <para>Lazy placement of temporary tables on disk</para>
     </listitem>
     <listitem>
-    <para>Consistent read on slaves (wait for WAL apply, see <xref linkend="sql-waitlsn">)</para>
+    <para>Consistent read on standby servers (wait for WAL apply, see <xref linkend="sql-waitlsn">)</para>
     </listitem>
     <listitem>
     <para>Utility <application>pg_repack</application> has been added (See <xref linkend="app-pgrepack">)</para>

doc/src/sgml/runtime.sgml

@@ -2674,8 +2674,8 @@ pg_dump <replaceable>dbname</> -h <replaceable>hostname</> > db.sql
    </sect2>
 
    <sect2>
-   <title>Using <acronym>RDMA</acronym> for Master-Slave Replication</title>
-   <para>To enable master-slave replication over <acronym>RDMA</acronym> connections via <literal>rsocket</literal>, you need to configure master and slave nodes. For example, to allow client connections to the server 172.17.3.21 from 172.17.3.0/24 addresses on behalf of the <literal>postgres</> user, follow the steps below:</para>
+   <title>Using <acronym>RDMA</acronym> for Master-Standby Replication</title>
+   <para>To enable master-standby replication over <acronym>RDMA</acronym> connections via <literal>rsocket</literal>, you need to configure master and standby nodes. For example, to allow client connections to the server 172.17.3.21 from 172.17.3.0/24 addresses on behalf of the <literal>postgres</> user, follow the steps below:</para>
 
        <para><emphasis role="strong">To set up the master node for replication over <acronym>RDMA</acronym> connections via <literal>rsocket</literal>:</emphasis>
        </para>
@@ -2715,7 +2715,7 @@ LOG:  disconnection: session time: 0:00:00.622 user=postgres database= host=172.
 </para>
 </tip>
 
-       <para><emphasis role="strong">To set up the slave node:</emphasis>
+       <para><emphasis role="strong">To set up the standby node:</emphasis>
        </para>
        <orderedlist>
          <listitem>
@@ -2730,7 +2730,7 @@ export WITH_RSOCKET=true
            <programlisting>
 pg_basebackup -D <replaceable>datadir</> -x -R -h 172.17.3.21 -U postgres
 </programlisting>
-All the data appears on the slave node under the specified <replaceable>datadir</> directory.
+All the data appears on the standby node under the specified <replaceable>datadir</> directory.
            </para>
          </listitem>
          <listitem>
@@ -2750,7 +2750,7 @@ listen_rdma_addresses = ''
          </listitem>
        </orderedlist>
 
-<para>Once the setup is complete, start the slave node. The streaming replication is now performed over the <acronym>RDMA</acronym> connections using <literal>rsocket</literal> API.</para>
+<para>Once the setup is complete, start the standby node. The streaming replication is now performed over the <acronym>RDMA</acronym> connections using <literal>rsocket</literal> API.</para>
 
    </sect2>