3.13.0 release notes: use new style rabbitmq.com doc guide paths

Author: michaelklishin

release-notes/3.13.0.md

@@ -14,7 +14,7 @@ The user-facing areas that have seen the biggest improvements in this release ar
  * [Khepri](https://www.youtube.com/watch?v=whVqpgvep90) now can be used as an [alternative schema data store](https://github.com/rabbitmq/rabbitmq-server/pull/7206) in RabbitMQ, replacing Mnesia
  * [MQTTv5 support](https://blog.rabbitmq.com/posts/2023/07/mqtt5)
  * Support for [consumer-side stream filtering](https://github.com/rabbitmq/rabbitmq-server/pull/8207)
- * A new [common message container format](https://github.com/rabbitmq/rabbitmq-server/pull/5077) used internally, based on the AMQP 1.0 message container format
+ * A new [common message container format](https://github.com/rabbitmq/rabbitmq-server/pull/5077) used internally, based on the AMQP 1.0 message format
  * Improved classic non-mirrored queue performance with message sizes larger than
    4 KiB (or a different customized CQ index embedding threshold)
  * Classic queues storage implementation version 2 (CQv2) is now highly recommended for all new deployments.
@@ -27,31 +27,31 @@ See Compatibility Notes below to learn about **breaking or potentially breaking
 RabbitMQ releases are distributed via [GitHub](https://github.com/rabbitmq/rabbitmq-server/releases).
 [Debian](https://rabbitmq.com/install-debian.html) and [RPM packages](https://rabbitmq.com/install-rpm.html) are available via Cloudsmith mirrors.
 
-[Community Docker image](https://hub.docker.com/_/rabbitmq/), [Chocolatey package](https://community.chocolatey.org/packages/rabbitmq), and the [Homebrew formula](https://rabbitmq.com/install-homebrew.html)
+[Community Docker image](https://hub.docker.com/_/rabbitmq/), [Chocolatey package](https://community.chocolatey.org/packages/rabbitmq), and the [Homebrew formula](https://www.rabbitmq.com/docs/install-homebrew)
 are other installation options. They are updated with a delay.
 
 
 ## Erlang/OTP Compatibility Notes
 
-This release [requires Erlang 26.x](https://www.rabbitmq.com/which-erlang.html).
+This release [requires Erlang 26.x](https://www.rabbitmq.com/docs/which-erlang).
 
-[Provisioning Latest Erlang Releases](https://www.rabbitmq.com/which-erlang.html#erlang-repositories) explains
+[Provisioning Latest Erlang Releases](https://www.rabbitmq.com/docs/which-erlang#erlang-repositories) explains
 what package repositories and tools can be used to provision latest patch versions of Erlang 26.x.
 
 
 ## Upgrading to 3.13
 
 ### Documentation guides on upgrades
 
-See the [Upgrading guide](https://www.rabbitmq.com/upgrade.html) for documentation on upgrades and [RabbitMQ change log](https://www.rabbitmq.com/changelog.html)
-for release notes of other releases.
+See the [Upgrading guide](https://www.rabbitmq.com/docs/upgrade) for documentation on upgrades and [GitHub releases](https://github.com/rabbitmq/rabbitmq-server/releases)
+for release notes of individual releases.
 
 Note that since 3.12.0 requires **all feature flags** to be enabled before upgrading,
 there is no upgrade path from 3.11.24 (or a later patch release) straight to 3.13.0.
 
 ### Required Feature Flags
 
-This release does not [graduate](https://rabbitmq.com/feature-flags.html#graduation) any feature flags.
+This release does not [graduate](https://www.rabbitmq.com/docs/feature-flags#graduation) any feature flags.
 
 However, all users are highly encouraged to enable all feature flags before upgrading to this release from
 3.12.x.
@@ -196,7 +196,7 @@ For example, if you set `mqtt.subscription_ttl = 3600000` (1 hour) prior to 3.13
 `rabbitmqctl node_health_check` has been deprecated for over three years
 and is now a no-op (does nothing).
 
-See the [Health Checks section](https://www.rabbitmq.com/monitoring.html#health-checks) in the monitoring guide
+See the [Health Checks section](https://www.rabbitmq.com/docs/monitoring#health-checks) in the monitoring guide
 to find out what modern alternatives are available.
 
 ### openSUSE Leap Package is not Provided
@@ -245,8 +245,8 @@ Some of it's great features include:
    ```
 
    In practical terms this means that it will be possible to swap Mnesia for a Raft-based data store
-   that will **predictably recover from network partitions and node failures**, the same way [quorum queues](https://rabbitmq.com/quorum-queues.html#leader-election)
-   and [streams](https://rabbitmq.com/streams.html#leader-election) already do. At the same time, this means
+   that will **predictably recover from network partitions and node failures**, the same way [quorum queues](https://www.rabbitmq.com/docs/quorum-queues#leader-election)
+   and [streams](https://www.rabbitmq.com/docs/streams#leader-election) already do. At the same time, this means
    that RabbitMQ clusters now **must have a majority of nodes online at all times**, or all client operations will be refused.
 
    Like quorum queues and streams, Khepri uses [RabbitMQ's Raft implementation](https://github.com/rabbitmq/ra) under the hood. With Khepri enabled, all key modern features
@@ -272,7 +272,7 @@ Some of it's great features include:
 
    When the number of online replicas of a quorum queue goes below (or above) its target,
    new replicas will be automatically placed if enough cluster nodes are available.
-   This is a more automatic version of how [quorum queue replicas have originally been grown](https://rabbitmq.com/quorum-queues.html#replica-management).
+   This is a more automatic version of how [quorum queue replicas have originally been grown](https://www.rabbitmq.com/docs/quorum-queues#replica-management).
 
    For automatic shrinking of queue replicas, the user must opt in.
 
@@ -281,7 +281,7 @@ Some of it's great features include:
    GitHub issue: [#8218](https://github.com/rabbitmq/rabbitmq-server/pull/8218)
 
  * Revisited peer discovery implementation that further reduces the probability of two or more
-   sets of nodes [forming separate clusters](https://www.rabbitmq.com/cluster-formation.html#initial-formation-race-condition) when **all** cluster nodes are created at the same time and boot in parallel.
+   sets of nodes [forming separate clusters](https://www.rabbitmq.com/docs/cluster-formation#initial-formation-race-condition) when **all** cluster nodes are created at the same time and boot in parallel.
 
    GitHub issue: [#9797](https://github.com/rabbitmq/rabbitmq-server/pull/9797)
 
@@ -320,7 +320,7 @@ Some of it's great features include:
 
    GitHub issues: [#8834](https://github.com/rabbitmq/rabbitmq-server/pull/8834), [#8927](https://github.com/rabbitmq/rabbitmq-server/pull/8927)
 
- * Classic queue storage version now can be set via [operator policies](https://rabbitmq.com/parameters.html#operator-policies).
+ * Classic queue storage version now can be set via [operator policies](https://www.rabbitmq.com/docs/parameters#operator-policies).
 
    Contributed by @SimonUnge (AWS).
 
@@ -353,7 +353,7 @@ Some of it's great features include:
 
    GitHub issue: [#10320](https://github.com/rabbitmq/rabbitmq-server/pull/10320)
 
- * When a [consumer delivery timeout](https://rabbitmq.com/consumers.html#acknowledgement-timeout) hits, a more informative message is now logged.
+ * When a [consumer delivery timeout](https://www.rabbitmq.com/docs/consumers#acknowledgement-timeout) hits, a more informative message is now logged.
 
    Contributed by @rluvaton.
 
@@ -426,7 +426,7 @@ This release includes all bug fixes shipped in the `3.12.x` series.
 
    **This is a potentially breaking change**.
 
-   Note that [Prometheus](https://rabbitmq.com/prometheus.html) is the recommended option for monitoring,
+   Note that [Prometheus](https://www.rabbitmq.com/docs/prometheus) is the recommended option for monitoring,
    not the management plugin's HTTP API.
 
    GitHub issues: [#9437](https://github.com/rabbitmq/rabbitmq-server/issues/9437), [#9578](https://github.com/rabbitmq/rabbitmq-server/pull/9578), [#9633](https://github.com/rabbitmq/rabbitmq-server/pull/9633)
@@ -502,7 +502,7 @@ This release includes all bug fixes shipped in the `3.12.x` series.
 
    GitHub issue: [#8680](https://github.com/rabbitmq/rabbitmq-server/pull/8680)
 
- * AMQP 1.0 connections are now throttled when the node hits a [resource alarm](https://rabbitmq.com/alarms.html).
+ * AMQP 1.0 connections are now throttled when the node hits a [resource alarm](https://www.rabbitmq.com/docs/alarms).
 
    GitHub issue: [#9953](https://github.com/rabbitmq/rabbitmq-server/pull/9953)