Space. The final frontier.

Author: Mathieu Martin

docs/conventions.asciidoc

@@ -9,18 +9,18 @@
 Elasticsearch can index text using:
 
 * *Text.* Text indexing allows for full text search, or searching arbitrary words that
-  are part of the field. 
+  are part of the field.
   See {ref}/text.html[Text datatype] in the {es} Reference Guide.
 * *Keywords.* Keyword indexing offers faster exact match filtering and prefix search,
   and makes aggregations (for {kib} visualizations) possible.
-  See the {es} Reference Guide for more information on 
+  See the {es} Reference Guide for more information on
   {ref}/query-dsl-term-query.html[exact match filtering],
-  {ref}/query-dsl-prefix-query.html[prefix search], or 
+  {ref}/query-dsl-prefix-query.html[prefix search], or
   {ref}/search-aggregations.html[aggregations].
 
 [float]
 ==== Default Elasticsearch convention
-  
+
 Unless your index mapping or index template specifies otherwise
 (as the ECS index template does),
 Elasticsearch indexes text field as `text` at the canonical field name,

docs/guidelines.asciidoc

@@ -27,7 +27,7 @@ practices.
 * *Singular or plural.* Use singular and plural names properly to reflect the field content. For example, use `requests_per_sec` rather than `request_per_sec`.
 * *General to specific.* Organise the prefixes from general to specific to allow grouping fields into objects with a prefix like `host.*`.
 * *Avoid repetition.* Avoid stuttering of words. If part of the field name is already in the prefix, do not repeat it. Example: `host.host_ip` should be `host.ip`.
-* *Use prefixes.* Fields must be prefixed except for the base fields. For example, all `host` fields are prefixed with `host.`. 
+* *Use prefixes.* Fields must be prefixed except for the base fields. For example, all `host` fields are prefixed with `host.`.
 See <<dot-notation>> for more details.
 +
 The document structure should be nested JSON objects. If you use Beats or