RRR topics support follower fetching (#755)

modules/develop/pages/consume-data/follower-fetching.adoc

@@ -12,7 +12,7 @@ Learn about follower fetching and how to configure a Redpanda consumer to fetch
 
 For a Redpanda cluster deployed across different data centers and availability zones (AZs), restricting a consumer to fetch only from the leader of a partition can incur greater costs and have higher latency than fetching from a follower that is geographically closer to the consumer.
 
-With follower fetching (proposed in {url-kip392}[KIP-392^]), the fetch protocol is extended to support a consumer fetching from any replica.
+With follower fetching (proposed in {url-kip392}[KIP-392^]), the fetch protocol is extended to support a consumer fetching from any replica. This includes xref:manage:remote-read-replicas.adoc[Remote Read Replicas].
 
 The first fetch from a consumer is processed by a Redpanda leader broker. The leader checks for a replica (itself or a follower) that has a rack ID that matches the consumer's rack ID. If a replica with a matching rack ID is found, the fetch request returns records from that replica. Otherwise, the fetch is handled by the leader.