[DOCS] Fix heading format errors (#31483)

* [DOCS] Fix heading format errors. Closes #31327

* [DOCS] Fix heading format errors. Closes #31327
This commit is contained in:
Sue Gallagher 2018-06-25 17:25:32 -07:00 committed by GitHub
parent c6012ed575
commit 357a07e7a2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions

View File

@ -224,7 +224,7 @@ Time values can also be specified via abbreviations supported by <<time-units,ti
Note that fractional time values are not supported, but you can address this by shifting to another Note that fractional time values are not supported, but you can address this by shifting to another
time unit (e.g., `1.5h` could instead be specified as `90m`). time unit (e.g., `1.5h` could instead be specified as `90m`).
====== Format *Format*
Internally, a date is represented as a 64 bit number representing a timestamp in milliseconds-since-the-epoch. Internally, a date is represented as a 64 bit number representing a timestamp in milliseconds-since-the-epoch.
These timestamps are returned as the bucket keys. It is possible to return a formatted date string instead using These timestamps are returned as the bucket keys. It is possible to return a formatted date string instead using
@ -257,7 +257,7 @@ GET /_search
<1> Supports expressive date <<date-format-pattern,format pattern>> <1> Supports expressive date <<date-format-pattern,format pattern>>
====== Time Zone *Time Zone*
Date-times are stored in Elasticsearch in UTC. By default, all bucketing and Date-times are stored in Elasticsearch in UTC. By default, all bucketing and
rounding is also done in UTC. The `time_zone` parameter can be used to indicate rounding is also done in UTC. The `time_zone` parameter can be used to indicate