[DOCS] Removed outdated new/deprecated version notices

docs/reference/modules/cluster.asciidoc

@@ -177,7 +177,7 @@ curl -XPUT localhost:9200/test/_settings -d '{
 }' 
 --------------------------------------------------
 
-From version 0.90, `index.routing.allocation.require.*` can be used to 
+`index.routing.allocation.require.*` can be used to 
 specify a number of rules, all of which MUST match in order for a shard
 to be  allocated to a node. This is in contrast to `include` which will
 include a node if ANY rule matches.

docs/reference/modules/discovery/zen.asciidoc

@@ -68,9 +68,7 @@ As part of the initial ping process a master of the cluster is either
 elected or joined to. This is done automatically. The
 `discovery.zen.ping_timeout` (which defaults to `3s`) allows to
 configure the election to handle cases of slow or congested networks
-(higher values assure less chance of failure). Note, this setting was
-changed from 0.15.1 onwards, prior it was called
-`discovery.zen.initial_ping_timeout`.
+(higher values assure less chance of failure). 
 
 Nodes can be excluded from becoming a master by setting `node.master` to
 `false`. Note, once a node is a client node (`node.client` set to

docs/reference/modules/indices.asciidoc

@@ -56,10 +56,7 @@ The following settings can be set to manage recovery policy:
     defaults to `true`.
 
 `indices.recovery.max_bytes_per_sec`::
-    since 0.90.1, defaults to `20mb`.
-
-`indices.recovery.max_size_per_sec`::
-    deprecated from 0.90.1. Replaced by `indices.recovery.max_bytes_per_sec`.
+    defaults to `20mb`.
 
 [float]
 === Store level throttling

docs/reference/modules/jmx.asciidoc

@@ -1,34 +0,0 @@
-[[modules-jmx]]
-== JMX
-
-[float]
-=== REMOVED AS OF v0.90
-
-Use the stats APIs instead.
-
-The JMX module exposes node information through
-http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/[JMX].
-JMX can be used by either
-http://en.wikipedia.org/wiki/JConsole[jconsole] or
-http://en.wikipedia.org/wiki/VisualVM[VisualVM].
-
-Exposed JMX data include both node level information, as well as
-instantiated index and shard on specific node. This is a work in
-progress with each version exposing more information.
-
-[float]
-=== jmx.domain
-
-The domain under which the JMX will register under can be set using
-`jmx.domain` setting. It defaults to `{elasticsearch}`.
-
-[float]
-=== jmx.create_connector
-
-An RMI connector can be started to accept JMX requests. This can be
-enabled by setting `jmx.create_connector` to `true`. An RMI connector
-does come with its own overhead, make sure you really need it.
-
-When an RMI connector is created, the `jmx.port` setting provides a port
-range setting for the ports the rmi connector can open on. By default,
-it is set to `9400-9500`.

docs/reference/modules/plugins.asciidoc

@@ -17,8 +17,14 @@ Installing plugins can either be done manually by placing them under the
 be found under the https://github.com/elasticsearch[elasticsearch]
 organization in GitHub, starting with `elasticsearch-`.
 
-Starting from 0.90.2, installing plugins typically take the form of
-`plugin --install <org>/<user/component>/<version>`. The plugins will be
+Installing plugins typically take the following form:
+
+[source,shell]
+-----------------------------------
+plugin --install <org>/<user/component>/<version>
+-----------------------------------
+
+The plugins will be
 automatically downloaded in this case from `download.elasticsearch.org`,
 and in case they don't exist there, from maven (central and sonatype).
 
@@ -26,17 +32,16 @@ Note that when the plugin is located in maven central or sonatype
 repository, `<org>` is the artifact `groupId` and `<user/component>` is
 the `artifactId`.
 
-For prior version, the older form is
-`plugin -install <org>/<user/component>/<version>`
-
 A plugin can also be installed directly by specifying the URL for it,
 for example:
-`bin/plugin --url file://path/to/plugin --install plugin-name` or
-`bin/plugin -url file://path/to/plugin -install plugin-name` for older
-version.
 
-Starting from 0.90.2, for more information about plugins, you can run
-`bin/plugin -h`.
+[source,shell]
+-----------------------------------
+bin/plugin --url file://path/to/plugin --install plugin-name
+-----------------------------------
+
+
+You can run `bin/plugin -h`.
 
 [float]
 ==== Site Plugins
@@ -56,13 +61,8 @@ running:
 
 [source,js]
 --------------------------------------------------
-# From 0.90.2
 bin/plugin --install mobz/elasticsearch-head
 bin/plugin --install lukas-vlcek/bigdesk
-
-# From a prior version
-bin/plugin -install mobz/elasticsearch-head
-bin/plugin -install lukas-vlcek/bigdesk
 --------------------------------------------------
 
 Will install both of those site plugins, with `elasticsearch-head`

docs/reference/modules/threadpool.asciidoc

@@ -7,29 +7,28 @@ pools, but the important ones include:
 
 [horizontal]
 `index`:: 
-    For index/delete operations, defaults to `fixed` type since
-    `0.90.0`, size `# of available processors`. (previously type `cached`)
+    For index/delete operations, defaults to `fixed`, 
+    size `# of available processors`. 
 
 `search`:: 
-    For count/search operations, defaults to `fixed` type since
-    `0.90.0`, size `3x # of available processors`. (previously type
-    `cached`)
+    For count/search operations, defaults to `fixed`,
+    size `3x # of available processors`. 
 
 `get`:: 
-    For get operations, defaults to `fixed` type since `0.90.0`,
-    size `# of available processors`. (previously type `cached`)
+    For get operations, defaults to `fixed`
+    size `# of available processors`.
 
 `bulk`:: 
-    For bulk operations, defaults to `fixed` type since `0.90.0`,
-    size `# of available processors`. (previously type `cached`)
+    For bulk operations, defaults to `fixed`
+    size `# of available processors`.
 
 `warmer`:: 
-    For segment warm-up operations, defaults to `scaling` since
-    `0.90.0` with a `5m` keep-alive. (previously type `cached`)
+    For segment warm-up operations, defaults to `scaling`
+    with a `5m` keep-alive. 
 
 `refresh`:: 
-    For refresh operations, defaults to `scaling` since
-    `0.90.0` with a `5m` keep-alive. (previously type `cached`)
+    For refresh operations, defaults to `scaling`
+    with a `5m` keep-alive. 
 
 Changing a specific thread pool can be done by setting its type and
 specific type parameters, for example, changing the `index` thread pool