Update intro doc

Author: russcam

docs/intro.asciidoc

@@ -22,17 +22,22 @@ You've reached the documentation page for `Elasticsearch.Net` and `NEST`, The tw
 enough so that **all** the Elasticsearch API endpoints are represented as methods but not too much to get in the way of how you want to build 
 your json/request/response objects. It also comes with built in, configurable/overridable, cluster failover retry mechanisms. Elasticsearch is _elastic_ so why not your client?
 
-`NEST` is a high level client that has the advantage of having mapped all the request and response objects, 
-comes with a strongly typed query DSL that maps 1 to 1 with the Elasticsearch query DSL, and takes advantage of specific .NET features such as 
-<<covariant-search-results, covariant results>> and <<auto-map, auto mapping of POCOs>>. NEST internally uses and still exposes the low level `Elasticsearch.Net` client.
+`NEST` is a high level client that maps all requests and responses as types, and 
+comes with a strongly typed query DSL that maps 1 to 1 with the Elasticsearch query DSL. It takes advantage of specific .NET 
+features to provide higher level abstractions such as <<auto-map, auto mapping of CLR types>>. Internally, 
+NEST uses and still exposes the low level `Elasticsearch.Net` client, providing access to the power of NEST and allowing
+users to drop down to the low level client when wishing to.
 
 Please read the getting started guide for both <<elasticsearch-net,Elasticsearch.Net>> and <<nest,NEST>>.
 
 [float]
-=== Questions, bugs, comments, requests
+=== Questions, bugs, comments, feature requests
 
-All of these are more then welcome on the {github}/issues[github issues pages]! We try to at least reply within the same day.
+Bug reports and Feature requests are more than welcome on the {github}/issues[github issues pages]! 
+We try to at least reply within the same day.
 
-We also monitor question tagged with {stackoverflow}/questions/tagged/nest['nest' on stackoverflow] or 
-{stackoverflow}/questions/tagged/elasticsearch-net['elasticsearch-net' on stackoverflow], as well as https://discuss.elastic.co[discussions on our discourse site]
+For more general questions and comments, we monitor questions tagged with {stackoverflow}/questions/tagged/nest[`nest`] and 
+{stackoverflow}/questions/tagged/elasticsearch-net[`elasticsearch-net` on Stackoverflow], as well as 
+discussions opened on our Discourse site, https://discuss.elastic.co/c/elasticsearch[discuss.elastic.co]. By mentioning 
+`NEST` or `Elasticsearch.Net` in the title will help folks quickly identify what the question is about.
 

src/Tests/Tests/intro.asciidoc

@@ -13,16 +13,21 @@ You've reached the documentation page for `Elasticsearch.Net` and `NEST`, The tw
 enough so that **all** the Elasticsearch API endpoints are represented as methods but not too much to get in the way of how you want to build 
 your json/request/response objects. It also comes with built in, configurable/overridable, cluster failover retry mechanisms. Elasticsearch is _elastic_ so why not your client?
 
-`NEST` is a high level client that has the advantage of having mapped all the request and response objects, 
-comes with a strongly typed query DSL that maps 1 to 1 with the Elasticsearch query DSL, and takes advantage of specific .NET features such as 
-<<covariant-search-results, covariant results>> and <<auto-map, auto mapping of POCOs>>. NEST internally uses and still exposes the low level `Elasticsearch.Net` client.
+`NEST` is a high level client that maps all requests and responses as types, and 
+comes with a strongly typed query DSL that maps 1 to 1 with the Elasticsearch query DSL. It takes advantage of specific .NET 
+features to provide higher level abstractions such as <<auto-map, auto mapping of CLR types>>. Internally, 
+NEST uses and still exposes the low level `Elasticsearch.Net` client, providing access to the power of NEST and allowing
+users to drop down to the low level client when wishing to.
 
 Please read the getting started guide for both <<elasticsearch-net,Elasticsearch.Net>> and <<nest,NEST>>.
 
 [float]
-=== Questions, bugs, comments, requests
+=== Questions, bugs, comments, feature requests
 
-All of these are more then welcome on the {github}/issues[github issues pages]! We try to at least reply within the same day.
+Bug reports and Feature requests are more than welcome on the {github}/issues[github issues pages]! 
+We try to at least reply within the same day.
 
-We also monitor question tagged with {stackoverflow}/questions/tagged/nest['nest' on stackoverflow] or 
-{stackoverflow}/questions/tagged/elasticsearch-net['elasticsearch-net' on stackoverflow], as well as https://discuss.elastic.co[discussions on our discourse site]
+For more general questions and comments, we monitor questions tagged with {stackoverflow}/questions/tagged/nest[`nest`] and 
+{stackoverflow}/questions/tagged/elasticsearch-net[`elasticsearch-net` on Stackoverflow], as well as 
+discussions opened on our Discourse site, https://discuss.elastic.co/c/elasticsearch[discuss.elastic.co]. By mentioning 
+`NEST` or `Elasticsearch.Net` in the title will help folks quickly identify what the question is about.