From a849cc97ea453d31051a0fe1d98886ecd463893c Mon Sep 17 00:00:00 2001
From: Isabel Drost-Fromm <isabel.drostfromm@elasticsearch.com>
Date: Wed, 18 May 2016 14:38:54 +0200
Subject: [PATCH] Add CONSOLE to script-fields docs

---
 docs/reference/search/request/script-fields.asciidoc | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/docs/reference/search/request/script-fields.asciidoc b/docs/reference/search/request/script-fields.asciidoc
index 596aba31d82..6e054f02e1c 100644
--- a/docs/reference/search/request/script-fields.asciidoc
+++ b/docs/reference/search/request/script-fields.asciidoc
@@ -6,9 +6,10 @@ evaluation>> (based on different fields) for each hit, for example:
 
 [source,js]
 --------------------------------------------------
+GET /_search
 {
     "query" : {
-        ...
+        "match_all": {}
     },
     "script_fields" : {
         "test1" : {
@@ -25,6 +26,8 @@ evaluation>> (based on different fields) for each hit, for example:
     }
 }
 --------------------------------------------------
+// CONSOLE
+
 
 Script fields can work on fields that are not stored (`my_field_name` in
 the above case), and allow to return custom values to be returned (the
@@ -36,9 +39,10 @@ type). Here is an example:
 
 [source,js]
 --------------------------------------------------
+GET /_search
     {
         "query" : {
-            ...
+            "match_all": {}
         },
         "script_fields" : {
             "test1" : {
@@ -47,6 +51,7 @@ type). Here is an example:
         }
     }
 --------------------------------------------------
+// CONSOLE
 
 Note the `_source` keyword here to navigate the json-like model.