anchor.diff:  // CONSOLE
   // TEST[continued]
   
  -The result of the above get operation is:
  +The API returns the following result:
   
   [source,js]
   --------------------------------------------------
  
positive.code: // CONSOLE
  // TEST[setup:twitter]
  
  [float]
  [[realtime]]
  ==== Realtime
  
  By default, the get API is realtime, and is not affected by the refresh
  rate of the index (when data will become visible for search). If a document
  has been updated but is not yet refreshed, the get API will issue a refresh
  call in-place to make the document visible. This will also make other documents
  changed since the last refresh visible. In order to disable realtime GET,
  one can set the `realtime` parameter to `false`.
  
  [float]
  [[get-source-filtering]]
  ==== Source filtering
  
  By default, the get operation returns the contents of the `_source` field unless
  you have used the `stored_fields` parameter or if the `_source` field is disabled.
  You can turn off `_source` retrieval by using the `_source` parameter:
  
  [source,js]
  --------------------------------------------------
  GET twitter/_doc/0?_source=false
  --------------------------------------------------
  // CONSOLE
  // TEST[setup:twitter]
  
  If you only need one or two fields from the complete `_source`, you can use the `_source_includes`
  and `_source_excludes` parameters to include or filter out the parts you need. This can be especially helpful
  with large documents where partial retrieval can save on network overhead. Both parameters take a comma separated list
  of fields or wildcard expressions. Example:
  
  [source,js]
  --------------------------------------------------
  GET twitter/_doc/0?_source_includes=*.id&_source_excludes=entities
  --------------------------------------------------
  // CONSOLE
  // TEST[setup:twitter]
  
  If you only want to specify includes, you can use a shorter notation:
  
  [source,js]
  --------------------------------------------------
  GET twitter/_doc/0?_source=*.id,retweeted
  --------------------------------------------------
  // CONSOLE
  // TEST[setup:twitter]
  
  [float]
  [[get-stored-fields]]
  ==== Stored Fields
  
  The get operation allows specifying a set of stored fields that will be
  returned by passing the `stored_fields` parameter.
  If the requested fields are not stored, they will be ignored.
  Consider for instance the following mapping:
  
  [source,js]
  
negative.code: // CONSOLE
  // TEST[setup:twitter]
  
  The API returns the following result:
  
  [source,js]
  --------------------------------------------------
  