Update custom serialization docs (#4580)

This commit updates the custom serialization docs that discuss using
JsonNetSerializer.

1. Remove the implication that the internal serializer
is based on Json.NET.
2. Include recommendation to hook up JsonNetSerializer when using
Newtonsoft.Json.Linq types like JObject

Author: russcam

docs/client-concepts/high-level/serialization/custom-serialization.asciidoc

@@ -115,8 +115,11 @@ back to NEST's built-in serializer.
 
 We ship a separate {nuget}/NEST.JsonNetSerializer[NEST.JsonNetSerializer] package that helps in composing a custom `SourceSerializer`
 using `Json.NET`, that is smart enough to delegate the serialization of known NEST types back to the built-in
-`RequestResponseSerializer`. This package is also useful if you want to control how your documents and values are stored
-and retrieved from Elasticsearch using `Json.NET`, without interfering with the way NEST uses `Json.NET` internally.
+`RequestResponseSerializer`. This package is also useful if
+
+. You want to control how your documents and values are stored and retrieved from Elasticsearch using `Json.NET`
+
+. You want to use `Newtonsoft.Json.Linq` types such as `JObject` within your documents
 
 The easiest way to hook this custom source serializer up is as follows
 

docs/query-dsl.asciidoc

@@ -49,13 +49,13 @@ NEST exposes all of the full text queries available in Elasticsearch
 
 * <<intervals-usage,Intervals Usage>>
 
-* <<match-bool-prefix-usage,Match Bool Prefix Usage>>
+* <<match-usage,Match Usage>>
 
-* <<match-phrase-prefix-usage,Match Phrase Prefix Usage>>
+* <<match-bool-prefix-usage,Match Bool Prefix Usage>>
 
 * <<match-phrase-usage,Match Phrase Usage>>
 
-* <<match-usage,Match Usage>>
+* <<match-phrase-prefix-usage,Match Phrase Prefix Usage>>
 
 * <<multi-match-usage,Multi Match Usage>>
 
@@ -71,13 +71,13 @@ include::query-dsl/full-text/common-terms/common-terms-usage.asciidoc[]
 
 include::query-dsl/full-text/intervals/intervals-usage.asciidoc[]
 
-include::query-dsl/full-text/match-bool-prefix/match-bool-prefix-usage.asciidoc[]
+include::query-dsl/full-text/match/match-usage.asciidoc[]
 
-include::query-dsl/full-text/match-phrase-prefix/match-phrase-prefix-usage.asciidoc[]
+include::query-dsl/full-text/match-bool-prefix/match-bool-prefix-usage.asciidoc[]
 
 include::query-dsl/full-text/match-phrase/match-phrase-usage.asciidoc[]
 
-include::query-dsl/full-text/match/match-usage.asciidoc[]
+include::query-dsl/full-text/match-phrase-prefix/match-phrase-prefix-usage.asciidoc[]
 
 include::query-dsl/full-text/multi-match/multi-match-usage.asciidoc[]
 
@@ -122,14 +122,14 @@ NEST exposes all of the term queries available in Elasticsearch
 
 * <<term-query-usage,Term Query Usage>>
 
-* <<terms-set-query-usage,Terms Set Query Usage>>
-
 * <<terms-list-query-usage,Terms List Query Usage>>
 
 * <<terms-lookup-query-usage,Terms Lookup Query Usage>>
 
 * <<terms-query-usage,Terms Query Usage>>
 
+* <<terms-set-query-usage,Terms Set Query Usage>>
+
 * <<wildcard-query-usage,Wildcard Query Usage>>
 
 See the Elasticsearch documentation on {ref_current}/term-level-queries.html[Term level queries] for more details.
@@ -160,14 +160,14 @@ include::query-dsl/term-level/regexp/regexp-query-usage.asciidoc[]
 
 include::query-dsl/term-level/term/term-query-usage.asciidoc[]
 
-include::query-dsl/term-level/terms-set/terms-set-query-usage.asciidoc[]
-
 include::query-dsl/term-level/terms/terms-list-query-usage.asciidoc[]
 
 include::query-dsl/term-level/terms/terms-lookup-query-usage.asciidoc[]
 
 include::query-dsl/term-level/terms/terms-query-usage.asciidoc[]
 
+include::query-dsl/term-level/terms-set/terms-set-query-usage.asciidoc[]
+
 include::query-dsl/term-level/wildcard/wildcard-query-usage.asciidoc[]
 
 [[compound-queries]]
@@ -283,10 +283,10 @@ Specialized types of queries that do not fit into other groups
 
 * <<rank-feature-query-usage,Rank Feature Query Usage>>
 
-* <<script-score-query-usage,Script Score Query Usage>>
-
 * <<script-query-usage,Script Query Usage>>
 
+* <<script-score-query-usage,Script Score Query Usage>>
+
 * <<shape-query-usage,Shape Query Usage>>
 
 See the Elasticsearch documentation on {ref_current}/specialized-queries.html[Specialized queries] for more details.
@@ -305,10 +305,10 @@ include::query-dsl/specialized/pinned/pinned-query-usage.asciidoc[]
 
 include::query-dsl/specialized/rank-feature/rank-feature-query-usage.asciidoc[]
 
-include::query-dsl/specialized/script-score/script-score-query-usage.asciidoc[]
-
 include::query-dsl/specialized/script/script-query-usage.asciidoc[]
 
+include::query-dsl/specialized/script-score/script-score-query-usage.asciidoc[]
+
 include::query-dsl/specialized/shape/shape-query-usage.asciidoc[]
 
 [[span-queries]]

tests/Tests/ClientConcepts/HighLevel/Serialization/CustomSerialization.doc.cs

@@ -120,8 +120,10 @@ public class MyPercolationDocument
 		 *
 		 * We ship a separate {nuget}/NEST.JsonNetSerializer[NEST.JsonNetSerializer] package that helps in composing a custom `SourceSerializer`
 		 * using `Json.NET`, that is smart enough to delegate the serialization of known NEST types back to the built-in
-		 * `RequestResponseSerializer`. This package is also useful if you want to control how your documents and values are stored
-		 * and retrieved from Elasticsearch using `Json.NET`, without interfering with the way NEST uses `Json.NET` internally.
+		 * `RequestResponseSerializer`. This package is also useful if
+		 *
+		 * . You want to control how your documents and values are stored and retrieved from Elasticsearch using `Json.NET`
+		 * . You want to use `Newtonsoft.Json.Linq` types such as `JObject` within your documents
 		 *
 		 * The easiest way to hook this custom source serializer up is as follows
 		 */