address PR comments

docs/reference/mapping/fields/field-names-field.asciidoc

@@ -1,6 +1,5 @@
 [[mapping-field-names-field]]
 === `_field_names`
-added[1.3.0]
 
 The `_field_names` field indexes the field names of a document, which can later
 be used to search for documents based on the fields that they contain typically

docs/reference/mapping/fields/routing-field.asciidoc

@@ -2,7 +2,7 @@
 === `_routing`
 
 The routing field allows to control the `_routing` aspect when indexing
-data and explicit routing control is required.
+data and explicit routing control is required. It is stored and indexed.
 
 [float]
 ==== required
@@ -11,9 +11,7 @@ Another aspect of the `_routing` mapping is the ability to define it as
 required by setting `required` to `true`. This is very important to set
 when using routing features, as it allows different APIs to make use of
 it. For example, an index operation will be rejected if no routing value
-has been provided (or derived from the doc). A delete operation will be
-broadcasted to all shards if no routing value is provided and `_routing`
-is required.
+has been provided.
 
 [float]
 ==== id uniqueness

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

@@ -15,4 +15,4 @@ uses the <<mapping-uid-field,_uid>> field.
 --------------------------------------------------
 
 The `type` is optional and can be omitted, and can also accept an array
-of values.
+of values. If no type is specified, all types defined in the index mapping are tried.

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

@@ -1,8 +1,7 @@
 [[query-dsl-type-filter]]
 === Type Filter
 
-Filters documents matching the provided document / mapping type. Note,
-this filter uses the <<mapping-uid-field,_uid>> field.
+Filters documents matching the provided document / mapping type.
 
 [source,js]
 --------------------------------------------------