anchor.diff:  For structured file formats, if you specify this parameter, the field must exist
   within the file.
   
  -If this parameter is not specified, the structure finder makes a decision about which
  -field (if any) is the primary timestamp field. For structured file formats, it
  -is not compulsory to have a timestamp in the file.
  +If this parameter is not specified, the structure finder makes a decision about 
  +which field (if any) is the primary timestamp field. For structured file 
  +formats, it is not compulsory to have a timestamp in the file.
   --
   
   `timestamp_format`::
  -  (string) Optional. The Java time format of the timestamp field in the file. +
  +  (Optional, string) The Java time format of the timestamp field in the file.
   +
   --
  -NOTE: Only a subset of Java time format letter groups are supported:
  +Only a subset of Java time format letter groups are supported:
   
   * `a`
   * `d`
  
positive.code: --
  NOTE: The `Content-Type: application/json` header must be set even though in
  this case the data is not JSON. (Alternatively the `Content-Type` can be set
  to any other supported by Elasticsearch, but it must be set.)
  --
  
  If the request does not encounter errors, you receive the following result:
  
negative.code: 
  [[ml-find-file-structure-examples]]
  ==== {api-examples-title}
  
  [[ml-find-file-structure-example-nld-json]]
  ===== Ingesting newline-delimited JSON
  
  Suppose you have a newline-delimited JSON file that contains information about
  some books. You can send the contents to the `find_file_structure` endpoint:
  