@@ -924,16 +924,17 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
924924 Promoting a cascading standby terminates the immediate downstream replication
925925 connections which it serves. This is because the timeline becomes different
926926 between standbys, and they can no longer continue replication. The
927- effected standby(s) may reconnect to reestablish streaming replication.
927+ affected standby(s) may reconnect to reestablish streaming replication.
928928 </para>
929929
930930 <para>
931931 To use cascading replication, set up the cascading standby so that it can
932- accept replication connections, i.e., set <varname>max_wal_senders</>,
933- <varname>hot_standby</> and authentication option (see
934- <xref linkend="streaming-replication"> and <xref linkend="hot-standby">).
935- Also set <varname>primary_conninfo</> in the downstream standby to point
936- to the cascading standby.
932+ accept replication connections (that is, set
933+ <xref linkend="guc-max-wal-senders"> and <xref linkend="guc-hot-standby">,
934+ and configure
935+ <link linkend="auth-pg-hba-conf">host-based authentication</link>).
936+ You will also need to set <varname>primary_conninfo</> in the downstream
937+ standby to point to the cascading standby.
937938 </para>
938939 </sect2>
939940