[DOCS] Tidied up layout of setup docs

Author: clintongormley

docs/reference/setup/as-a-service-win.asciidoc

@@ -1,7 +1,7 @@
 [[setup-service-win]]
 == Running as a Service on Windows
 
-Windows users can configure Elasticsearch to run as a service to run in the background or start automatically 
+Windows users can configure Elasticsearch to run as a service to run in the background or start automatically
 at startup without any user interaction.
 This can be achieved through `service.bat` script under `bin/` folder which allows one to install,
 remove, manage or configure the service and potentially start and stop the service, all from the command-line.
@@ -47,6 +47,7 @@ The service 'elasticsearch-service-x64' has been installed.
 NOTE: While a JRE can be used for the Elasticsearch service, due to its use of a client VM (as oppose to a server JVM which
 offers better performance for long-running applications) its usage is discouraged and a warning will be issued.
 
+[float]
 === Customizing service settings
 
 There are two ways to customize the service settings:

docs/reference/setup/as-a-service.asciidoc

@@ -3,6 +3,7 @@
 
 In order to run elasticsearch as a service on your operating system, the provided packages try to make it as easy as possible for you to start and stop elasticsearch during reboot and upgrades.
 
+[float]
 === Linux
 
 Currently our build automatically creates a debian package and an RPM package, which is available on the download page. The package itself does not have any dependencies, but you have to make sure that you installed a JDK.
@@ -26,6 +27,7 @@ Each package features a configuration file, which allows you to set the followin
 `ES_JAVA_OPTS`::          Any additional java options you may want to apply. This may be useful, if you need to set the `node.name` property, but do not want to change the `elasticsearch.yml` configuration file, because it is distributed via a provisioning system like puppet or chef. Example: `ES_JAVA_OPTS="-Des.node.name=search-01"`
 `RESTART_ON_UPGRADE`::    Configure restart on package upgrade, defaults to `false`. This means you will have to restart your elasticsearch instance after installing a package manually. The reason for this is to ensure, that upgrades in a cluster do not result in a continouos shard reallocation resulting in high network traffic and reducing the response times of your cluster.
 
+[float]
 ==== Debian/Ubuntu
 
 The debian package ships with everything you need as it uses standard debian tools like update `update-rc.d` to define the runlevels it runs on. The init script is placed at `/etc/init.d/elasticsearch` is you would expect it. The configuration file is placed at `/etc/default/elasticsearch`.
@@ -38,6 +40,7 @@ sudo update-rc.d elasticsearch defaults 95 10
 sudo /etc/init.d/elasticsearch start
 --------------------------------------------------
 
+[float]
 ===== Installing the oracle JDK
 
 The usual recommendation is to run the Oracle JDK with elasticsearch. However Ubuntu and Debian only ship the OpenJDK due to license issues. You can easily install the oracle installer package though. In case you are missing the `add-apt-repository` command under Debian GNU/Linux, make sure have at least Debian Wheezy and the package `python-software-properties` installed
@@ -53,8 +56,10 @@ java -version
 The last command should verify a successful installation of the Oracle JDK.
 
 
-==== RPM based distributions 
+[float]
+==== RPM based distributions
 
+[float]
 ===== Using chkconfig
 
 Some RPM based distributions are using `chkconfig` to enable and disable services. The init script is located at `/etc/init.d/elasticsearch`, where as the configuration file is placed at `/etc/sysconfig/elasticsearch`. Like the debian package the RPM package is not started by default after installation, you have to do this manually by entering the following commands
@@ -66,6 +71,7 @@ sudo service elasticsearch start
 --------------------------------------------------
 
 
+[float]
 ===== Using systemd
 
 Distributions like SuSe do not use the `chkconfig` tool to register services, but rather `systemd` and its command `/bin/systemctl` to start and stop services (at least in newer versions, otherwise use the `chkconfig` commands above). The configuration file is also placed at `/etc/sysconfig/elasticsearch`. After installing the RPM, you have to change the systemd configuration and then start up elasticsearch

docs/reference/setup/repositories.asciidoc

@@ -6,6 +6,7 @@ We also have repositories available for APT and YUM based distributions.
 We have split the major versions in separate urls to avoid accidental upgrades across major version.
 For all 0.90.x releases use 0.90 as version number, for 1.0.x use 1.0, etc.
 
+[float]
 === APT
 
 Download and install the Public Signing Key
@@ -25,6 +26,7 @@ deb http://packages.elasticsearch.org/elasticsearch/0.90/debian stable main
 Run apt-get update and the repository is ready for use.
 
 
+[float]
 === YUM
 
 Download and install the Public Signing Key