updated documentation

Author: spinscale

docs/reference/mapping/date-format.asciidoc

@@ -200,6 +200,17 @@ year.
 year, and two digit day of month.
 |=======================================================================
 
+[float]
+[[strict]]
+=== Strict date formats
+
+Most of the above dates have a `strict` companion dates, which means, that
+year, month and day parts of the week must have prepending zeros in order
+to be valid. This means, that a date like `5/11/1` would not be valid, but
+you would need to specify the full date, which would be `2005/11/01` in this
+example. So instead of `dateOptionalTime` you would need to specify
+`strictDateOptionalTime`.
+
 [float]
 [[custom]]
 === Custom Format

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

@@ -79,7 +79,7 @@ format>> used to parse the provided timestamp value. For example:
 }
 --------------------------------------------------
 
-Note, the default format is `dateOptionalTime`. The timestamp value will
+Note, the default format is `strictDateOptionalTime`. The timestamp value will
 first be parsed as a number and if it fails the format will be tried.
 
 [float]

docs/reference/mapping/types/core-types.asciidoc

@@ -349,7 +349,7 @@ date type:
 Defaults to the property/field name.
 
 |`format` |The <<mapping-date-format,date
-format>>. Defaults to `dateOptionalTime`.
+format>>. Defaults to `strictDateOptionalTime`.
 
 |`store` |Set to `true` to store actual field in the index, `false` to not
 store it. Defaults to `false` (note, the JSON document itself is stored,

docs/reference/mapping/types/root-object-type.asciidoc

@@ -42,7 +42,7 @@ and will use the matching format as its format attribute. The date
 format itself is explained
 <<mapping-date-format,here>>.
 
-The default formats are: `dateOptionalTime` (ISO) and
+The default formats are: `strictDateOptionalTime` (ISO) and
 `yyyy/MM/dd HH:mm:ss Z||yyyy/MM/dd Z`.
 
 *Note:* `dynamic_date_formats` are used *only* for dynamically added