Link to new stream client connection guide

Author: acogoluegnes

docs/clustering.md

@@ -56,7 +56,7 @@ After cluster formation, all nodes in a cluster are aware of other cluster membe
 
 Client applications can be aware or not be aware of the fact that there are multiple cluster nodes,
 and connect to any of them, or, depending on the protocol used, a subset of them. For example,
-RabbitMQ Stream Protocol clients [can connect to multiple nodes at once](https://www.rabbitmq.com/blog/2021/07/23/connecting-to-streams).
+RabbitMQ Stream Protocol clients [can connect to multiple nodes at once](./stream-connections).
 This is covered in more details [later in this guide](#clustering-and-clients).
 
 
@@ -432,8 +432,7 @@ the target stream. The protocol includes a topology discovery operation, so well
 libraries will select one of the suitable nodes. This won't be the case when a load balancer is used,
 however.
 
-See [Connecting to Streams](/blog/2021/07/23/connecting-to-streams#well-behaved-clients)
-to learn more.
+See the [stream client connection guide](./stream-connections) to learn more.
 
 ### Queue and Stream Leader Replica Placement {#replica-placement}
 

docs/queues.md

@@ -377,7 +377,7 @@ for improved data locality.
 This general rule applies to all messaging data types supported by RabbitMQ except for one.
 [Streams](./streams) are an exception to this rule, and require clients, regardless of the protocol they use, to connect to a node
 that hosts a replica (a leader of rollower) of the target stream.
-Consequently, RabbitMQ Stream protocol clients will [connect to multiple nodes in parallel](https://www.rabbitmq.com/blog/2021/07/23/connecting-to-streams).
+Consequently, RabbitMQ Stream protocol clients will [connect to multiple nodes in parallel](./stream-connections).
 
 Queues can also be [federated](./federated-queues)
 across loosely coupled nodes or clusters.
@@ -405,7 +405,7 @@ for improved data locality.
 This general rule applies to all messaging data types supported by RabbitMQ except for one.
 [Streams](./streams) are an exception to this rule, and require clients, regardless of the protocol they use, to connect to a node
 that hosts a replica (a leader of rollower) of the target stream.
-Consequently, RabbitMQ Stream protocol clients will [connect to multiple nodes in parallel](https://www.rabbitmq.com/blog/2021/07/23/connecting-to-streams).
+Consequently, RabbitMQ Stream protocol clients will [connect to multiple nodes in parallel](./stream-connections).
 
 
 

docs/stream.md

@@ -207,7 +207,7 @@ stream.advertised_host = rabbitmq-1
 stream.advertised_port = 12345
 ```
 
-The [Connecting to Streams](/blog/2021/07/23/connecting-to-streams) blog post covers why the `advertised_host` and `advertised_port` settings are necessary in some deployments.
+The [stream client connection guide](./stream-connections) covers why the `advertised_host` and `advertised_port` settings are necessary in some deployments.
 
 The configuration entries have [TLS counterparts](#tls) (`advertised_tls_host` and `advertised_tls_port`).
 

versioned_docs/version-3.13/clustering.md

@@ -56,7 +56,7 @@ After cluster formation, all nodes in a cluster are aware of other cluster membe
 
 Client applications can be aware or not be aware of the fact that there are multiple cluster nodes,
 and connect to any of them, or, depending on the protocol used, a subset of them. For example,
-RabbitMQ Stream Protocol clients [can connect to multiple nodes at once](https://www.rabbitmq.com/blog/2021/07/23/connecting-to-streams).
+RabbitMQ Stream Protocol clients [can connect to multiple nodes at once](./stream-connections).
 This is covered in more details [later in this guide](#clustering-and-clients).
 
 
@@ -432,8 +432,7 @@ the target stream. The protocol includes a topology discovery operation, so well
 libraries will select one of the suitable nodes. This won't be the case when a load balancer is used,
 however.
 
-See [Connecting to Streams](/blog/2021/07/23/connecting-to-streams#well-behaved-clients)
-to learn more.
+See the [stream client connection guide](./stream-connections) to learn more.
 
 ### Queue and Stream Leader Replica Placement {#replica-placement}
 

versioned_docs/version-3.13/queues.md

@@ -372,7 +372,7 @@ for improved data locality.
 This general rule applies to all messaging data types supported by RabbitMQ except for one.
 [Streams](./streams) are an exception to this rule, and require clients, regardless of the protocol they use, to connect to a node
 that hosts a replica (a leader of rollower) of the target stream.
-Consequently, RabbitMQ Stream protocol clients will [connect to multiple nodes in parallel](https://www.rabbitmq.com/blog/2021/07/23/connecting-to-streams).
+Consequently, RabbitMQ Stream protocol clients will [connect to multiple nodes in parallel](./stream-connections).
 
 Queues can also be [federated](./federated-queues)
 across loosely coupled nodes or clusters.
@@ -400,7 +400,7 @@ for improved data locality.
 This general rule applies to all messaging data types supported by RabbitMQ except for one.
 [Streams](./streams) are an exception to this rule, and require clients, regardless of the protocol they use, to connect to a node
 that hosts a replica (a leader of rollower) of the target stream.
-Consequently, RabbitMQ Stream protocol clients will [connect to multiple nodes in parallel](https://www.rabbitmq.com/blog/2021/07/23/connecting-to-streams).
+Consequently, RabbitMQ Stream protocol clients will [connect to multiple nodes in parallel](./stream-connections).
 
 
 ## Time-to-Live and Length Limit {#ttl-and-limits}

versioned_docs/version-3.13/stream.md

@@ -207,7 +207,7 @@ stream.advertised_host = rabbitmq-1
 stream.advertised_port = 12345
 ```
 
-The [Connecting to Streams](/blog/2021/07/23/connecting-to-streams) blog post covers why the `advertised_host` and `advertised_port` settings are necessary in some deployments.
+The [stream client connection guide](./stream-connections) covers why the `advertised_host` and `advertised_port` settings are necessary in some deployments.
 
 The configuration entries have [TLS counterparts](#tls) (`advertised_tls_host` and `advertised_tls_port`).
 

versioned_docs/version-4.0/clustering.md

@@ -56,7 +56,7 @@ After cluster formation, all nodes in a cluster are aware of other cluster membe
 
 Client applications can be aware or not be aware of the fact that there are multiple cluster nodes,
 and connect to any of them, or, depending on the protocol used, a subset of them. For example,
-RabbitMQ Stream Protocol clients [can connect to multiple nodes at once](https://www.rabbitmq.com/blog/2021/07/23/connecting-to-streams).
+RabbitMQ Stream Protocol clients [can connect to multiple nodes at once](./stream-connections).
 This is covered in more details [later in this guide](#clustering-and-clients).
 
 
@@ -432,8 +432,7 @@ the target stream. The protocol includes a topology discovery operation, so well
 libraries will select one of the suitable nodes. This won't be the case when a load balancer is used,
 however.
 
-See [Connecting to Streams](/blog/2021/07/23/connecting-to-streams#well-behaved-clients)
-to learn more.
+See the [stream client connection guide](./stream-connections) to learn more.
 
 ### Queue and Stream Leader Replica Placement {#replica-placement}
 

versioned_docs/version-4.0/queues.md

@@ -377,7 +377,7 @@ for improved data locality.
 This general rule applies to all messaging data types supported by RabbitMQ except for one.
 [Streams](./streams) are an exception to this rule, and require clients, regardless of the protocol they use, to connect to a node
 that hosts a replica (a leader of rollower) of the target stream.
-Consequently, RabbitMQ Stream protocol clients will [connect to multiple nodes in parallel](https://www.rabbitmq.com/blog/2021/07/23/connecting-to-streams).
+Consequently, RabbitMQ Stream protocol clients will [connect to multiple nodes in parallel](./stream-connections).
 
 Queues can also be [federated](./federated-queues)
 across loosely coupled nodes or clusters.
@@ -405,7 +405,7 @@ for improved data locality.
 This general rule applies to all messaging data types supported by RabbitMQ except for one.
 [Streams](./streams) are an exception to this rule, and require clients, regardless of the protocol they use, to connect to a node
 that hosts a replica (a leader of rollower) of the target stream.
-Consequently, RabbitMQ Stream protocol clients will [connect to multiple nodes in parallel](https://www.rabbitmq.com/blog/2021/07/23/connecting-to-streams).
+Consequently, RabbitMQ Stream protocol clients will [connect to multiple nodes in parallel](./stream-connections).
 
 
 

versioned_docs/version-4.0/stream.md

@@ -207,7 +207,7 @@ stream.advertised_host = rabbitmq-1
 stream.advertised_port = 12345
 ```
 
-The [Connecting to Streams](/blog/2021/07/23/connecting-to-streams) blog post covers why the `advertised_host` and `advertised_port` settings are necessary in some deployments.
+The [stream client connection guide](./stream-connections) covers why the `advertised_host` and `advertised_port` settings are necessary in some deployments.
 
 The configuration entries have [TLS counterparts](#tls) (`advertised_tls_host` and `advertised_tls_port`).
 

versioned_docs/version-4.1/clustering.md

@@ -56,7 +56,7 @@ After cluster formation, all nodes in a cluster are aware of other cluster membe
 
 Client applications can be aware or not be aware of the fact that there are multiple cluster nodes,
 and connect to any of them, or, depending on the protocol used, a subset of them. For example,
-RabbitMQ Stream Protocol clients [can connect to multiple nodes at once](https://www.rabbitmq.com/blog/2021/07/23/connecting-to-streams).
+RabbitMQ Stream Protocol clients [can connect to multiple nodes at once](./stream-connections).
 This is covered in more details [later in this guide](#clustering-and-clients).
 
 
@@ -432,8 +432,7 @@ the target stream. The protocol includes a topology discovery operation, so well
 libraries will select one of the suitable nodes. This won't be the case when a load balancer is used,
 however.
 
-See [Connecting to Streams](/blog/2021/07/23/connecting-to-streams#well-behaved-clients)
-to learn more.
+See the [stream client connection guide](./stream-connections) to learn more.
 
 ### Queue and Stream Leader Replica Placement {#replica-placement}