Docs: Replace added[1.4.0] with coming[1.4.0] since 1.4 is not released yet.

docs/reference/docs/get.asciidoc

@@ -127,7 +127,7 @@ will fail.
 [float]
 [[generated-fields]]
 === Generated fields
-added[1.4.0]
+coming[1.4.0]
 
 If no refresh occurred between indexing and refresh, GET will access the transaction log to fetch the document. However, some fields are generated only when indexing. 
 If you try to access a field that is only generated when indexing, you will get an exception (default). You can choose to ignore field that are generated if the transaction log is accessed by setting `ignore_errors_on_generated_fields=true`.

docs/reference/docs/multi-get.asciidoc

@@ -183,7 +183,7 @@ curl 'localhost:9200/_mget' -d '{
 [float]
 === Generated fields
 
-added[1.4.0]
+coming[1.4.0]
 
 See <<generated-fields>> for fields are generated only when indexing. 
 

docs/reference/docs/termvectors.asciidoc

@@ -23,7 +23,7 @@ curl -XGET 'http://localhost:9200/twitter/tweet/1/_termvector?fields=text,...'
 
 or by adding the requested fields in the request body (see
 example below). Fields can also be specified with wildcards
-in similar way to the <<query-dsl-multi-match-query,multi match query>> added[1.4.0].
+in similar way to the <<query-dsl-multi-match-query,multi match query>> coming[1.4.0].
 
 [float]
 === Return values
@@ -44,7 +44,7 @@ If the requested information wasn't stored in the index, it will be
 computed on the fly if possible. See <<mapping-types,type mapping>>
 for how to configure your index to store term vectors.
 
-added[1.4.0,The ability to computed term vectors on the fly is only available from 1.4.0 onwards (see below)]
+coming[1.4.0,The ability to computed term vectors on the fly is only available from 1.4.0 onwards (see below)]
 
 [WARNING]
 ======
@@ -229,7 +229,7 @@ Response:
 --------------------------------------------------
 
 [float]
-=== Example 2 added[1.4.0]
+=== Example 2 coming[1.4.0]
 
 Additionally, term vectors which are not explicitly stored in the index are automatically
 computed on the fly. The following request returns all information and statistics for the

docs/reference/docs/update.asciidoc

@@ -143,7 +143,7 @@ curl -XPOST 'localhost:9200/test/type1/1/_update' -d '{
     }
 }'
 --------------------------------------------------
-added[1.4.0]
+coming[1.4.0]
 
 If the document does not exist you may want your update script to
 run anyway in order to initialize the document contents using 

docs/reference/search/aggregations/bucket/significantterms-aggregation.asciidoc

@@ -308,7 +308,7 @@ Per default, the assumption is that the documents in the bucket are also contain
 
 
 ===== Chi square
-added[1.4.0]
+coming[1.4.0]
 
 Chi square as described in "Information Retrieval", Manning et al., Chapter 13.5.2 can be used as significance score by adding the parameter
 	
@@ -323,7 +323,7 @@ Chi square behaves like mutual information and can be configured with the same p
 
 
 ===== google normalized distance
-added[1.4.0]
+coming[1.4.0]
 
 Google normalized distance  as described in "The Google Similarity Distance", Cilibrasi and Vitanyi, 2007 (http://arxiv.org/pdf/cs/0412098v3.pdf) can be used as significance score by adding the parameter
 	

docs/reference/search/aggregations/metrics/scripted-metric-aggregation.asciidoc

@@ -1,7 +1,7 @@
 [[search-aggregations-metrics-scripted-metric-aggregation]]
 === Scripted Metric Aggregation
 
-added[1.4.0]
+coming[1.4.0]
 
 A metric aggregation that executes using scripts to provide a metric output.
 

docs/reference/search/benchmark.asciidoc

@@ -1,7 +1,7 @@
 [[search-benchmark]]
 == Benchmark
 
-added[1.4.0]
+coming[1.4.0]
 
 .Experimental!
 [IMPORTANT]

docs/reference/search/request/sort.asciidoc

@@ -285,7 +285,7 @@ conform with http://geojson.org/[GeoJSON].
 
 ==== Multiple reference points
 
-added[1.4.0]
+coming[1.4.0]
 
 Multiple geo points can be passed as an array containing any `geo_point` format, for example