Avoid unnecessary use of stored_fields in our docs.

Generally we don't advocate for using `stored_fields`, and we're interested in
eventually removing the need for this parameter. So it's best to avoid using
stored fields in our docs examples when it's not actually necessary.

Individual changes:
* Avoid using 'stored_fields' in our docs.
* When defining script fields in top-hits, de-emphasize stored fields.

docs/painless/painless-getting-started.asciidoc

@@ -155,10 +155,6 @@ First, let's look at the source data for a player by submitting the following re
 ----------------------------------------------------------------
 GET hockey/_search
 {
-  "stored_fields": [
-    "_id",
-    "_source"
-  ],
   "query": {
     "term": {
       "_id": 1

docs/reference/scripting/fields.asciidoc

@@ -26,8 +26,10 @@ Depending on how many documents you have, this could mean millions or billions
 of executions: these scripts need to be fast!
 
 Field values can be accessed from a script using
-<<modules-scripting-doc-vals,doc-values>>, or
-<<modules-scripting-stored,stored fields or `_source` field>>, which are explained below.
+<<modules-scripting-doc-vals,doc-values>>,
+<<modules-scripting-source, the `_source` field>>, or
+<<modules-scripting-stored, stored fields>>,
+each of which is explained below.
 
 [[scripting-score]]
 [float]
@@ -139,27 +141,22 @@ access `text` fields from scripts.
 ===================================================
 
 [float]
-[[modules-scripting-stored]]
-=== Stored fields and `_source`
-
-_Stored fields_ -- fields explicitly marked as
-<<mapping-store,`"store": true`>> -- can be accessed using the
-`_fields['field_name'].value` or `_fields['field_name']` syntax.
+[[modules-scripting-source]]
+=== The document `_source`
 
-The document <<mapping-source-field,`_source`>>, which is really just a
-special stored field,  can be accessed using the `_source.field_name` syntax.
-The `_source` is loaded as a map-of-maps, so properties within object fields
-can be accessed as, for example, `_source.name.first`.
+The document <<mapping-source-field,`_source`>> can be accessed using the
+`_source.field_name` syntax. The `_source` is loaded as a map-of-maps, so
+properties within object fields can be accessed as, for example,
+`_source.name.first`.
 
 [IMPORTANT]
-.Prefer doc-values to stored fields
+.Prefer doc-values to _source
 =========================================================
 
-Stored fields (which includes the stored `_source` field) are much slower than
-doc-values.  They are  optimised for returning several fields per result,
-while doc values are optimised for accessing the value of a specific field in
-many documents.
-
+Accessing the `_source` field is much slower than using doc-values. The
+_source field is optimised for returning several fields per result, while doc
+values are optimised for accessing the value of a specific field in many
+documents.
 
 It makes sense to use `_source` or stored fields when generating a
 <<search-request-script-fields,script field>> for the top ten hits from a search
@@ -177,16 +174,11 @@ PUT my_index
   "mappings": {
     "_doc": {
       "properties": {
-        "title": { <1>
-          "type": "text"
-        },
         "first_name": {
-          "type": "text",
-          "store": true
+          "type": "text"
         },
         "last_name": {
-          "type": "text",
-          "store": true
+          "type": "text"
         }
       }
     }
@@ -195,32 +187,71 @@ PUT my_index
 
 PUT my_index/_doc/1?refresh
 {
-  "title": "Mr",
   "first_name": "Barry",
   "last_name": "White"
 }
 
 GET my_index/_search
 {
   "script_fields": {
-    "source": {
+    "full_name": {
       "script": {
         "lang": "painless",
-        "source": "params._source.title + ' ' + params._source.first_name + ' ' + params._source.last_name" <2>
+        "source": "params._source.first_name + ' ' + params._source.last_name"
+      }
+    }
+  }
+}
+-------------------------------
+// CONSOLE
+
+[float]
+[[modules-scripting-stored]]
+=== Stored fields
+
+_Stored fields_ -- fields explicitly marked as
+<<mapping-store,`"store": true`>> in the mapping -- can be accessed using the
+`_fields['field_name'].value` or `_fields['field_name']` syntax:
+
+[source,js]
+-------------------------------
+PUT my_index
+{
+  "mappings": {
+    "_doc": {
+      "properties": {
+        "full_name": {
+          "type": "text",
+          "store": true
+        },
+        "title": {
+          "type": "text",
+          "store": true
+        }
       }
-    },
-    "stored_fields": {
+    }
+  }
+}
+
+PUT my_index/_doc/1?refresh
+{
+  "full_name": "Alice Ball",
+  "title": "Professor"
+}
+
+GET my_index/_search
+{
+  "script_fields": {
+    "name_with_title": {
       "script": {
         "lang": "painless",
-        "source": "params._fields['first_name'].value + ' ' + params._fields['last_name'].value"
+        "source": "params._fields['title'].value + ' ' + params._fields['full_name'].value"
       }
     }
   }
 }
 -------------------------------
 // CONSOLE
-<1> The `title` field is not stored and so cannot be used with the `_fields[]` syntax.
-<2> The `title` field can still be accessed from the `_source`.
 
 [TIP]
 .Stored vs `_source`

docs/reference/search/request/highlighting.asciidoc

@@ -313,7 +313,6 @@ highlighting would only take the search query into account.
 --------------------------------------------------
 GET /_search
 {
-    "stored_fields": [ "_id" ],
     "query" : {
         "match": {
             "comment": {
@@ -335,6 +334,7 @@ GET /_search
             "rescore_query_weight" : 10
         }
     },
+    "_source": false,
     "highlight" : {
         "order" : "score",
         "fields" : {