Merge pull request #10838 from rabbitmq/mergify/bp/v3.13.x/pr-10837

chore: fix some typos (backport #10837)

deps/rabbit/src/rabbit_maintenance.erl

@@ -226,7 +226,7 @@ transfer_leadership_of_metadata_store(TransferCandidates) ->
     end.
 
 -spec transfer_leadership_of_classic_mirrored_queues([node()]) -> ok.
-%% This function is no longer used by maintanence mode. We retain it in case
+%% This function is no longer used by maintenance mode. We retain it in case
 %% classic mirrored queue leadership transfer would be reconsidered.
 %%
 %% With a lot of CMQs in a cluster, the transfer procedure can take prohibitively long

release-notes/3.11.10.md

@@ -30,7 +30,7 @@ Release notes can be found on GitHub at [rabbitmq-server/release-notes](https://
 
 #### Enhancements
 
- * Key classic mirrored queue (a deprecated feature) settings now can be overriden with
+ * Key classic mirrored queue (a deprecated feature) settings now can be overridden with
    operator policies.
 
    Contributed by @SimonUnge (AWS).

release-notes/3.13.0.md

@@ -47,7 +47,7 @@ See the [Upgrading guide](https://www.rabbitmq.com/upgrade.html) for documentati
 for release notes of other releases.
 
 Note that since 3.12.0 requires **all feature flags** to be enabled before upgrading,
-there is no upgrade path from from 3.11.24 (or a later patch release) straight to 3.13.0.
+there is no upgrade path from 3.11.24 (or a later patch release) straight to 3.13.0.
 
 ### Required Feature Flags
 

release-notes/3.6.4.md

@@ -1,6 +1,6 @@
 ## RabbitMQ 3.6.4
 
-`3.6.4` is a maintanence release.
+`3.6.4` is a maintenance release.
 
 
 ### Server

release-notes/3.8.10.md

@@ -102,7 +102,7 @@ and [RabbitMQ community Slack](https://rabbitmq-slack.herokuapp.com/).
  * `rabbitmq-diagnostics check_if_node_is_quorum_critical` returned a false positive for a node [marked for maintenance](https://www.rabbitmq.com/upgrade.html#maintenance-mode).
    Given the refinement to the `rabbitmq-upgrade drain` command in [rabbitmq/rabbitmq-server#2474](https://github.com/rabbitmq/rabbitmq-server/issues/2474),
    `rabbitmq-diagnostics check_if_node_is_quorum_critical` now will unconditionally return a success
-   if target node is under maintanence.
+   if target node is under maintenance.
 
    GitHub issue: [rabbitmq/rabbitmq-server#2469](https://github.com/rabbitmq/rabbitmq-server/issues/2469)
 

release-notes/3.8.3.md

@@ -120,7 +120,7 @@ Any questions about this release, upgrades or RabbitMQ in general are welcome on
    GitHub issue: [rabbitmq/rabbitmq-server#2222](https://github.com/rabbitmq/rabbitmq-server/issues/2222)
 
  * Every cluster now features a persistent internal cluster ID that can be used by core features or plugins.
-   Unlike the human-readable cluster name, the value cannot be overriden by the user.
+   Unlike the human-readable cluster name, the value cannot be overridden by the user.
 
    GitHub issue: [rabbitmq/rabbitmq-server#2226](https://github.com/rabbitmq/rabbitmq-server/pull/2226)
 

release-notes/README-1.8.1.txt

@@ -26,7 +26,7 @@ enhancements
    now enforces the negotiated maximum frame size
  - AMQP 0.9.1 guidance on error constants is now followed more closely and
    0.9.1 error codes are produced in more situations
- - SSL compatiblity under R14A has been improved
+ - SSL compatibility under R14A has been improved
 
 java client
 -----------

release-notes/README-3.4.0.txt

@@ -218,7 +218,7 @@ dependency change
 26095 drop support for Java 1.5
 
 licencing change
-24543 make the Java client additionally avaliable under the ASL2
+24543 make the Java client additionally available under the ASL2
 
 
 .net client