Remove reference to text datatype

Replace with reference to string datatype.

Author: russcam

docs/client-concepts/high-level/analysis/writing-analyzers.asciidoc

@@ -36,7 +36,7 @@ image::analysis-chain.png[analysis chain]
 
 ==== Specifying an analyzer on a field mapping
 
-An analyzer can be specified on a `text` datatype field mapping when creating a new field on a type, usually
+An analyzer can be specified on a `string` datatype field mapping when creating a new field on a type, usually
 when creating the type mapping at index creation time, but also when adding a new field
 using the Put Mapping API.
 
@@ -102,6 +102,7 @@ var createIndexResponse = client.CreateIndex("my-index", c => c
 );
 ----
 <1> Pre-defined list of English stopwords within Elasticsearch
+
 <2> Use the `standard_english` analyzer configured
 
 [source,javascript]
@@ -267,6 +268,7 @@ var createIndexResponse = client.CreateIndex("questions", c => c
 );
 ----
 <1> Use an analyzer at index time that strips HTML tags
+
 <2> Use an analyzer at search time that does not strip HTML tags
 
 With this in place, the text of a question body will be analyzed with the `index_question` analyzer

docs/search/returned-fields.asciidoc

@@ -28,7 +28,7 @@ in how they work.
 ==== Stored fields
 
 When indexing a document, by default, Elasticsearch stores the originally sent JSON document in a special
-field called {ref_current}/mapping-source-field.html[_source]. The previous example demonstrated that the documents returned from
+field called {ref_current}/mapping-source-field.html[_source]. Documents returned from
 a search query are materialized from the `_source` field returned from Elasticsearch for each hit.
 
 It is also possible to store a field from the JSON document _separately_ within Elasticsearch
@@ -113,7 +113,9 @@ var searchResponse = client.Search<Project>(s => s
 );
 ----
 <1> **Include** the following fields
+
 <2> **Exclude** the following fields
+
 <3> Fields can be included or excluded through patterns
 
 With source filtering specified on the request, `.Documents` will

src/Tests/ClientConcepts/HighLevel/Analysis/WritingAnalyzers.doc.cs

@@ -31,7 +31,7 @@ public class WritingAnalyzers
         /**
          * ==== Specifying an analyzer on a field mapping
          *
-         * An analyzer can be specified on a `text` datatype field mapping when creating a new field on a type, usually
+         * An analyzer can be specified on a `string` datatype field mapping when creating a new field on a type, usually
          * when creating the type mapping at index creation time, but also when adding a new field
          * using the Put Mapping API.
          *

src/Tests/Search/ReturnedFields.doc.cs

@@ -25,7 +25,7 @@ public class ReturnedFields : SerializationTestBase
         /**==== Stored fields
          *
          * When indexing a document, by default, Elasticsearch stores the originally sent JSON document in a special
-         * field called {ref_current}/mapping-source-field.html[_source]. The previous example demonstrated that the documents returned from
+         * field called {ref_current}/mapping-source-field.html[_source]. Documents returned from
          * a search query are materialized from the `_source` field returned from Elasticsearch for each hit.
          *
          * It is also possible to store a field from the JSON document _separately_ within Elasticsearch