Update URL to blog posts

Author: acogoluegnes

src/docs/asciidoc/api.adoc

@@ -75,7 +75,7 @@ Creating the environment to connect to a cluster node works usually seamlessly.
 Creating publishers and consumers can cause problems as the client uses hints from the cluster to find the nodes where stream leaders and replicas are located to connect to the appropriate nodes.
 
 These connection hints can be accurate or less appropriate depending on the infrastructure.
-If you hit some connection problems at some point – like hostnames impossible to resolve for client applications - this https://blog.rabbitmq.com/posts/2021/07/connecting-to-streams/[blog post] should help you understand what is going on and fix the issues.
+If you hit some connection problems at some point – like hostnames impossible to resolve for client applications - this https://www.rabbitmq.com/blog/2021/07/23/connecting-to-streams[blog post] should help you understand what is going on and fix the issues.
 
 To make the local development experience simple, the client library can choose to always use `localhost` for producers and consumers.
 This happens if the following conditions are met: the initial host to connect to is `localhost`, the user is `guest`, and no custom address resolver has been provided.
@@ -275,7 +275,7 @@ It is the developer's responsibility to close the `EventLoopGroup` they provide.
 ==== When a Load Balancer is in Use
 
 A load balancer can misguide the client when it tries to connect to nodes that host stream leaders and replicas.
-The https://blog.rabbitmq.com/posts/2021/07/connecting-to-streams/["Connecting to Streams"] blog post covers why client applications must connect to the appropriate nodes in a cluster and how a https://blog.rabbitmq.com/posts/2021/07/connecting-to-streams/#with-a-load-balancer[load balancer can make things complicated] for them.
+The https://www.rabbitmq.com/blog/2021/07/23/connecting-to-streams["Connecting to Streams"] blog post covers why client applications must connect to the appropriate nodes in a cluster and how a https://blog.rabbitmq.com/posts/2021/07/connecting-to-streams/#with-a-load-balancer[load balancer can make things complicated] for them.
 
 The `EnvironmentBuilder#addressResolver(AddressResolver)` method allows intercepting the node resolution after metadata hints and before connection.
 Applications can use this hook to ignore metadata hints and always use the load balancer, as illustrated in the following snippet:
@@ -289,7 +289,7 @@ include::{test-examples}/EnvironmentUsage.java[tag=address-resolver]
 <2> Use load balancer address for initial connection
 <3> Ignore metadata hints, always use load balancer
 
-The blog post covers the https://blog.rabbitmq.com/posts/2021/07/connecting-to-streams/#client-workaround-with-a-load-balancer[underlying details of this workaround].
+The blog post covers the https://www.rabbitmq.com/blog/2021/07/23/connecting-to-streams/#client-workaround-with-a-load-balancer[underlying details of this workaround].
 
 ==== Managing Streams
 

src/docs/asciidoc/overview.adoc

@@ -66,7 +66,7 @@ can also be useful for development and testing.
 * _avoid publishing duplicate messages_ thanks to message deduplication.
 * _consume asynchronously from streams and resume where left off_ thanks to
 automatic or manual offset tracking.
-* _enforce https://blog.rabbitmq.com/posts/2021/07/connecting-to-streams/[best practices] to create client connections_ – to stream leaders for publishers to minimize inter-node traffic and to stream replicas for consumers to offload leaders.
+* _enforce https://www.rabbitmq.com/blog/2021/07/23/connecting-to-streams/#client-workaround-with-a-load-balancer[best practices] to create client connections_ – to stream leaders for publishers to minimize inter-node traffic and to stream replicas for consumers to offload leaders.
 * _optimize resources_ thanks to automatic growing and shrinking of
 connections depending on the number of publishers and consumers.
 * _let the client handle network failure_ thanks to automatic connection