Move this section to the top

README.md

@@ -1,7 +1,15 @@
 RabbitMQ Autocluster
 ====================
 
-A RabbitMQ plugin that clusters nodes automatically using a number of peer discovery mechanisms:
+What it Does
+------------
+
+This plugin provides a mechanism for peer node discovery in RabbitMQ
+clusters. It also supports a few opinionated features around cluster
+formation and "permanently unavailable" node detection.
+
+Nodes using this plugin will discover its peers on boot and (optionally) register with
+one of the supported backends:
 
   * [AWS EC2 tags](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html)
   * [AWS Autoscaling Groups](https://aws.amazon.com/autoscaling/)
@@ -10,6 +18,20 @@ A RabbitMQ plugin that clusters nodes automatically using a number of peer disco
   * [Consul](https://consul.io)
   * [etcd](https://github.com/coreos/etcd)
 
+If at least one peer node has been discovered, cluster formation proceeds as usual,
+otherwise the node is considered to be the first one to come up and becomes the seed node.
+
+To avoid a natural race condition around seed node "election" when a newly formed cluster
+first boots, peer discovery backends use either randomized delays or a locking mechanism.
+
+Some backends support node health checks. Nodes not reporting their status periodically
+are considered to be in an errored state. If the user opts in, such nodes can be automatically
+removed from the cluster. This is useful for deployments that use AWS autoscaling groups
+or similar IaaS features, for example.
+
+This plugin only covers cluster formation and does not change how RabbitMQ clusters
+operate once formed.
+
 
 **Note:** This plugin is not a replacement for first-hand knowledge of
 how to manually create a RabbitMQ cluster. If you run into issues
@@ -76,38 +98,6 @@ Alternatively, there is a pre-built Docker Image available at on DockerHub as [a
 As of version ``0.5`` the autocluster plugin does not have a default backend configured. See the [Project Wiki](https://github.com/rabbitmq/rabbitmq-autocluster/wiki) for configuration details.
 
 
-What it Does
-------------
-
-This plugin provides a mechanism for peer node discovery in RabbitMQ
-clusters. It also supports a few opinionated features around cluster
-formation and "permanently unavailable" node detection.
-
-Nodes using this plugin will discover its peers on boot and (optionally) register with
-one of the supported backends:
-
-  * [AWS EC2 tags](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html)
-  * [AWS Autoscaling Groups](https://aws.amazon.com/autoscaling/)
-  * [Kubernetes](https://kubernetes.io/)
-  * DNS A records
-  * [Consul](https://consul.io)
-  * [etcd](https://github.com/coreos/etcd)
-
-If at least one peer node has been discovered, cluster formation proceeds as usual,
-otherwise the node is considered to be the first one to come up and becomes the seed node.
-
-To avoid a natural race condition around seed node "election" when a newly formed cluster
-first boots, peer discovery backends use either randomized delays or a locking mechanism.
-
-Some backends support node health checks. Nodes not reporting their status periodically
-are considered to be in an errored state. If the user opts in, such nodes can be automatically
-removed from the cluster. This is useful for deployments that use AWS autoscaling groups
-or similar IaaS features, for example.
-
-This plugin only covers cluster formation and does not change how RabbitMQ clusters
-operate once formed.
-
-
 Configuration
 -------------