Docs: Removed old coming/added tags

docs/reference/docs/termvectors.asciidoc

@@ -3,9 +3,8 @@
 
 Returns information and statistics on terms in the fields of a particular
 document. The document could be stored in the index or artificially provided
-by the user coming[1.4.0]. Term vectors are now <<realtime,realtime>>, as opposed to
-previously near realtime coming[1.5.0]. The functionality is disabled by setting
-`realtime` parameter to `false`.
+by the user. Term vectors are <<realtime,realtime>> by default, not near
+realtime. This can be changed by setting `realtime` parameter to `false`.
 
 [source,js]
 --------------------------------------------------
@@ -281,7 +280,7 @@ curl -XGET 'http://localhost:9200/twitter/tweet/_termvector' -d '{
 
 [float]
 [[docs-termvectors-per-field-analyzer]]
-=== Example 4 coming[1.5.0]
+=== Example 4
 
 Additionally, a different analyzer than the one at the field may be provided
 by using the `per_field_analyzer` parameter. This is useful in order to

docs/reference/modules/discovery/zen.asciidoc

@@ -173,8 +173,6 @@ to 30 seconds and can be changed dynamically through the
 [[no-master-block]]
 ==== No master block
 
-coming[1.4.0.Beta1]
-
 For a node to be fully operational, it must have an active master. The `discovery.zen.no_master_block` settings controls
 what operations should be rejected when there is no active master.
 

docs/reference/modules/snapshots.asciidoc

@@ -94,8 +94,6 @@ Other repository backends are available in these official plugins:
 
 [float]
 ===== Repository Verification
-added[1.4.0]
-
 When repository is registered, it's immediately verified on all master and data nodes to make sure that it's functional
 on all nodes currently present in the cluster. The verification process can also be executed manually by running the
 following command:

docs/reference/query-dsl/filters/range-filter.asciidoc

@@ -59,8 +59,6 @@ In the above example, `gte` will be actually moved to `2011-12-31T23:00:00` UTC
 NOTE: if you give a date with a timezone explicitly defined and use the `time_zone` parameter, `time_zone` will be
 ignored. For example, setting `from` to `2012-01-01T00:00:00+01:00` with `"time_zone":"+10:00"` will still use `+01:00` time zone.
 
-coming[1.5.0,New feature added]
-
 When applied on `date` fields the `range` filter accepts also a `format` parameter.
 The `format` parameter will help support another date format than the one defined in mapping:
 

docs/reference/query-dsl/queries/mlt-query.asciidoc

@@ -132,14 +132,10 @@ The text is analyzed by the default analyzer at the field, unless specified by t
 |`include` |When using `like` with document requests, specifies whether the documents should be
 included from the search. Defaults to `false`.
 
-|`minimum_should_match`| coming[1.5.0] From the generated query, the number of terms that
+|`minimum_should_match`| From the generated query, the number of terms that
 must match following the <<query-dsl-minimum-should-match,minimum should
 syntax>>. (Defaults to `"30%"`).
 
-|`percent_terms_to_match` | deprecated[1.5.0,Replaced by `minimum_should_match`]
-From the generated query, the percentage of terms that must match (float value
-between 0 and 1). Defaults to `0.3` (30 percent).
-
 |`min_term_freq` |The frequency below which terms will be ignored in the
 source doc. The default frequency is `2`.
 

docs/reference/query-dsl/queries/range-query.asciidoc

@@ -54,8 +54,6 @@ In the above example, `gte` will be actually moved to `2011-12-31T23:00:00` UTC
 NOTE: if you give a date with a timezone explicitly defined and use the `time_zone` parameter, `time_zone` will be
 ignored. For example, setting `from` to `2012-01-01T00:00:00+01:00` with `"time_zone":"+10:00"` will still use `+01:00` time zone.
 
-coming[1.5.0,New feature added]
-
 When applied on `date` fields the `range` query accepts also a `format` parameter.
 The `format` parameter will help support another date format than the one defined in mapping:
 

docs/reference/search/aggregations/metrics/tophits-aggregation.asciidoc

@@ -197,8 +197,6 @@ and therefore can't be used in the `order` option of the `terms` aggregator.
 
 ==== top_hits support in a nested or reverse_nested aggregator
 
-coming[1.5.0]
-
 If the `top_hits` aggregator is wrapped in a `nested` or `reverse_nested` aggregator then nested hits are being returned.
 Nested hits are in a sense hidden mini documents that are part of regular document where in the mapping a nested field type
 has been configured. The `top_hits` aggregator has the ability to un-hide these documents if it is wrapped in a `nested`