anchor.diff:  also supports other types for specific use cases. Here is an overview of
   the different version types and their semantics.
   
  -`internal`:: only index the document if the given version is identical to the version
  +`internal`:: Only index the document if the given version is identical to the version
   of the stored document.
   deprecated[6.7.0, Please use `if_seq_no` & `if_primary_term` instead. See <<optimistic-concurrency-control>> for more details.]
   
   
  -`external` or `external_gt`:: only index the document if the given version is strictly higher
  +`external` or `external_gt`:: Only index the document if the given version is strictly higher
   than the version of the stored document *or* if there is no existing document. The given
   version will be used as the new version and will be stored with the new document. The supplied
   version must be a non-negative long number.
   
  -`external_gte`:: only index the document if the given version is *equal* or higher
  +`external_gte`:: Only index the document if the given version is *equal* or higher
   than the version of the stored document. If there is no existing document
   the operation will succeed as well. The given version will be used as the new version
   and will be stored with the new document. The supplied version must be a non-negative long number.
  
positive.code: [[index-noop]]
  === Noop Updates
  
  When updating a document using the index api a new version of the document is
  always created even if the document hasn't changed. If this isn't acceptable
  use the `_update` api with `detect_noop` set to true. This option isn't
  available on the index api because the index api doesn't fetch the old source
  and isn't able to compare it against the new source.
  
  There isn't a hard and fast rule about when noop updates aren't acceptable.
  It's a combination of lots of factors like how frequently your data source
  sends updates that are actually noops and how many queries per second
  Elasticsearch runs on the shard with receiving the updates.
  
  [float]
  [[timeout]]
  
negative.code: // CONSOLE
  // TEST[continued]
  
  *NOTE:* Versioning is completely real time, and is not affected by the
  near real time aspects of search operations. If no version is provided,
  then the operation is executed without any version checks.
  
  