Consumers guide: move a section around

Author: michaelklishin

docs/consumers.md

@@ -370,14 +370,6 @@ See [Java client guide](/client-libraries/java-api-guide#consuming) for examples
 
 See [.NET client guide](/client-libraries/dotnet-api-guide#consuming) for examples.
 
-## Limiting the number of Consumers per channel
-
-In some scenarios where consumer leaks can happen it is good to limit the number of consumers that can be active on
-each channel. This can be configured in [rabbitmq.conf](./configure#config-file) using the setting `consumer_max_per_channel`:
-
-```ini
-consumer_max_per_channel = 100
-```
 
 ## Fetching Individual Messages ("Pull API") {#fetching}
 
@@ -471,6 +463,16 @@ The timeout is specified in milliseconds.
 Whether the timeout should be enforced is evaluated periodically, at one minute intervals.
 
 
+## Limiting the number of Consumers per channel
+
+In some scenarios where consumer leaks can happen it is good to limit the number of consumers that can be active on
+each channel. This can be configured in [rabbitmq.conf](./configure#config-file) using the setting `consumer_max_per_channel`:
+
+```ini
+consumer_max_per_channel = 100
+```
+
+
 ## Exclusivity {#exclusivity}
 
 When registering a consumer with an AMQP 0-9-1 client, [the `exclusive` flag](/amqp-0-9-1-reference#basic.consume)

versioned_docs/version-3.13/consumers.md

@@ -140,15 +140,6 @@ See [Java client guide](/client-libraries/java-api-guide#consuming) for examples
 
 See [.NET client guide](/client-libraries/dotnet-api-guide#consuming) for examples.
 
-## Limiting the number of Consumers per channel
-
-In some scenarios where consumer leaks can happen it is good to limit the number of consumers that can be active on
-each channel. This can be configured in [rabbitmq.conf](./configure#config-file) using the setting `consumer_max_per_channel`:
-
-```ini
-consumer_max_per_channel = 100
-```
-
 ## Message Properties and Delivery Metadata {#message-properties}
 
 Every delivery combines message metadata and delivery information. Different client
@@ -471,6 +462,16 @@ The timeout is specified in milliseconds.
 Whether the timeout should be enforced is evaluated periodically, at one minute intervals.
 
 
+## Limiting the number of Consumers per channel
+
+In some scenarios where consumer leaks can happen it is good to limit the number of consumers that can be active on
+each channel. This can be configured in [rabbitmq.conf](./configure#config-file) using the setting `consumer_max_per_channel`:
+
+```ini
+consumer_max_per_channel = 100
+```
+
+
 ## Exclusivity {#exclusivity}
 
 When registering a consumer with an AMQP 0-9-1 client, [the `exclusive` flag](/amqp-0-9-1-reference#basic.consume)