Clarify consequence of translog async setting
Relates
@@ -26,8 +26,9 @@ although this is rarely needed.
=== Translog settings
The data in the translog is only persisted to disk when the translog is
-++fsync++ed and committed. In the event of hardware failure, any data written
-since the previous translog commit will be lost.
+++fsync++ed and committed. In the event of a hardware failure or an operating
+system crash or a JVM crash or a shard failure, any data written since the
+previous translog commit will be lost.
By default, Elasticsearch ++fsync++s and commits the translog every 5 seconds
if `index.translog.durability` is set to `async` or if set to `request`
@@ -61,7 +62,7 @@ update, or bulk request. This setting accepts the following parameters:
`async`::
`fsync` and commit in the background every `sync_interval`. In
- the event of hardware failure, all acknowledged writes since the last
+ the event of a failure, all acknowledged writes since the last
automatic commit will be discarded.
--
