GEMNC-509: Rename .NET client to .NET Framework

docs/geode-native-docs-cpp/about-client-users-guide.html.md.erb

@@ -21,12 +21,12 @@ This documentation describes the Apache Geode Native Client version <%=vars.prod
 Source files are available from the [Apache Geode-Native Github repository](https://github.com/apache/geode-native) 
 and instructions on how to build this documentation are available in the project README file found at that location.
 
-The Apache Geode Native Client is a library that provides access for C++ and Microsoft<sup>®</sup> .NET™ clients to an Apache Geode cluster.
+The Apache Geode Native Client is a library that provides access for C++ and Microsoft<sup>®</sup> .NET™ Framework clients to an Apache Geode cluster.
 
 See the API docs for API details:
 
   - [C++ API docs](/<%=vars.cppapiref_version%>/hierarchy.html)
-  - [.NET API docs](/<%=vars.dotnetapiref_version%>/hierarchy.html)
+  - [.NET Framework API docs](/<%=vars.dotnetapiref_version%>/hierarchy.html)
 
 See the [_<%=vars.product_name_long%> User Guide_](<%=vars.serverman%>/about_<%=vars.product_name.downcase%>.html) for information regarding the server.
 

docs/geode-native-docs-cpp/client-cache-ref.html.md.erb

@@ -41,7 +41,7 @@ specified in the XML file.
 
 The declarative XML file is used to externalize the configuration of the client cache.
 The contents of the XML file correspond to APIs found in the`apache::geode::client` package for C++ applications,
-and the `Apache::Geode::Client` package for .NET applications.
+and the `Apache::Geode::Client` package for .NET Framework applications.
 
 Elements are defined in the Client Cache XSD file, named `cpp-cache-1.0.xsd`, which you can find in
 your native client distribution in the `xsds` directory, and online at

docs/geode-native-docs-cpp/continuous-queries.html.md.erb

@@ -19,9 +19,9 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-The C++ and .NET clients can initiate queries that run on the <%=vars.product_name%> cache server
-and notify the client when the query results have changed.  For details on the server-side setup for
-continuous queries, see [How Continuous Querying Works](<%=vars.serverman%>/developing/continuous_querying/how_continuous_querying_works.html) 
+The C++ and .NET Framework clients can initiate queries that run on the <%=vars.product_name%>
+cache server and notify the client when the query results have changed.  For details on the
+server-side setup for continuous queries, see [How Continuous Querying Works](<%=vars.serverman%>/developing/continuous_querying/how_continuous_querying_works.html)
 in the *<%=vars.product_name%> User Guide*.
 
 ## <a id="cq_main_features" ></a>Continuous Query Basics

docs/geode-native-docs-cpp/function-execution.html.md.erb

@@ -97,7 +97,7 @@ The client:
 - invokes the object's execute method to invoke the server-side function
 
 If the client expects results, it must create a result object.
-The .NET example uses a built-in result collector (`IResultCollector.getResults()`) to retrieve the function results.
+The .NET Framework example uses a built-in result collector (`IResultCollector.getResults()`) to retrieve the function results.
 
 The example creates a result variable to hold the results from the collector.
 

docs/geode-native-docs-cpp/serialization/cpp-serialization/pdxserializable-interface.html.md.erb

@@ -43,7 +43,7 @@ Use this procedure to program your domain object for PDX serialization using the
     }
     ```
 
-    If you also use PDX serialization in Java or .NET for the object, serialize the object in the same way for each language. Serialize the same fields in the same order and mark the same identity fields.
+    If you also use PDX serialization in Java or .NET Framework for the object, serialize the object in the same way for each language. Serialize the same fields in the same order and mark the same identity fields.
 
 3.  Program the `fromData` function to read your data fields from the serialized form into the object's fields.