geode-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dbar...@apache.org
Subject [geode-native] branch develop updated: GEODE-3517 Variable-ize product version and name in client user guide
Date Wed, 06 Sep 2017 23:49:03 GMT
This is an automated email from the ASF dual-hosted git repository.

dbarnes pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/geode-native.git


The following commit(s) were added to refs/heads/develop by this push:
     new af6031c  GEODE-3517 Variable-ize product version and name in client user guide
af6031c is described below

commit af6031cb355b2af1a95b67e6605ecb2461f0fa53
Author: Dave Barnes <dbarnes@pivotal.io>
AuthorDate: Wed Sep 6 16:47:17 2017 -0700

    GEODE-3517 Variable-ize product version and name in client user guide
---
 docs/geode-native-book/Gemfile                     |   2 +-
 docs/geode-native-book/Gemfile.lock                | 190 +++++++++++----------
 docs/geode-native-book/config.yml                  |   3 +
 .../about-client-users-guide.html.md.erb           |  14 +-
 .../cache-init-file/chapter-overview.html.md.erb   |   2 +-
 .../client-cache/application-plugins.html.md.erb   |   2 +-
 .../client-cache/caches.html.md.erb                |   2 +-
 .../client-cache/chapter-overview.html.md.erb      |   6 +-
 .../consistency-checking-in-regions.html.md.erb    |   6 +-
 .../controlling-cache-size.html.md.erb             |   2 +-
 .../client-cache/lru-entries-limit.html.md.erb     |   2 +-
 .../client-cache/region-shortcuts.html.md.erb      |   4 +-
 .../client-cache/regions.html.md.erb               |   2 +-
 .../client-cache/troubleshooting.html.md.erb       |   4 +-
 .../3-client-cq-api.html.md.erb                    |   6 +-
 .../continuous-querying/5a-writing-cq.html.md.erb  |   2 +-
 .../continuous-querying.html.md.erb                |   2 +-
 .../cpp-caching-api/pdx-serialization.html.md.erb  |   2 +-
 ...region-data-requiring-serialization.html.md.erb |   2 +-
 .../serialization-options.html.md.erb              |   6 +-
 .../serialization-overview.html.md.erb             |   4 +-
 .../serialization-using-serializable.html.md.erb   |   6 +-
 .../cpp-caching-api/using-pdxinstance.html.md.erb  |   2 +-
 .../using-pdxinstancefactory.html.md.erb           |   2 +-
 .../delta-propagation-properties.html.md.erb       |   4 +-
 .../delta-propagation.html.md.erb                  |   4 +-
 .../how-delta-propagation-works.html.md.erb        |   2 +-
 .../implementing-delta-propagation.html.md.erb     |   2 +-
 .../dotnet-caching-api/cache-apis.html.md.erb      |   2 +-
 .../csharp-dotnet-api.html.md.erb                  |   2 +-
 .../csharp-dotnet-naming-conventions.html.md.erb   |   2 +-
 .../data-serialization-apis.html.md.erb            |   8 +-
 .../dotnet-adding-entry-to-cache.html.md.erb       |   2 +-
 .../dotnet-caching-api.html.md.erb                 |   6 +-
 .../dotnet-data-serialization-options.html.md.erb  |  16 +-
 .../dotnet-data-serialization.html.md.erb          |   2 +-
 .../dotnet-pdx-autoserializer.html.md.erb          |   8 +-
 .../dotnet-pdx-serialization-features.html.md.erb  |  10 +-
 .../dotnet-pdx-serialization.html.md.erb           |   4 +-
 .../event-handling-apis.html.md.erb                |   4 +-
 .../how-igfserializable-works.html.md.erb          |   4 +-
 .../implementing-igfserializable.html.md.erb       |   2 +-
 .../dotnet-caching-api/other-apis.html.md.erb      |   2 +-
 .../primary-apis-cache-generic.html.md.erb         |   2 +-
 .../problem-scenarios.html.md.erb                  |  10 +-
 .../serializable-types.html.md.erb                 |   2 +-
 .../serialize-using-igfserializable.html.md.erb    |   4 +-
 .../serialize-using-ipdxserializable.html.md.erb   |   6 +-
 .../simple-csharp-example.html.md.erb              |   2 +-
 .../executing-functions.html.md.erb                |   2 +-
 .../handling-function-results.html.md.erb          |   4 +-
 .../how-functions-execute.html.md.erb              |   2 +-
 .../solutions-use-cases.html.md.erb                |   2 +-
 docs/geode-native-docs/glossary.html.md.erb        |  16 +-
 .../introduction/client-configurations.html.md.erb |  18 +-
 .../introduction/client-intro.html.md.erb          |   2 +-
 .../introduction/client-overview.html.md.erb       |   4 +-
 .../introduction/developing-linux.html.md.erb      |  10 +-
 .../introduction/developing-solaris.html.md.erb    |   4 +-
 .../introduction/developing-windows.html.md.erb    |  10 +-
 .../introduction/install-overview.html.md.erb      |  28 +--
 .../introduction/quickstart.html.md.erb            |  32 ++--
 .../introduction/running-client-apps.html.md.erb   |   4 +-
 .../configuring-durable-nc.html.md.erb             |   2 +-
 ...mpl-cache-listeners-durable-clients.html.md.erb |   2 +-
 .../preserving-data/reconnection.html.md.erb       |   2 +-
 .../1-quickintro-overview.html.md.erb              |   2 +-
 ...4-quickintro-exampleportfolioregion.html.md.erb |   2 +-
 .../security/LDAPserverauth.html.md.erb            |   2 +-
 docs/geode-native-docs/security/PKCS.html.md.erb   |   4 +-
 .../security/authentication-levels.html.md.erb     |   2 +-
 .../createsecureconnregionservice.html.md.erb      |   2 +-
 .../security/overviewauthentication.html.md.erb    |   4 +-
 .../security/overviewsecurity.html.md.erb          |   6 +-
 .../security/security-systemprops.html.md.erb      |   2 +-
 .../security/sslclientserver.html.md.erb           |   2 +-
 .../setting-properties/propfile-sample.html.md.erb |   2 +-
 .../sqlite-persistence/windows-install.html.md.erb |   2 +-
 .../transactions/running-client-xact.html.md.erb   |   2 +-
 .../transactions/suspend-resume-xacts.html.md.erb  |   2 +-
 80 files changed, 282 insertions(+), 285 deletions(-)

diff --git a/docs/geode-native-book/Gemfile b/docs/geode-native-book/Gemfile
index b61bbdc..5b35235 100644
--- a/docs/geode-native-book/Gemfile
+++ b/docs/geode-native-book/Gemfile
@@ -17,6 +17,6 @@
 
 source "https://rubygems.org"
 
-gem 'bookbindery'
+gem 'bookbindery', '10.1.8'
 
 gem 'libv8', '3.16.14.7'
diff --git a/docs/geode-native-book/Gemfile.lock b/docs/geode-native-book/Gemfile.lock
index 1d98505..36b3236 100644
--- a/docs/geode-native-book/Gemfile.lock
+++ b/docs/geode-native-book/Gemfile.lock
@@ -1,43 +1,40 @@
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (4.2.7)
+    activesupport (4.2.9)
       i18n (~> 0.7)
-      json (~> 1.7, >= 1.7.7)
       minitest (~> 5.1)
       thread_safe (~> 0.3, >= 0.3.4)
       tzinfo (~> 1.1)
-    addressable (2.4.0)
+    addressable (2.5.2)
+      public_suffix (>= 2.0.2, < 4.0)
     ansi (1.5.0)
-    bookbindery (9.12.0)
+    backports (3.8.0)
+    bookbindery (10.1.8)
       ansi (~> 1.4)
       css_parser
       elasticsearch
       fog-aws (~> 0.7.1)
       font-awesome-sass
       git (~> 1.2.8)
-      middleman (~> 3.4.0)
-      middleman-livereload (~> 3.4.3)
-      middleman-syntax (~> 2.0)
+      middleman (= 4.1.10)
+      middleman-compass
+      middleman-livereload
+      middleman-sprockets
+      middleman-syntax (= 2.1.0)
       nokogiri (= 1.6.7.2)
       puma
       rack-rewrite
       redcarpet (~> 3.2.3)
       rouge (!= 1.9.1)
       therubyracer
-      thor
-    builder (3.2.2)
-    capybara (2.4.4)
-      mime-types (>= 1.16)
-      nokogiri (>= 1.3.3)
-      rack (>= 1.0.0)
-      rack-test (>= 0.5.4)
-      xpath (~> 2.0)
-    chunky_png (1.3.6)
+      thor (= 0.19.1)
+    builder (3.2.3)
+    chunky_png (1.3.8)
     coffee-script (2.4.1)
       coffee-script-source
       execjs
-    coffee-script-source (1.10.0)
+    coffee-script-source (1.12.2)
     compass (1.0.3)
       chunky_png (~> 1.2)
       compass-core (~> 1.0.2)
@@ -50,154 +47,159 @@ GEM
       sass (>= 3.3.0, < 3.5)
     compass-import-once (1.0.5)
       sass (>= 3.2, < 3.5)
-    css_parser (1.4.5)
+    concurrent-ruby (1.0.5)
+    contracts (0.13.0)
+    css_parser (1.5.0)
       addressable
-    elasticsearch (2.0.0)
-      elasticsearch-api (= 2.0.0)
-      elasticsearch-transport (= 2.0.0)
-    elasticsearch-api (2.0.0)
+    dotenv (2.2.1)
+    elasticsearch (5.0.4)
+      elasticsearch-api (= 5.0.4)
+      elasticsearch-transport (= 5.0.4)
+    elasticsearch-api (5.0.4)
       multi_json
-    elasticsearch-transport (2.0.0)
+    elasticsearch-transport (5.0.4)
       faraday
       multi_json
     em-websocket (0.5.1)
       eventmachine (>= 0.12.9)
       http_parser.rb (~> 0.6.0)
     erubis (2.7.0)
-    eventmachine (1.2.0.1)
-    excon (0.51.0)
+    eventmachine (1.2.5)
+    excon (0.59.0)
     execjs (2.7.0)
-    faraday (0.9.2)
+    faraday (0.13.1)
       multipart-post (>= 1.2, < 3)
-    ffi (1.9.14)
+    fast_blank (1.0.0)
+    fastimage (2.1.0)
+    ffi (1.9.18)
     fog-aws (0.7.6)
       fog-core (~> 1.27)
       fog-json (~> 1.0)
       fog-xml (~> 0.1)
       ipaddress (~> 0.8)
-    fog-core (1.42.0)
+    fog-core (1.45.0)
       builder
-      excon (~> 0.49)
+      excon (~> 0.58)
       formatador (~> 0.2)
     fog-json (1.0.2)
       fog-core (~> 1.0)
       multi_json (~> 1.10)
-    fog-xml (0.1.2)
+    fog-xml (0.1.3)
       fog-core
-      nokogiri (~> 1.5, >= 1.5.11)
-    font-awesome-sass (4.6.2)
+      nokogiri (>= 1.5.11, < 2.0.0)
+    font-awesome-sass (4.7.0)
       sass (>= 3.2)
     formatador (0.2.5)
     git (1.2.9.1)
-    haml (4.0.7)
+    haml (5.0.2)
+      temple (>= 0.8.0)
       tilt
-    hike (1.2.3)
-    hooks (0.4.1)
-      uber (~> 0.0.14)
+    hamster (3.0.0)
+      concurrent-ruby (~> 1.0)
+    hashie (3.5.6)
     http_parser.rb (0.6.0)
     i18n (0.7.0)
     ipaddress (0.8.3)
-    json (1.8.3)
-    kramdown (1.11.1)
+    kramdown (1.14.0)
     libv8 (3.16.14.7)
     listen (3.0.8)
       rb-fsevent (~> 0.9, >= 0.9.4)
       rb-inotify (~> 0.9, >= 0.9.7)
-    middleman (3.4.1)
+    memoist (0.16.0)
+    middleman (4.1.10)
       coffee-script (~> 2.2)
-      compass (>= 1.0.0, < 2.0.0)
       compass-import-once (= 1.0.5)
-      execjs (~> 2.0)
       haml (>= 4.0.5)
       kramdown (~> 1.2)
-      middleman-core (= 3.4.1)
-      middleman-sprockets (>= 3.1.2)
+      middleman-cli (= 4.1.10)
+      middleman-core (= 4.1.10)
       sass (>= 3.4.0, < 4.0)
-      uglifier (~> 2.5)
-    middleman-core (3.4.1)
-      activesupport (~> 4.1)
+    middleman-cli (4.1.10)
+      thor (>= 0.17.0, < 2.0)
+    middleman-compass (4.0.1)
+      compass (>= 1.0.0, < 2.0.0)
+      middleman-core (>= 4.0.0)
+    middleman-core (4.1.10)
+      activesupport (~> 4.2)
+      addressable (~> 2.3)
+      backports (~> 3.6)
       bundler (~> 1.1)
-      capybara (~> 2.4.4)
+      contracts (~> 0.13.0)
+      dotenv
       erubis
-      hooks (~> 0.3)
+      execjs (~> 2.0)
+      fast_blank
+      fastimage (~> 2.0)
+      hamster (~> 3.0)
+      hashie (~> 3.4)
       i18n (~> 0.7.0)
-      listen (~> 3.0.3)
-      padrino-helpers (~> 0.12.3)
+      listen (~> 3.0.0)
+      memoist (~> 0.14)
+      padrino-helpers (~> 0.13.0)
+      parallel
       rack (>= 1.4.5, < 2.0)
-      thor (>= 0.15.2, < 2.0)
-      tilt (~> 1.4.1, < 2.0)
+      sass (>= 3.4)
+      servolux
+      tilt (~> 1.4.1)
+      uglifier (~> 3.0)
     middleman-livereload (3.4.6)
       em-websocket (~> 0.5.1)
       middleman-core (>= 3.3)
       rack-livereload (~> 0.3.15)
-    middleman-sprockets (3.4.2)
-      middleman-core (>= 3.3)
-      sprockets (~> 2.12.1)
-      sprockets-helpers (~> 1.1.0)
-      sprockets-sass (~> 1.3.0)
+    middleman-sprockets (4.1.1)
+      middleman-core (~> 4.0)
+      sprockets (>= 3.0)
     middleman-syntax (2.1.0)
       middleman-core (>= 3.2)
       rouge (~> 1.0)
-    mime-types (3.1)
-      mime-types-data (~> 3.2015)
-    mime-types-data (3.2016.0521)
     mini_portile2 (2.0.0)
-    minitest (5.9.0)
-    multi_json (1.12.1)
+    minitest (5.10.3)
+    multi_json (1.12.2)
     multipart-post (2.0.0)
     nokogiri (1.6.7.2)
       mini_portile2 (~> 2.0.0.rc2)
-    padrino-helpers (0.12.8)
+    padrino-helpers (0.13.3.4)
       i18n (~> 0.6, >= 0.6.7)
-      padrino-support (= 0.12.8)
-      tilt (~> 1.4.1)
-    padrino-support (0.12.8)
+      padrino-support (= 0.13.3.4)
+      tilt (>= 1.4.1, < 3)
+    padrino-support (0.13.3.4)
       activesupport (>= 3.1)
-    puma (3.6.0)
-    rack (1.6.4)
+    parallel (1.12.0)
+    public_suffix (3.0.0)
+    puma (3.10.0)
+    rack (1.6.8)
     rack-livereload (0.3.16)
       rack
     rack-rewrite (1.5.1)
-    rack-test (0.6.3)
-      rack (>= 1.0)
-    rb-fsevent (0.9.7)
-    rb-inotify (0.9.7)
-      ffi (>= 0.5.0)
+    rb-fsevent (0.10.2)
+    rb-inotify (0.9.10)
+      ffi (>= 0.5.0, < 2)
     redcarpet (3.2.3)
     ref (2.0.0)
     rouge (1.11.1)
-    sass (3.4.22)
-    sprockets (2.12.4)
-      hike (~> 1.2)
-      multi_json (~> 1.0)
-      rack (~> 1.0)
-      tilt (~> 1.1, != 1.3.0)
-    sprockets-helpers (1.1.0)
-      sprockets (~> 2.0)
-    sprockets-sass (1.3.1)
-      sprockets (~> 2.0)
-      tilt (~> 1.1)
+    sass (3.4.25)
+    servolux (0.13.0)
+    sprockets (3.7.1)
+      concurrent-ruby (~> 1.0)
+      rack (> 1, < 3)
+    temple (0.8.0)
     therubyracer (0.12.2)
       libv8 (~> 3.16.14.0)
       ref
     thor (0.19.1)
-    thread_safe (0.3.5)
+    thread_safe (0.3.6)
     tilt (1.4.1)
-    tzinfo (1.2.2)
+    tzinfo (1.2.3)
       thread_safe (~> 0.1)
-    uber (0.0.15)
-    uglifier (2.7.2)
-      execjs (>= 0.3.0)
-      json (>= 1.8.0)
-    xpath (2.0.0)
-      nokogiri (~> 1.3)
+    uglifier (3.2.0)
+      execjs (>= 0.3.0, < 3)
 
 PLATFORMS
   ruby
 
 DEPENDENCIES
-  bookbindery
+  bookbindery (= 10.1.8)
   libv8 (= 3.16.14.7)
 
 BUNDLED WITH
-   1.11.2
+   1.13.6
diff --git a/docs/geode-native-book/config.yml b/docs/geode-native-book/config.yml
index 7177699..32dc012 100644
--- a/docs/geode-native-book/config.yml
+++ b/docs/geode-native-book/config.yml
@@ -25,6 +25,9 @@ sections:
   subnav_template: geode-nc-nav
 
 template_variables:
+  product_name_long: Apache Geode
+  product_name: Geode
+  product_version: 1.3
   support_url: http://geode.apache.org/community
   product_url: http://geode.apache.org
   book_title: Apache Geode Client Documentation
diff --git a/docs/geode-native-docs/about-client-users-guide.html.md.erb b/docs/geode-native-docs/about-client-users-guide.html.md.erb
index 7a5ab64..c420ec4 100644
--- a/docs/geode-native-docs/about-client-users-guide.html.md.erb
+++ b/docs/geode-native-docs/about-client-users-guide.html.md.erb
@@ -1,6 +1,4 @@
----
-title: Apache Geode Client 1.3 Documentation
----
+<% set_title(product_name_long, "Client", product_version, "Documentation") %>
 
 <!--
 Licensed to the Apache Software Foundation (ASF) under one or more
@@ -31,7 +29,7 @@ This documentation provides step-by-step procedures for installation, configurat
 
 -   **[Setting System Properties](setting-properties/chapter-overview.html)**
 
-    *Setting System Properties* describes how to configure Apache Geode clients and cache servers to participate in a distributed system.
+    *Setting System Properties* describes how to configure <%=vars.product_name_long%> clients and cache servers to participate in a distributed system.
 
 -   **[Configuring the Client Cache](client-cache/chapter-overview.html)**
 
@@ -51,15 +49,15 @@ This documentation provides step-by-step procedures for installation, configurat
 
 -   **[Security](security/overviewsecurity.html)**
 
-    *Security* describes how to implement the security framework for the Geode client, including authentication, authorization, ecryption, and SSL client/server communication.
+    *Security* describes how to implement the security framework for the <%=vars.product_name%> client, including authentication, authorization, ecryption, and SSL client/server communication.
 
 -   **[Remote Querying](remote-querying/remote-querying.html)**
 
-    *Remote Querying* documents remote querying from the client to the Geode cache server. Using examples and procedures, it describes how to use the APIs to run queries against cached data; work with query strings in the client; create and manage queries; and create indexes.
+    *Remote Querying* documents remote querying from the client to the <%=vars.product_name%> cache server. Using examples and procedures, it describes how to use the APIs to run queries against cached data; work with query strings in the client; create and manage queries; and create indexes.
 
 -   **[Continuous Querying](continuous-querying/continuous-querying.html)**
 
-    *Continuous Querying* describes how to implement continuous querying in the Apache Geode client so that C++ and .NET clients can run queries against events in the Geode cache server region. It also describes main features and the client CQ API.
+    *Continuous Querying* describes how to implement continuous querying in the <%=vars.product_name_long%> client so that C++ and .NET clients can run queries against events in the <%=vars.product_name%> cache server region. It also describes main features and the client CQ API.
 
 -   **[Using Connection Pools](connection-pools/connection-pools.html)**
 
@@ -79,7 +77,7 @@ This documentation provides step-by-step procedures for installation, configurat
 
 -   **[Programming Examples](programming-examples/programming-examples.html)**
 
-    This chapter provides a set of programming examples to help you understand the Geode client API.
+    This chapter provides a set of programming examples to help you understand the <%=vars.product_name%> client API.
 
 -   **[Interoperability of Language Classes and Types](type-mappings/chapter-overview.html)**
 
diff --git a/docs/geode-native-docs/cache-init-file/chapter-overview.html.md.erb b/docs/geode-native-docs/cache-init-file/chapter-overview.html.md.erb
index 056c28e..db6654f 100644
--- a/docs/geode-native-docs/cache-init-file/chapter-overview.html.md.erb
+++ b/docs/geode-native-docs/cache-init-file/chapter-overview.html.md.erb
@@ -19,7 +19,7 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-To ease the task of managing the structure of the cache, you can define the default Geode cache structure in an XML-based initialization file.
+To ease the task of managing the structure of the cache, you can define the default <%=vars.product_name%> cache structure in an XML-based initialization file.
 
 # Cache Initialization File Basics
 
diff --git a/docs/geode-native-docs/client-cache/application-plugins.html.md.erb b/docs/geode-native-docs/client-cache/application-plugins.html.md.erb
index 7629043..2269b12 100644
--- a/docs/geode-native-docs/client-cache/application-plugins.html.md.erb
+++ b/docs/geode-native-docs/client-cache/application-plugins.html.md.erb
@@ -263,7 +263,7 @@ void removeListener(RegionPtr& region)
 
 Keep your callback implementations lightweight and prevent situations that might cause them to hang. For example, do not perform distribution operations or disconnects inside event handlers.
 
-Your code should handle any exceptions that it generates. If not, Geode handles them as well as possible. Because C++ has no standard for exceptions, in many cases Geode can only print an `unknown error` message.
+Your code should handle any exceptions that it generates. If not, <%=vars.product_name%> handles them as well as possible. Because C++ has no standard for exceptions, in many cases <%=vars.product_name%> can only print an `unknown error` message.
 
 ## <a id="application-plugins__section_E81DB00AE0784BA2819DB3683C257647" class="no-quick-link"></a>Specifying Application Plug-In Attributes
 
diff --git a/docs/geode-native-docs/client-cache/caches.html.md.erb b/docs/geode-native-docs/client-cache/caches.html.md.erb
index 3e540fa..785c3f8 100644
--- a/docs/geode-native-docs/client-cache/caches.html.md.erb
+++ b/docs/geode-native-docs/client-cache/caches.html.md.erb
@@ -19,7 +19,7 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-The cache is the entry point to data caching in Geode. Through the cache, clients gain access to the Geode caching framework for data loading, distribution, and maintenance.
+The cache is the entry point to data caching in <%=vars.product_name%>. Through the cache, clients gain access to the <%=vars.product_name%> caching framework for data loading, distribution, and maintenance.
 
 -   **[About the Client Cache](overview-client-cache.html)**
 
diff --git a/docs/geode-native-docs/client-cache/chapter-overview.html.md.erb b/docs/geode-native-docs/client-cache/chapter-overview.html.md.erb
index 31e73a4..15ba5bf 100644
--- a/docs/geode-native-docs/client-cache/chapter-overview.html.md.erb
+++ b/docs/geode-native-docs/client-cache/chapter-overview.html.md.erb
@@ -25,11 +25,11 @@ The client cache provides a framework for clients to store, manage, and distribu
 
 -   **[Caches](caches.html)**
 
-    The cache is the entry point to data caching in Geode. Through the cache, clients gain access to the Geode caching framework for data loading, distribution, and maintenance.
+    The cache is the entry point to data caching in <%=vars.product_name%>. Through the cache, clients gain access to the <%=vars.product_name%> caching framework for data loading, distribution, and maintenance.
 
 -   **[Cache Initialization File (cache.xml)](../cache-init-file/chapter-overview.html)**
 
-    To ease the task of managing the structure of the cache, you can define the default Geode cache structure in an XML-based initialization file.
+    To ease the task of managing the structure of the cache, you can define the default <%=vars.product_name%> cache structure in an XML-based initialization file.
 
 -   **[Regions](regions.html)**
 
@@ -41,7 +41,7 @@ The client cache provides a framework for clients to store, manage, and distribu
 
 -   **[Region Consistency](consistency-checking-in-regions.html)**
 
-    Geode ensures that all copies of a region eventually reach a consistent state on all members and clients that host the region.
+    <%=vars.product_name%> ensures that all copies of a region eventually reach a consistent state on all members and clients that host the region.
 
 -   **[Region Attributes](region-attributes.html)**
 
diff --git a/docs/geode-native-docs/client-cache/consistency-checking-in-regions.html.md.erb b/docs/geode-native-docs/client-cache/consistency-checking-in-regions.html.md.erb
index f510c34..84bc252 100644
--- a/docs/geode-native-docs/client-cache/consistency-checking-in-regions.html.md.erb
+++ b/docs/geode-native-docs/client-cache/consistency-checking-in-regions.html.md.erb
@@ -19,11 +19,11 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-Geode ensures that all copies of a region eventually reach a consistent state on all members and clients that host the region.
+<%=vars.product_name%> ensures that all copies of a region eventually reach a consistent state on all members and clients that host the region.
 
-By default Geode members perform consistency checks when they apply updates to a distributed region, in order to ensure that all copies of the region eventually become consistent on all Geode members and client caches that host the region. Different types of region ensure consistency using different techniques. However, when consistency checking is enabled (the default) all entries in a region require additional overhead in order to store version and timestamp information.
+By default <%=vars.product_name%> members perform consistency checks when they apply updates to a distributed region, in order to ensure that all copies of the region eventually become consistent on all <%=vars.product_name%> members and client caches that host the region. Different types of region ensure consistency using different techniques. However, when consistency checking is enabled (the default) all entries in a region require additional overhead in order to store version and tim [...]
 
-Although a region must have the same consistency checking configuration on all Geode members that host the region, you can optionally disable consistency checking in a client cache region while leaving consistency checking enabled for the region on Geode members. This configuration may be necessary in certain cases where the client must view all updates to a given region, even when Geode members discards an update in order to preserve region consistency.
+Although a region must have the same consistency checking configuration on all <%=vars.product_name%> members that host the region, you can optionally disable consistency checking in a client cache region while leaving consistency checking enabled for the region on <%=vars.product_name%> members. This configuration may be necessary in certain cases where the client must view all updates to a given region, even when <%=vars.product_name%> members discards an update in order to preserve re [...]
 
 See [Consistency for Region Updates](geodeman/developing/distributed_regions/region_entry_versions.html#topic_CF2798D3E12647F182C2CEC4A46E2045) in the server's documentation for more information.
 
diff --git a/docs/geode-native-docs/client-cache/controlling-cache-size.html.md.erb b/docs/geode-native-docs/client-cache/controlling-cache-size.html.md.erb
index 6486291..52cce63 100644
--- a/docs/geode-native-docs/client-cache/controlling-cache-size.html.md.erb
+++ b/docs/geode-native-docs/client-cache/controlling-cache-size.html.md.erb
@@ -22,7 +22,7 @@ limitations under the License.
 You can control cache size through region size limits, cache size limits, or a combination of the two.
 
 <a id="controlling-cache-size__section_A0C25D6D1D5243778800AE67CAD8CB2C"></a>
-Geode controls region size by moving least recently used (LRU) entries from the region or from all cache regions.
+<%=vars.product_name%> controls region size by moving least recently used (LRU) entries from the region or from all cache regions.
 
 ## <a id="controlling-cache-size__section_3C7994A4C9D9468F860D99C0ED086D74" class="no-quick-link"></a>Controlling Region Size
 
diff --git a/docs/geode-native-docs/client-cache/lru-entries-limit.html.md.erb b/docs/geode-native-docs/client-cache/lru-entries-limit.html.md.erb
index d6d4180..2acb215 100644
--- a/docs/geode-native-docs/client-cache/lru-entries-limit.html.md.erb
+++ b/docs/geode-native-docs/client-cache/lru-entries-limit.html.md.erb
@@ -25,7 +25,7 @@ This attribute sets the maximum number of entries to hold in a caching region. W
 **Note:**
 This is a tuning parameter that affects system performance.
 
-When eviction is configured, memory consumption or entry count is monitored and, when capacity is reached, Geode makes way for new entries by removing or overflowing the stalest LRU entries to disk.
+When eviction is configured, memory consumption or entry count is monitored and, when capacity is reached, <%=vars.product_name%> makes way for new entries by removing or overflowing the stalest LRU entries to disk.
 
 If you use disk data overflow to supplement memory for your data cache, make sure you have enough disk space to store the data.
 
diff --git a/docs/geode-native-docs/client-cache/region-shortcuts.html.md.erb b/docs/geode-native-docs/client-cache/region-shortcuts.html.md.erb
index 7ce17cf..6533c9c 100644
--- a/docs/geode-native-docs/client-cache/region-shortcuts.html.md.erb
+++ b/docs/geode-native-docs/client-cache/region-shortcuts.html.md.erb
@@ -20,9 +20,9 @@ limitations under the License.
 -->
 
 <a id="region-shortcuts__section_62D2AB580EDB4165970E4FC42A35C80B"></a>
-Geode provides predefined, shortcut region attributes settings for your use, in `RegionShortcut`.
+<%=vars.product_name%> provides predefined, shortcut region attributes settings for your use, in `RegionShortcut`.
 
-Shortcut attributes are a convenience only. They are named attributes that Geode has already stored for you. You can override their settings by storing new attributes with the same `id` as the predefined attributes.
+Shortcut attributes are a convenience only. They are named attributes that <%=vars.product_name%> has already stored for you. You can override their settings by storing new attributes with the same `id` as the predefined attributes.
 
 You can also create custom region attributes and store them with an identifier for later retrieval. Both types of stored attributes are referred to as named region attributes. You can create and store your attribute settings in the `cache.xml` file and through the API.
 
diff --git a/docs/geode-native-docs/client-cache/regions.html.md.erb b/docs/geode-native-docs/client-cache/regions.html.md.erb
index 723f395..238e8a9 100644
--- a/docs/geode-native-docs/client-cache/regions.html.md.erb
+++ b/docs/geode-native-docs/client-cache/regions.html.md.erb
@@ -22,7 +22,7 @@ limitations under the License.
 You create cache regions either programmatically or through declarative statements in the `cache.xml` file. Generally, a cache is organized and populated through a combination of the two approaches.
 
 <a id="regions__section_1BE4ABB76537488C966E452C2D89478F"></a>
-The region is the core building block of the Geode distributed system. All cached data is organized into data regions and you do all of your data puts, gets, and querying activities against them.
+The region is the core building block of the <%=vars.product_name%> distributed system. All cached data is organized into data regions and you do all of your data puts, gets, and querying activities against them.
 
 A distributed region can be either non-partitioned or a partitioned region. See [Data Regions](geodeman/basic_config/data_regions/chapter_overview.html) for detailed descriptions of both non-partitioned and partitioned regions. Region creation is subject to attribute consistency checks. The requirements for consistency between attributes are detailed both in the API documentation and throughout the discussion of [Region Attributes](region-attributes.html#region-attributes).
 
diff --git a/docs/geode-native-docs/client-cache/troubleshooting.html.md.erb b/docs/geode-native-docs/client-cache/troubleshooting.html.md.erb
index 83c4aae..e0aef6e 100644
--- a/docs/geode-native-docs/client-cache/troubleshooting.html.md.erb
+++ b/docs/geode-native-docs/client-cache/troubleshooting.html.md.erb
@@ -30,7 +30,7 @@ Can't get Windows performance data. RegQueryValueEx returned 5
 ```
 
 This can occur because incorrect information is returned when a Win32 application calls the ANSI version of `RegQueryValueEx` Win32 API with `HKEY_PERFORMANCE_DATA`. This error is described in Microsoft KB article ID 226371 at [http://support.microsoft.com/kb/226371/en-us](http://support.microsoft.com/kb/226371/en-us).
-To successfully acquire Windows performance data, you need to verify that you have the proper registry key access permissions in the system registry. In particular, make sure that `Perflib` in the following registry path is readable (`KEY_READ` access) by the Geode process:
+To successfully acquire Windows performance data, you need to verify that you have the proper registry key access permissions in the system registry. In particular, make sure that `Perflib` in the following registry path is readable (`KEY_READ` access) by the <%=vars.product_name%> process:
 
 ``` pre
 HKEY_LOCAL_MACHINE\
@@ -43,7 +43,7 @@ HKEY_LOCAL_MACHINE\
 
 An example of reasonable security on the performance data would be to grant administrators `KEY_ALL_ACCESS` and interactive users `KEY_READ` access. This particular configuration prevents non-administrator remote users from querying performance data.
 
-See [http://support.microsoft.com/kb/310426](http://support.microsoft.com/kb/310426) and [http://support.microsoft.com/kb/146906](http://support.microsoft.com/kb/146906) for instructions about how to ensure that Geode processes have access to the registry keys associated with performance.
+See [http://support.microsoft.com/kb/310426](http://support.microsoft.com/kb/310426) and [http://support.microsoft.com/kb/146906](http://support.microsoft.com/kb/146906) for instructions about how to ensure that <%=vars.product_name%> processes have access to the registry keys associated with performance.
 
 ## <a id="troubleshooting__section_65EC3B1EAC55421BB734E72E7BFEBFFC" class="no-quick-link"></a>Generating a Process Memory Dump Image for Fatal Errors
 
diff --git a/docs/geode-native-docs/continuous-querying/3-client-cq-api.html.md.erb b/docs/geode-native-docs/continuous-querying/3-client-cq-api.html.md.erb
index 8706d93..403d8ed 100644
--- a/docs/geode-native-docs/continuous-querying/3-client-cq-api.html.md.erb
+++ b/docs/geode-native-docs/continuous-querying/3-client-cq-api.html.md.erb
@@ -21,7 +21,7 @@ limitations under the License.
 
 This chapter documents the primary native client API for CQ management.
 
-The Apache Geode native client API allows your clients to create and manage CQs. (The server side does not have an API.) Continuous querying provides native client query syntax, events-based management, integration with client/server architecture, active query execution, and interest criteria based on data values. For complete information on the classes and interfaces described here, 
+The <%=vars.product_name_long%> native client API allows your clients to create and manage CQs. (The server side does not have an API.) Continuous querying provides native client query syntax, events-based management, integration with client/server architecture, active query execution, and interest criteria based on data values. For complete information on the classes and interfaces described here, 
 see the documentation for the [C++ API](/releases/latest/api/cppdocs) or the [.NET API](/releases/latest/api/dotnetdocs).
 
 **Apache.Geode.Client.Cache**
@@ -47,8 +47,8 @@ Only C\# versions of CQ API interfaces, classes, and methods are shown here (exa
 
 Continuous querying in the native client has the following features:
 
--   **Standard Geode native client query syntax and semantics**. CQ queries are expressed in the same language used for other native client queries. See [Remote Querying](../remote-querying/remote-querying.html).
--   **Standard Geode events-based management of CQ events**. The event handling used to process CQ events is based on the standard Geode event handling framework. The CQListener interface is similar to [Application Plug-Ins](../client-cache/application-plugins.html) and [Application Callbacks](../dotnet-caching-api/application-callbacks.html).
+-   **Standard <%=vars.product_name%> native client query syntax and semantics**. CQ queries are expressed in the same language used for other native client queries. See [Remote Querying](../remote-querying/remote-querying.html).
+-   **Standard <%=vars.product_name%> events-based management of CQ events**. The event handling used to process CQ events is based on the standard <%=vars.product_name%> event handling framework. The CQListener interface is similar to [Application Plug-Ins](../client-cache/application-plugins.html) and [Application Callbacks](../dotnet-caching-api/application-callbacks.html).
 -   **Complete integration with the client/server architecture**. CQ functionality uses existing server-to-client messaging mechanisms to send events. All tuning of your server-to-client messaging also tunes the messaging of your CQ events. If your system is configured for high availability then your CQs are highly available, with seamless failover provided in case of server failure (see [High Availability for Client-to-Server Communication](../preserving-data/high-availability-client-se [...]
 -   **Interest criteria based on data values**. CQ queries are run against the region's entry values. Compare this to register interest by reviewing [Registering Interest for Entries](../client-cache/registering-interest-for-entries.html).
 -   **Active query execution**. Once initialized, the queries only operate on new events instead of on the entire region data set. Events that change the query result are sent to the client immediately.
diff --git a/docs/geode-native-docs/continuous-querying/5a-writing-cq.html.md.erb b/docs/geode-native-docs/continuous-querying/5a-writing-cq.html.md.erb
index 60743c4..cf1294d 100644
--- a/docs/geode-native-docs/continuous-querying/5a-writing-cq.html.md.erb
+++ b/docs/geode-native-docs/continuous-querying/5a-writing-cq.html.md.erb
@@ -27,7 +27,7 @@ This is the basic syntax for the CQ query:
 SELECT * FROM /fullRegionPath [iterator] [WHERE clause]
 ```
 
-The CQ query must satisfy the standard Geode native client querying specifications described in [Remote Querying](../remote-querying/remote-querying.html). It also must satisfy these restrictions:
+The CQ query must satisfy the standard <%=vars.product_name%> native client querying specifications described in [Remote Querying](../remote-querying/remote-querying.html). It also must satisfy these restrictions:
 
 -   The `FROM` clause must contain only a single region specification, with optional iterator variable.
 -   The query must be a `SELECT` expression only, preceded by zero or more `IMPORT` statements. This means the query cannot be a statement like `/tradeOrder.name` or `(SELECT * from                     /tradeOrder).size`.
diff --git a/docs/geode-native-docs/continuous-querying/continuous-querying.html.md.erb b/docs/geode-native-docs/continuous-querying/continuous-querying.html.md.erb
index 9effa11..6e3439c 100644
--- a/docs/geode-native-docs/continuous-querying/continuous-querying.html.md.erb
+++ b/docs/geode-native-docs/continuous-querying/continuous-querying.html.md.erb
@@ -19,7 +19,7 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-*Continuous Querying* describes how to implement continuous querying in the Apache Geode native client so that C++ and .NET clients can run queries against events in the Geode cache server region. It also describes main features and the native client CQ API.
+*Continuous Querying* describes how to implement continuous querying in the <%=vars.product_name_long%> native client so that C++ and .NET clients can run queries against events in the <%=vars.product_name%> cache server region. It also describes main features and the native client CQ API.
 
 -   **[How Continuous Querying Works](1-how-cont-query-works.html)**
 
diff --git a/docs/geode-native-docs/cpp-caching-api/pdx-serialization.html.md.erb b/docs/geode-native-docs/cpp-caching-api/pdx-serialization.html.md.erb
index df656b9..aacb1fa 100644
--- a/docs/geode-native-docs/cpp-caching-api/pdx-serialization.html.md.erb
+++ b/docs/geode-native-docs/cpp-caching-api/pdx-serialization.html.md.erb
@@ -39,7 +39,7 @@ When using the C++ client API, you can opt to use PDX autoserialization. The com
 
 -   **[Programming Your Application to Use PdxInstances](using-pdxinstance.html)**
 
-    A `PdxInstance` is a lightweight wrapper around the raw bytes of the PDX serialized objects kept in the cache. It provides applications with run-time access to files of a PDX serialized object. Geode provides the implementation of the `PdxInstance` class.
+    A `PdxInstance` is a lightweight wrapper around the raw bytes of the PDX serialized objects kept in the cache. It provides applications with run-time access to files of a PDX serialized object. <%=vars.product_name%> provides the implementation of the `PdxInstance` class.
 
 -   **[Configuring PDX to Ignore Unread Fields During Deserialization](pdx-ignore-unread-fields.html)**
 
diff --git a/docs/geode-native-docs/cpp-caching-api/region-data-requiring-serialization.html.md.erb b/docs/geode-native-docs/cpp-caching-api/region-data-requiring-serialization.html.md.erb
index 3a78e94..648d0dc 100644
--- a/docs/geode-native-docs/cpp-caching-api/region-data-requiring-serialization.html.md.erb
+++ b/docs/geode-native-docs/cpp-caching-api/region-data-requiring-serialization.html.md.erb
@@ -31,6 +31,6 @@ Region data in the following types of regions must be serializable:
 -   Regions that receive events from remote caches.
 -   Regions that provide function arguments and results.
 
-To minimize the cost of serialization and deserialization, Geode avoids changing the data format whenever possible. This means your data may be stored in the cache in serialized or deserialized form, depending on how you use it. For example, if a server acts only as a storage location for data distribution between clients, it makes sense to leave the data in serialized form, ready to be transmitted to clients that request it. Partitioned region data is always stored in serialized form wi [...]
+To minimize the cost of serialization and deserialization, <%=vars.product_name%> avoids changing the data format whenever possible. This means your data may be stored in the cache in serialized or deserialized form, depending on how you use it. For example, if a server acts only as a storage location for data distribution between clients, it makes sense to leave the data in serialized form, ready to be transmitted to clients that request it. Partitioned region data is always stored in s [...]
 
 
diff --git a/docs/geode-native-docs/cpp-caching-api/serialization-options.html.md.erb b/docs/geode-native-docs/cpp-caching-api/serialization-options.html.md.erb
index b640c3e..045e6d2 100644
--- a/docs/geode-native-docs/cpp-caching-api/serialization-options.html.md.erb
+++ b/docs/geode-native-docs/cpp-caching-api/serialization-options.html.md.erb
@@ -19,9 +19,9 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-The C++ client API gives two serialization options: the `apache::geode::client::Serializable` interface and Geode PDX serialization.
+The C++ client API gives two serialization options: the `apache::geode::client::Serializable` interface and <%=vars.product_name%> PDX serialization.
 
-Geode Portable Data eXchange (PDX) serialization is the recommended option. PDX serialization provides portability for PDX serializable objects so that clients can share data with Java servers and other non-C++ clients. PDX is a cross-language data format that can reduce the cost of distributing and serializing your objects. PDX stores data in named fields that you can access individually in order to avoid the cost of deserializing the entire data object. PDX also allows you to mix versi [...]
+<%=vars.product_name%> Portable Data eXchange (PDX) serialization is the recommended option. PDX serialization provides portability for PDX serializable objects so that clients can share data with Java servers and other non-C++ clients. PDX is a cross-language data format that can reduce the cost of distributing and serializing your objects. PDX stores data in named fields that you can access individually in order to avoid the cost of deserializing the entire data object. PDX also allows [...]
 
 When using PDX serialization, you can use either `PdxSerializer` (for all your domain objects) or `PdxSerializable` (for a specific domain object).
 
@@ -59,7 +59,7 @@ The non-PDX serialization option is to use the `apache::geode::client::Serializa
 <td>X</td>
 </tr>
 <tr class="odd">
-<td><p>Automatically ported to other languages by Geode - no need to program Java-side implementation</p></td>
+<td><p>Automatically ported to other languages by <%=vars.product_name%> - no need to program Java-side implementation</p></td>
 <td></td>
 <td>X</td>
 </tr>
diff --git a/docs/geode-native-docs/cpp-caching-api/serialization-overview.html.md.erb b/docs/geode-native-docs/cpp-caching-api/serialization-overview.html.md.erb
index 7b530b6..b55c568 100644
--- a/docs/geode-native-docs/cpp-caching-api/serialization-overview.html.md.erb
+++ b/docs/geode-native-docs/cpp-caching-api/serialization-overview.html.md.erb
@@ -27,7 +27,7 @@ All data moving out of the client cache must be serializable.
 
 -   **[Data Serialization Options](serialization-options.html)**
 
-    The C++ client API provides two serialization options: the `apache::geode::client::Serializable` interface and Geode PDX serialization.
+    The C++ client API provides two serialization options: the `apache::geode::client::Serializable` interface and <%=vars.product_name%> PDX serialization.
 
 -   **[Serializing Data with PDX Serialization](pdx-serialization.html)**
 
@@ -35,7 +35,7 @@ All data moving out of the client cache must be serializable.
 
 -   **[Serializing Data with the Serializable Interface](serialization-using-serializable.html)**
 
-    The C++ client API provides a `Serializable` interface that you can use for fast and compact data serialization. This section discusses the Geode serializable interface, and presents implementation examples.
+    The C++ client API provides a `Serializable` interface that you can use for fast and compact data serialization. This section discusses the <%=vars.product_name%> serializable interface, and presents implementation examples.
 
 -   **[Serializing Object Graphs](object-graphs.html)**
 
diff --git a/docs/geode-native-docs/cpp-caching-api/serialization-using-serializable.html.md.erb b/docs/geode-native-docs/cpp-caching-api/serialization-using-serializable.html.md.erb
index 9b95e77..3a1edbe 100644
--- a/docs/geode-native-docs/cpp-caching-api/serialization-using-serializable.html.md.erb
+++ b/docs/geode-native-docs/cpp-caching-api/serialization-using-serializable.html.md.erb
@@ -19,17 +19,17 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-The C++ client API provides a `Serializable` interface that you can use for fast and compact data serialization. This section discusses the Geode serializable interface, and presents implementation examples.
+The C++ client API provides a `Serializable` interface that you can use for fast and compact data serialization. This section discusses the <%=vars.product_name%> serializable interface, and presents implementation examples.
 
 ## <a id="concept_696AB5206C3E45898CC1A24CDD93D003__section_8143F965A8C6495E8AB104FD36DA366A" class="no-quick-link"></a>How Serialization Works
 
-When your application puts an object into the cache for subsequent distribution, Geode serializes the data by taking these steps:
+When your application puts an object into the cache for subsequent distribution, <%=vars.product_name%> serializes the data by taking these steps:
 
 1.  Calls the appropriate `classId` function.
 2.  Writes the full `typeId` using the `classId` for the instance.
 3.  Invokes the instance’s `toData` function.
 
-When your application subsequently receives a byte array, Geode takes the following steps:
+When your application subsequently receives a byte array, <%=vars.product_name%> takes the following steps:
 
 1.  Decodes the `typeId`, extracts the `classId` from the `typeId`, then creates an object of the designated type using the registered factory functions.
 
diff --git a/docs/geode-native-docs/cpp-caching-api/using-pdxinstance.html.md.erb b/docs/geode-native-docs/cpp-caching-api/using-pdxinstance.html.md.erb
index 847f32a..4153dc4 100644
--- a/docs/geode-native-docs/cpp-caching-api/using-pdxinstance.html.md.erb
+++ b/docs/geode-native-docs/cpp-caching-api/using-pdxinstance.html.md.erb
@@ -19,7 +19,7 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-A `PdxInstance` is a lightweight wrapper around the raw bytes of the PDX serialized objects kept in the cache. It provides applications with run-time access to files of a PDX serialized object. Geode provides the implementation of the `PdxInstance` class.
+A `PdxInstance` is a lightweight wrapper around the raw bytes of the PDX serialized objects kept in the cache. It provides applications with run-time access to files of a PDX serialized object. <%=vars.product_name%> provides the implementation of the `PdxInstance` class.
 
 You can configure your cache to return a `PdxInstance` when a PDX serialized object is deserialized instead of deserializing the object to a domain class. Preventing deserialization saves both time and memory and does not require you deserialize the object to the domain class.
 
diff --git a/docs/geode-native-docs/cpp-caching-api/using-pdxinstancefactory.html.md.erb b/docs/geode-native-docs/cpp-caching-api/using-pdxinstancefactory.html.md.erb
index 940f67a..f1d755b 100644
--- a/docs/geode-native-docs/cpp-caching-api/using-pdxinstancefactory.html.md.erb
+++ b/docs/geode-native-docs/cpp-caching-api/using-pdxinstancefactory.html.md.erb
@@ -69,7 +69,7 @@ int main(int argc, char ** argv)
     CachePtr cachePtr = cacheFactory->set("cache-xml-file", 
                 "XMLs/clientPdxInstance.xml")->create();          
 
-    LOGINFO("Created the Geode Cache");
+    LOGINFO("Created the <%=vars.product_name%> Cache");
 
     // Get the example Region from the Cache which is declared in the 
     // Cache XML file.
diff --git a/docs/geode-native-docs/delta-propagation/delta-propagation-properties.html.md.erb b/docs/geode-native-docs/delta-propagation/delta-propagation-properties.html.md.erb
index d079127..1b4013c 100644
--- a/docs/geode-native-docs/delta-propagation/delta-propagation-properties.html.md.erb
+++ b/docs/geode-native-docs/delta-propagation/delta-propagation-properties.html.md.erb
@@ -19,7 +19,7 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-With cloning enabled, Geode does a deep copy of the object, using serialization. You can improve performance by implementing the appropriate `clone` method for your API, making a deep copy of anything to which a delta may be applied.
+With cloning enabled, <%=vars.product_name%> does a deep copy of the object, using serialization. You can improve performance by implementing the appropriate `clone` method for your API, making a deep copy of anything to which a delta may be applied.
 
 The goal is to significantly reduce the overhead of copying the object while still retaining the isolation needed for your deltas.
 
@@ -34,7 +34,7 @@ Cloning can be expensive, but it ensures that the new object is fully initialize
 Without cloning:
 
 -   It is possible for application code to read the entry value as it is being modified, possibly seeing the value in an intermediate, inconsistent state, with just part of the delta applied. You may choose to resolve this issue by having your application code synchronize on reads and writes.
--   Geode loses any reference to the old value because the old value is transformed in place into the new value. Because of this, your `CacheListener` sees the same new value returned for `EntryEvent.getOldValue` and `EntryEvent.getNewValue`.
+-   <%=vars.product_name%> loses any reference to the old value because the old value is transformed in place into the new value. Because of this, your `CacheListener` sees the same new value returned for `EntryEvent.getOldValue` and `EntryEvent.getNewValue`.
 -   Exceptions thrown from `fromDelta` may leave your cache in an inconsistent state. Without cloning, any interruption of the delta application could leave you with some fields in your cached object changed and others unchanged. If you do not use cloning, keep this in mind when you program your error handling in your `fromDelta` implementation.
 
 ## Enabling Cloning in cache.xml
diff --git a/docs/geode-native-docs/delta-propagation/delta-propagation.html.md.erb b/docs/geode-native-docs/delta-propagation/delta-propagation.html.md.erb
index 153d929..3ecb050 100644
--- a/docs/geode-native-docs/delta-propagation/delta-propagation.html.md.erb
+++ b/docs/geode-native-docs/delta-propagation/delta-propagation.html.md.erb
@@ -25,7 +25,7 @@ In most distributed data management systems, stored data is created once and upd
 
 -   **[How Delta Propagation Works](how-delta-propagation-works.html)**
 
-    Geode propagates object deltas using methods that you program on the client side. The methods are in the delta interface, which you implement in your cached objects’ classes.
+    <%=vars.product_name%> propagates object deltas using methods that you program on the client side. The methods are in the delta interface, which you implement in your cached objects’ classes.
 
 -   **[Delta Propagation API](delta-propagation-api.html)**
 
@@ -33,7 +33,7 @@ In most distributed data management systems, stored data is created once and upd
 
 -   **[Cloning](delta-propagation-properties.html)**
 
-    With cloning enabled, Geode does a deep copy of the object, using serialization. You can improve performance by implementing the appropriate `clone` method for your API, making a deep copy of anything to which a delta may be applied.
+    With cloning enabled, <%=vars.product_name%> does a deep copy of the object, using serialization. You can improve performance by implementing the appropriate `clone` method for your API, making a deep copy of anything to which a delta may be applied.
 
 -   **[Implementing Delta Propagation](implementing-delta-propagation.html)**
 
diff --git a/docs/geode-native-docs/delta-propagation/how-delta-propagation-works.html.md.erb b/docs/geode-native-docs/delta-propagation/how-delta-propagation-works.html.md.erb
index 138105f..25a820a 100644
--- a/docs/geode-native-docs/delta-propagation/how-delta-propagation-works.html.md.erb
+++ b/docs/geode-native-docs/delta-propagation/how-delta-propagation-works.html.md.erb
@@ -19,7 +19,7 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-Geode propagates object deltas using methods that you program on the client side. The methods are in the delta interface, which you implement in your cached objects’ classes.
+<%=vars.product_name%> propagates object deltas using methods that you program on the client side. The methods are in the delta interface, which you implement in your cached objects’ classes.
 
 This figure shows delta propagation for a change to an entry with key, `k`, and value object, `v`.
 
diff --git a/docs/geode-native-docs/delta-propagation/implementing-delta-propagation.html.md.erb b/docs/geode-native-docs/delta-propagation/implementing-delta-propagation.html.md.erb
index c77a656..4f5153c 100644
--- a/docs/geode-native-docs/delta-propagation/implementing-delta-propagation.html.md.erb
+++ b/docs/geode-native-docs/delta-propagation/implementing-delta-propagation.html.md.erb
@@ -30,7 +30,7 @@ For a complete delta propagation example, see
 -   Decide whether to enable cloning. Cloning is disabled by default. See [cloning-enabled](delta-propagation-properties.html#delta-propagation-properties).
 -   If you enable cloning, consider providing your own implementation, to optimize performance.
 -   If you do not enable cloning, be sure to synchronize your delta code.
--   If you do not enable cloning, review all associated listener code for dependencies on the entry event old value. Without cloning, Geode modifies the entry in place and so loses its reference to the old value. For delta events, the `EntryEvent` methods to retrieve the old and new values both return the new value.
+-   If you do not enable cloning, review all associated listener code for dependencies on the entry event old value. Without cloning, <%=vars.product_name%> modifies the entry in place and so loses its reference to the old value. For delta events, the `EntryEvent` methods to retrieve the old and new values both return the new value.
 
 **Procedure**
 
diff --git a/docs/geode-native-docs/dotnet-caching-api/cache-apis.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/cache-apis.html.md.erb
index 551b66d..75a736f 100644
--- a/docs/geode-native-docs/dotnet-caching-api/cache-apis.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/cache-apis.html.md.erb
@@ -22,6 +22,6 @@ limitations under the License.
 This section describes the `CacheFactory` and `Cache` classes.
 
 -   **CacheFactory class**. Creates a `Cache` instance based on the provided distributed system and cache configuration. Any `geode.properties` and `cache.xml` files provided to the application are used to initialize the system and cache. See [Setting System and Cache Properties](../setting-properties/chapter-overview.html#system_and_cache_properties). If a `cache.xml` file is used to create a cache and some of the regions already exist, a warning states that the regions exist and the ca [...]
--   **Cache class**. This class is the entry point to the Geode caching API. This class allows you to create regions. The cache is created by calling the `create` function of the `CacheFactory` class. When creating a cache, you specify a `DistributedSystem` that tells the new cache where to find other caches on the network and how to communicate with them.
+-   **Cache class**. This class is the entry point to the <%=vars.product_name%> caching API. This class allows you to create regions. The cache is created by calling the `create` function of the `CacheFactory` class. When creating a cache, you specify a `DistributedSystem` that tells the new cache where to find other caches on the network and how to communicate with them.
 
 
diff --git a/docs/geode-native-docs/dotnet-caching-api/csharp-dotnet-api.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/csharp-dotnet-api.html.md.erb
index 71bd750..ffd752d 100644
--- a/docs/geode-native-docs/dotnet-caching-api/csharp-dotnet-api.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/csharp-dotnet-api.html.md.erb
@@ -37,7 +37,7 @@ Using C\#, you can write callbacks and define user objects in the cache. The fol
 This chapter uses C\# as the reference language, but other .NET languages work the same way.
 
 The .NET API is provided in the `Apache.Geode.Client` namespace. This namespace allows you to manage your cache, regions, and data.
-Use the Geode .NET API to programmatically create, populate, and manage a distributed system.
+Use the <%=vars.product_name%> .NET API to programmatically create, populate, and manage a distributed system.
 
 **Note:**
 The .NET library is thread-safe except where otherwise indicated in the API documentation.
diff --git a/docs/geode-native-docs/dotnet-caching-api/csharp-dotnet-naming-conventions.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/csharp-dotnet-naming-conventions.html.md.erb
index f14bbea..fc72e4c 100644
--- a/docs/geode-native-docs/dotnet-caching-api/csharp-dotnet-naming-conventions.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/csharp-dotnet-naming-conventions.html.md.erb
@@ -23,7 +23,7 @@ Unless noted, the .NET API classes and functions have the same names as their C+
 
 The .NET interface names match those of comparable C++ interfaces, but with an ’I’ prepended to satisfy .NET naming conventions. For example, the .NET equivalent of the C++ `CacheLoader` interface is `ICacheLoader`.
 
-The name of the Geode `Serializable` interface is `IGeodeSerializable` because `ISerializable` is a .NET built-in type.
+The name of the <%=vars.product_name%> `Serializable` interface is `IGeodeSerializable` because `ISerializable` is a .NET built-in type.
 
 Where possible, get\* and set\* functions are replaced by .NET properties.
 
diff --git a/docs/geode-native-docs/dotnet-caching-api/data-serialization-apis.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/data-serialization-apis.html.md.erb
index 7b66144..124af9a 100644
--- a/docs/geode-native-docs/dotnet-caching-api/data-serialization-apis.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/data-serialization-apis.html.md.erb
@@ -23,13 +23,13 @@ Use either `IPdxSerializable` or `IGeodeSerializable` for each region. Do not mi
 
 For more information on these options, see [Data Serialization](dotnet-data-serialization.html#concept_28A7797A0342447ABF6A5014E0DCB05F).
 
--   **IPdxSerializable interface**. Provides a flexible way to serialize your domain objects for cache storage and transfer to the servers. This is a Geode built-in serialization framework. 
--   **IPdxReader**. Supplies operations for reading data from Geode IPDXSerializable types.
--   **IPdxWriter**. Provides operations for writing data into Geode IPDXSerializable types.
+-   **IPdxSerializable interface**. Provides a flexible way to serialize your domain objects for cache storage and transfer to the servers. This is a <%=vars.product_name%> built-in serialization framework. 
+-   **IPdxReader**. Supplies operations for reading data from <%=vars.product_name%> IPDXSerializable types.
+-   **IPdxWriter**. Provides operations for writing data into <%=vars.product_name%> IPDXSerializable types.
 -   **IPdxInstance**. Instance of a PDX serialized object that you can use to access the object’s data without having to deserialize the object first.
 -   **IPdxInstanceFactory**. Allows you to build an IPdxInstance using raw data.
 -   **IPdxTypeMapper interface**. Allows you to map .NET type names to Java type names when using PDX serialization.
--   **IGeodeSerializable interface**. Superclass of one set of user objects that can be serialized and stored in the cache. These are Geode built-in serializable types.
+-   **IGeodeSerializable interface**. Superclass of one set of user objects that can be serialized and stored in the cache. These are <%=vars.product_name%> built-in serializable types.
 -   **Serializable class**. Wraps the C++ `apache::geode::client::Serializable` objects as managed `IGeodeSerializable` objects. Whenever C++ clients and .NET clients interoperate and are part of the same distributed system, the user-defined types that are put by the C++ clients that have not been defined in .NET are returned as objects of this class.
 
     The API contains overloads for most Region methods and other methods that take `Serializable` as a value and that are more optimized than the more generic `IGeodeSerializable` overloads. The application prefers using these overloads whenever the base class of an object is `Serializable`.
diff --git a/docs/geode-native-docs/dotnet-caching-api/dotnet-adding-entry-to-cache.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/dotnet-adding-entry-to-cache.html.md.erb
index 7f219e9..4f4e489 100644
--- a/docs/geode-native-docs/dotnet-caching-api/dotnet-adding-entry-to-cache.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/dotnet-adding-entry-to-cache.html.md.erb
@@ -23,7 +23,7 @@ Populate a client region with cache entries by using the generic `IDictionary` A
 
 The `Put` function places a new value into a region entry with the specified key, while the `Create` function creates a new entry in the region. The `Put` and `Create` functions provide a user-defined parameter object to any cache writer invoked in the process.
 
-If a value for the entry key already exists in the cache when you add an entry, Geode overwrites the previously cached value. New values in the cache are propagated to the connected cache server.
+If a value for the entry key already exists in the cache when you add an entry, <%=vars.product_name%> overwrites the previously cached value. New values in the cache are propagated to the connected cache server.
 
 The .NET Generics provide type safety, so you cannot change your entry key and value types once you have begun to populate the region. If you need to use different types for the same region, store them all inside objects in the region.
 
diff --git a/docs/geode-native-docs/dotnet-caching-api/dotnet-caching-api.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/dotnet-caching-api.html.md.erb
index ceb14dd..67704b2 100644
--- a/docs/geode-native-docs/dotnet-caching-api/dotnet-caching-api.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/dotnet-caching-api.html.md.erb
@@ -45,7 +45,7 @@ See the [.NET API](http://geode.apache.org/docs/) documentation for API details.
 
 -   **[Creating a Cache](creating-a-cache.html)**
 
-    You create a cache using the Geode `CacheFactory.Create` call. Cache creation initializes the distributed system and creates the cache using your `geode.properties` and `cache.xml` file settings and any additional properties you provide to the call.
+    You create a cache using the <%=vars.product_name%> `CacheFactory.Create` call. Cache creation initializes the distributed system and creates the cache using your `geode.properties` and `cache.xml` file settings and any additional properties you provide to the call.
 
 -   **[Creating a Region](creating-a-region.html)**
 
@@ -65,7 +65,7 @@ See the [.NET API](http://geode.apache.org/docs/) documentation for API details.
 
 -   **[Data Serialization](dotnet-data-serialization.html)**
 
-    All data that Geode moves out of the local cache must be serializable.
+    All data that <%=vars.product_name%> moves out of the local cache must be serializable.
 
 -   **[Application Callbacks](application-callbacks.html)**
 
@@ -73,7 +73,7 @@ See the [.NET API](http://geode.apache.org/docs/) documentation for API details.
 
 -   **[A Simple C\# Example](simple-csharp-example.html)**
 
-    An example shows how to connect to Geode, create a cache and region, put and get keys and values, and disconnect.
+    An example shows how to connect to <%=vars.product_name%>, create a cache and region, put and get keys and values, and disconnect.
 
 -   **[Troubleshooting .NET Applications](troubleshooting-dotnet-applications.html)**
 
diff --git a/docs/geode-native-docs/dotnet-caching-api/dotnet-data-serialization-options.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/dotnet-data-serialization-options.html.md.erb
index 1e6823c..8326260 100644
--- a/docs/geode-native-docs/dotnet-caching-api/dotnet-data-serialization-options.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/dotnet-data-serialization-options.html.md.erb
@@ -19,17 +19,17 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-Built-in .NET types are serialized automatically into the cache and can be retrieved by Java servers and other Geode clients. For domain objects that are not simple types, you have three Geode serialization options.
+Built-in .NET types are serialized automatically into the cache and can be retrieved by Java servers and other <%=vars.product_name%> clients. For domain objects that are not simple types, you have three <%=vars.product_name%> serialization options.
 
-The options give good performance and flexibility for data storage, transfers, and language types. The Geode options can also improve performance in serializing and deserializing built-in types.
+The options give good performance and flexibility for data storage, transfers, and language types. The <%=vars.product_name%> options can also improve performance in serializing and deserializing built-in types.
 
-The simplest option is to use perform automatic serialization by registering the Geode .NET PDX reflection-based autoserializer in your application. When you have this registered, Geode uses it for all domain objects that are not custom serialized.
+The simplest option is to use perform automatic serialization by registering the <%=vars.product_name%> .NET PDX reflection-based autoserializer in your application. When you have this registered, <%=vars.product_name%> uses it for all domain objects that are not custom serialized.
 
-You can also custom serialize your objects by implementing one of the Geode .NET interfaces, `Apache.Geode.Client.IPdxSerializable` or `Apache.Geode.Client.IGeodeSerializable`.
+You can also custom serialize your objects by implementing one of the <%=vars.product_name%> .NET interfaces, `Apache.Geode.Client.IPdxSerializable` or `Apache.Geode.Client.IGeodeSerializable`.
 
 You also have the option of using default .NET serialization, but you cannot use it unless you also use helper classes. The helper classes you must use are `CacheableObject` and `CacheableObjectXml`.
 
-Geode .NET PDX serialization has more bytes in overhead than Geode .NET Data serialization, but using PDX serialization helps you avoid the performance costs of deserialization when performing queries. Applications can use `PdxInstances` in functions to avoid the deserialization of entire objects.
+<%=vars.product_name%> .NET PDX serialization has more bytes in overhead than <%=vars.product_name%> .NET Data serialization, but using PDX serialization helps you avoid the performance costs of deserialization when performing queries. Applications can use `PdxInstances` in functions to avoid the deserialization of entire objects.
 
 <a id="concept_6DC3DD288F6C4190AEA07DEDE76DD867__table_D61A94C4BFBE4712835F632F30BB488E"></a>
 
@@ -59,12 +59,12 @@ Geode .NET PDX serialization has more bytes in overhead than Geode .NET Data ser
 <td>X</td>
 </tr>
 <tr class="odd">
-<td><p>Automatically ported to other languages by Geode - no need to program Java-side implementation</p></td>
+<td><p>Automatically ported to other languages by <%=vars.product_name%> - no need to program Java-side implementation</p></td>
 <td></td>
 <td>X</td>
 </tr>
 <tr class="even">
-<td><p>Works with Geode delta propagation</p></td>
+<td><p>Works with <%=vars.product_name%> delta propagation</p></td>
 <td>X</td>
 <td>X (See explanation below.)</td>
 </tr>
@@ -74,6 +74,6 @@ Geode .NET PDX serialization has more bytes in overhead than Geode .NET Data ser
 
 \*You can mix domain object versions where the differences between versions are the addition and removal of object fields.
 
-By default, you can use Geode delta propagation with PDX serialization. However, delta propagation will not work if you have set the Geode property read-serialized to "true". In terms of deserialization, to apply a change delta propagation requires a domain class instance and the `fromDelta` method. If you have set read-serialized to true, you will receive an `IPdxInstance` instead of a domain class instance and `IPdxInstance` does not have the `fromDelta` method required for delta propa [...]
+By default, you can use <%=vars.product_name%> delta propagation with PDX serialization. However, delta propagation will not work if you have set the <%=vars.product_name%> property read-serialized to "true". In terms of deserialization, to apply a change delta propagation requires a domain class instance and the `fromDelta` method. If you have set read-serialized to true, you will receive an `IPdxInstance` instead of a domain class instance and `IPdxInstance` does not have the `fromDelt [...]
 
 
diff --git a/docs/geode-native-docs/dotnet-caching-api/dotnet-data-serialization.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/dotnet-data-serialization.html.md.erb
index e919bf9..10c4823 100644
--- a/docs/geode-native-docs/dotnet-caching-api/dotnet-data-serialization.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/dotnet-data-serialization.html.md.erb
@@ -31,5 +31,5 @@ Region data that must be serializable falls under the following categories:
 -   Regions that receive events from remote caches.
 -   Regions that provide function arguments and results.
 
-To minimize the cost of serialization and deserialization, Geode avoids changing the data format whenever possible. This means your data may be stored in the cache in serialized or deserialized form, depending on how you use it. For example, if a server acts only as a storage location for data distribution between clients, it makes sense to leave the data in serialized form, ready to be transmitted to clients that request it. Partitioned region data is always stored in serialized form wi [...]
+To minimize the cost of serialization and deserialization, <%=vars.product_name%> avoids changing the data format whenever possible. This means your data may be stored in the cache in serialized or deserialized form, depending on how you use it. For example, if a server acts only as a storage location for data distribution between clients, it makes sense to leave the data in serialized form, ready to be transmitted to clients that request it. Partitioned region data is always stored in s [...]
 
diff --git a/docs/geode-native-docs/dotnet-caching-api/dotnet-pdx-autoserializer.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/dotnet-pdx-autoserializer.html.md.erb
index d4c90b6..19c2112 100644
--- a/docs/geode-native-docs/dotnet-caching-api/dotnet-pdx-autoserializer.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/dotnet-pdx-autoserializer.html.md.erb
@@ -1,6 +1,4 @@
----
-title:  Serialize Using the Geode PDX Autoserializer
----
+<% set_title("Serialize Using the", product_name, "PDX Autoserializer") %>
 
 <!--
 Licensed to the Apache Software Foundation (ASF) under one or more
@@ -19,7 +17,7 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-When you register the reflection-based serializer, Geode uses it to serialize all objects that do not implement `IPdxSerializable` or `IGeodeSerializable`. You can customize the auto-serialization behavior for your domain objects by adding serialization attributes to your object’s fields.
+When you register the reflection-based serializer, <%=vars.product_name%> uses it to serialize all objects that do not implement `IPdxSerializable` or `IGeodeSerializable`. You can customize the auto-serialization behavior for your domain objects by adding serialization attributes to your object’s fields.
 
 **Procedure**
 
@@ -69,6 +67,6 @@ When you register the reflection-based serializer, Geode uses it to serialize al
         [NonSerialized] private int myLocalData;
         ```
 
-For each domain class Geode serializes using the autoserializer, all fields are considered for serialization except those defined as `static`, `literal` or `readonly` and those you explicitly exclude using the .NET `NonSerialized` attribute.
+For each domain class <%=vars.product_name%> serializes using the autoserializer, all fields are considered for serialization except those defined as `static`, `literal` or `readonly` and those you explicitly exclude using the .NET `NonSerialized` attribute.
 
 
diff --git a/docs/geode-native-docs/dotnet-caching-api/dotnet-pdx-serialization-features.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/dotnet-pdx-serialization-features.html.md.erb
index 1315b60..6684bf9 100644
--- a/docs/geode-native-docs/dotnet-caching-api/dotnet-pdx-serialization-features.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/dotnet-pdx-serialization-features.html.md.erb
@@ -1,6 +1,4 @@
----
-title:  Geode PDX Serialization Features
----
+<% set_title(product_name, "PDX Serialization Features") %>
 
 <!--
 Licensed to the Apache Software Foundation (ASF) under one or more
@@ -19,7 +17,7 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-Geode PDX serialization offers several advantages.
+<%=vars.product_name%> PDX serialization offers several advantages.
 
 ## <a id="concept_E8DCAA3027B64C0C8213A0DF2D773BF4__section_8F8D96A0DAC3416DA90622D0E240F54A" class="no-quick-link"></a>Application Versioning of PDX Domain Objects
 
@@ -27,11 +25,11 @@ Domain objects evolve along with your application code. You may create an addres
 
 With PDX, you can use old and new versions of domain objects together in a distributed system if the versions differ by the addition or removal of fields. This compatibility lets you gradually introduce modified code and data into the system, without bringing the system down.
 
-Geode maintains a central registry of the PDX domain object metadata. Using the registry, Geode preserves fields in each member's cache regardless of whether the member has the field defined. When a member receives an object that has a field registered that the member is not aware of, the member does not access the field, but preserves it and passes it along with the rest of the object to other members. When a member receives an object that is missing one or more fields according to the  [...]
+<%=vars.product_name%> maintains a central registry of the PDX domain object metadata. Using the registry, <%=vars.product_name%> preserves fields in each member's cache regardless of whether the member has the field defined. When a member receives an object that has a field registered that the member is not aware of, the member does not access the field, but preserves it and passes it along with the rest of the object to other members. When a member receives an object that is missing on [...]
 
 ## <a id="concept_E8DCAA3027B64C0C8213A0DF2D773BF4__section_4CD0072C619F4F0496B73597B92B2289" class="no-quick-link"></a>Portability of PDX Serializable Objects
 
-When you create an `IPdxSerializable` object, Geode stores the object's type information in a central registry. The information is passed between peers, between clients and servers, and between distributed systems.
+When you create an `IPdxSerializable` object, <%=vars.product_name%> stores the object's type information in a central registry. The information is passed between peers, between clients and servers, and between distributed systems.
 
 This offers a notable advantage to the .NET client, which shares data with Java cache servers. Clients automatically pass registry information to servers when they store an `IPdxSerializable` object. Clients can run queries and functions against the data in the servers without the servers needing to know anything about the stored objects. One client can store data on the server to be retrieved by another client, with the server never needing to know the object type. This means you can co [...]
 
diff --git a/docs/geode-native-docs/dotnet-caching-api/dotnet-pdx-serialization.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/dotnet-pdx-serialization.html.md.erb
index 6192a3d..30751b9 100644
--- a/docs/geode-native-docs/dotnet-caching-api/dotnet-pdx-serialization.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/dotnet-pdx-serialization.html.md.erb
@@ -19,8 +19,8 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-Geode's Portable Data eXchange (PDX) is a cross-language data format that can reduce the cost of distributing and serializing your objects. PDX stores data in named fields that you can access individually, to avoid the cost of deserializing the entire data object. PDX also allows you to mix versions of objects where you have added or removed fields.
+<%=vars.product_name%>'s Portable Data eXchange (PDX) is a cross-language data format that can reduce the cost of distributing and serializing your objects. PDX stores data in named fields that you can access individually, to avoid the cost of deserializing the entire data object. PDX also allows you to mix versions of objects where you have added or removed fields.
 
-You have two options for Geode PDX serialization when using the .NET caching API. You can program your domain objects using the `IPdxSerializable` interface, or you can use Geode’s reflection-based autoserializer.
+You have two options for <%=vars.product_name%> PDX serialization when using the .NET caching API. You can program your domain objects using the `IPdxSerializable` interface, or you can use <%=vars.product_name%>’s reflection-based autoserializer.
 
 
diff --git a/docs/geode-native-docs/dotnet-caching-api/event-handling-apis.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/event-handling-apis.html.md.erb
index c0f04c7..a481b11 100644
--- a/docs/geode-native-docs/dotnet-caching-api/event-handling-apis.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/event-handling-apis.html.md.erb
@@ -19,9 +19,9 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-Code your event handlers to do minimal work before returning control to Geode.
+Code your event handlers to do minimal work before returning control to <%=vars.product_name%>.
 
-For example, a listener implementation may hand off the event to a thread pool that processes the event on its thread rather than the listener thread. Exceptions thrown by the listeners are caught by Geode and logged.
+For example, a listener implementation may hand off the event to a thread pool that processes the event on its thread rather than the listener thread. Exceptions thrown by the listeners are caught by <%=vars.product_name%> and logged.
 
 -   **RegionEvent class**. Provides information about the event, such as what region the event originated in, whether the event originated in a cache remote to the event handler, and whether the event resulted from a distributed operation.
 -   **EntryEvent class**. Provides all available information for the `RegionEvent`. It also provides entry-specific information, such as the old and new entry values and whether the event resulted from a load operation.
diff --git a/docs/geode-native-docs/dotnet-caching-api/how-igfserializable-works.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/how-igfserializable-works.html.md.erb
index 6008497..d524eb8 100644
--- a/docs/geode-native-docs/dotnet-caching-api/how-igfserializable-works.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/how-igfserializable-works.html.md.erb
@@ -19,13 +19,13 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-When your application puts an object into the cache for distribution, Geode serializes the data by taking these steps.
+When your application puts an object into the cache for distribution, <%=vars.product_name%> serializes the data by taking these steps.
 
 1.  Calls the appropriate `ClassId` function and creates the `TypeId` from it.
 2.  Writes the `TypeId` for the instance.
 3.  Invokes the `ToData` function for the instance.
 
-When your application subsequently receives a byte array, Geode takes the following steps:
+When your application subsequently receives a byte array, <%=vars.product_name%> takes the following steps:
 
 1.  Decodes the `TypeId` and creates an object of the designated type, using the registered factory functions.
 2.  Invokes the `FromData` function with input from the data stream.
diff --git a/docs/geode-native-docs/dotnet-caching-api/implementing-igfserializable.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/implementing-igfserializable.html.md.erb
index e9daee6..7cdf6d6 100644
--- a/docs/geode-native-docs/dotnet-caching-api/implementing-igfserializable.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/implementing-igfserializable.html.md.erb
@@ -19,7 +19,7 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-To store your own data types in the cache, you implement the Geode `IGeodeSerializable` interface.
+To store your own data types in the cache, you implement the <%=vars.product_name%> `IGeodeSerializable` interface.
 
 Examples follow the procedure.
 
diff --git a/docs/geode-native-docs/dotnet-caching-api/other-apis.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/other-apis.html.md.erb
index 9f08610..f409832 100644
--- a/docs/geode-native-docs/dotnet-caching-api/other-apis.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/other-apis.html.md.erb
@@ -22,7 +22,7 @@ limitations under the License.
 This section describes classes for property collections and logging.
 
 -   **Properties** **class**. Provides a collection of properties, each of which is a key/value pair. Each key is a string, and the value can be a string or an integer.
--   **Log class**. Defines methods available to clients that need to write a log message to their Geode system shared log file. Any attempt to use an instance after its connection is disconnected throws a **NotConnectedException**. For any logged message the log file contains:
+-   **Log class**. Defines methods available to clients that need to write a log message to their <%=vars.product_name%> system shared log file. Any attempt to use an instance after its connection is disconnected throws a **NotConnectedException**. For any logged message the log file contains:
     -   The log level of the message.
     -   The time the message was logged.
     -   The ID of the connection and thread that logged the message.
diff --git a/docs/geode-native-docs/dotnet-caching-api/primary-apis-cache-generic.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/primary-apis-cache-generic.html.md.erb
index 1470b8b..47bd285 100644
--- a/docs/geode-native-docs/dotnet-caching-api/primary-apis-cache-generic.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/primary-apis-cache-generic.html.md.erb
@@ -38,7 +38,7 @@ Declarative configuration via XML of application plug-ins such as cache listener
 
 -   **[Event Handling APIs](event-handling-apis.html)**
 
-    Code your event handlers to do minimal work before returning control to Geode.
+    Code your event handlers to do minimal work before returning control to <%=vars.product_name%>.
 
 -   **[Property Collections and Logging APIs](other-apis.html)**
 
diff --git a/docs/geode-native-docs/dotnet-caching-api/problem-scenarios.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/problem-scenarios.html.md.erb
index ca932a7..7e48db2 100644
--- a/docs/geode-native-docs/dotnet-caching-api/problem-scenarios.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/problem-scenarios.html.md.erb
@@ -24,18 +24,18 @@ These scenarios describe processes and implementations that should be avoided wh
 
 ## <a id="concept_025AAAF8896C4F4CB4530EE9CEEF4BAE__section_FFC3E18AD8F042DA9EFB42852242AAE0" class="no-quick-link"></a>Using Application Callbacks
 
-**Scenario:** A .NET thread loads the Geode DLL in application domain `AD1`. This thread may have access to the other domains in the application if code access security allows it. This thread can then call `AppDomain.CreateInstance` to create a callback object ( `ICacheListener`, `ICacheLoader`, or `ICacheWriter`) in another domain called `AD2`. If the callback object is marshaled by reference, the callback is executed in the domain where it is created (`AD2`). The thread that loads the  [...]
+**Scenario:** A .NET thread loads the <%=vars.product_name%> DLL in application domain `AD1`. This thread may have access to the other domains in the application if code access security allows it. This thread can then call `AppDomain.CreateInstance` to create a callback object ( `ICacheListener`, `ICacheLoader`, or `ICacheWriter`) in another domain called `AD2`. If the callback object is marshaled by reference, the callback is executed in the domain where it is created (`AD2`). The threa [...]
 
-**Resolution:** When an application creates and unloads application domains it should ensure that the application domain where the Geode .NET DLL is loaded is the same domain where the application callback and `IGeodeSerializable` objects are created.
+**Resolution:** When an application creates and unloads application domains it should ensure that the application domain where the <%=vars.product_name%> .NET DLL is loaded is the same domain where the application callback and `IGeodeSerializable` objects are created.
 
 ## <a id="concept_025AAAF8896C4F4CB4530EE9CEEF4BAE__section_9FEC4666F4FD467AA57AD70943703F00" class="no-quick-link"></a>Loading an Application DLL in Multiple AppDomains
 
-**Scenario:** The application loads the Geode DLL in one application domain, then reloads the Geode DLL in another application domain (with or without unloading the previous `AppDomain` ). The callbacks, as well as other interface implementations, like `IPdxSerializable` and `IGeodeSerializable`, throw exceptions because the C++ code does not know about the `AppDomain` and is loaded only once in the initial `AppDomain`.
+**Scenario:** The application loads the <%=vars.product_name%> DLL in one application domain, then reloads the <%=vars.product_name%> DLL in another application domain (with or without unloading the previous `AppDomain` ). The callbacks, as well as other interface implementations, like `IPdxSerializable` and `IGeodeSerializable`, throw exceptions because the C++ code does not know about the `AppDomain` and is loaded only once in the initial `AppDomain`.
 
-**Resolution:** The application should always use the first `AppDomain` to load the Geode DLL, or it should not load the Geode DLL multiple times.
+**Resolution:** The application should always use the first `AppDomain` to load the <%=vars.product_name%> DLL, or it should not load the <%=vars.product_name%> DLL multiple times.
 
 ## <a id="concept_025AAAF8896C4F4CB4530EE9CEEF4BAE__section_646373554C764DD3A919A906A5F05EE9" class="no-quick-link"></a>Inside IIS
 
 **Scenario:** When you deploy more than one web application inside an Internet Information Service (IIS), the IIS creates an appdomain subprocess for each web application in the single process, but the C++ client cache instance remains a singleton in the process. Because of this, you can run into conflicts between cache creation and closure by the different appdomains. For example, if one appdomain calls `cache.close`, it closes the cache for the entire process. Any further cache access  [...]
 
-**Resolution:** `Cache create`/`close` provides reference counting of `Cache` `create` and `close`. Each process can use the counter to make sure it creates the `Cache` once and closes it once. To enable this, set the Geode system property, `appdomain-enabled` to true .
+**Resolution:** `Cache create`/`close` provides reference counting of `Cache` `create` and `close`. Each process can use the counter to make sure it creates the `Cache` once and closes it once. To enable this, set the <%=vars.product_name%> system property, `appdomain-enabled` to true .
diff --git a/docs/geode-native-docs/dotnet-caching-api/serializable-types.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/serializable-types.html.md.erb
index 70f84d3..081d21d 100644
--- a/docs/geode-native-docs/dotnet-caching-api/serializable-types.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/serializable-types.html.md.erb
@@ -32,5 +32,5 @@ If you have data that is best handled as a blob, such as structs that do not con
 If you have a graph of objects in which each node can be serializable, the parent node calls `DataOutput.WriteObject` to delegate the serialization responsibility to its child nodes. Similarly, your application calls `DataInput.ReadObject` to deserialize the object graph.
 
 **Note:**
-The Geode `IGeodeSerializable` interface does not support object graphs with multiple references to the same object. If your application uses these types of circular graphs, you must address this design concern explicitly.
+The <%=vars.product_name%> `IGeodeSerializable` interface does not support object graphs with multiple references to the same object. If your application uses these types of circular graphs, you must address this design concern explicitly.
 
diff --git a/docs/geode-native-docs/dotnet-caching-api/serialize-using-igfserializable.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/serialize-using-igfserializable.html.md.erb
index 7c7bce8..a90a7b9 100644
--- a/docs/geode-native-docs/dotnet-caching-api/serialize-using-igfserializable.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/serialize-using-igfserializable.html.md.erb
@@ -27,11 +27,11 @@ The .NET `IGeodeSerializable` interface provides fast and compact data serializa
 
 -   **[How Serialization Works with IGeodeSerializable](how-igfserializable-works.html)**
 
-    When your application puts an object into the cache for distribution, Geode serializes the data by taking these steps.
+    When your application puts an object into the cache for distribution, <%=vars.product_name%> serializes the data by taking these steps.
 
 -   **[Implement the IGeodeSerializable Interface](implementing-igfserializable.html)**
 
-    To store your own data types in the cache, you implement the Geode `IGeodeSerializable` interface.
+    To store your own data types in the cache, you implement the <%=vars.product_name%> `IGeodeSerializable` interface.
 
 -   **[Register the Type](registering-the-type.html)**
 
diff --git a/docs/geode-native-docs/dotnet-caching-api/serialize-using-ipdxserializable.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/serialize-using-ipdxserializable.html.md.erb
index f007650..cddda23 100644
--- a/docs/geode-native-docs/dotnet-caching-api/serialize-using-ipdxserializable.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/serialize-using-ipdxserializable.html.md.erb
@@ -36,8 +36,8 @@ Use this procedure to program your domain object for PDX serialization using the
     If you also use PDX serialization in Java 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 identify fields.
 
 3.  Program the `IPdxSerializable ToData` function to serialize your object as required by your application.
-    1.  Write your domain class's standard .NET data fields using the `IPdxWriter` write methods. Geode automatically provides `IPdxWriter` to the `ToData` function for `IPdxSerializable` objects.
-    2.  Call the `ToData markIdentifyField` function for each field Geode should use to identify your object. This is used to compare objects for operations like `DISTINCT` queries. The `markIdentifyField` call must come after the associated field write methods.
+    1.  Write your domain class's standard .NET data fields using the `IPdxWriter` write methods. <%=vars.product_name%> automatically provides `IPdxWriter` to the `ToData` function for `IPdxSerializable` objects.
+    2.  Call the `ToData markIdentifyField` function for each field <%=vars.product_name%> should use to identify your object. This is used to compare objects for operations like `DISTINCT` queries. The `markIdentifyField` call must come after the associated field write methods.
 
         Example:
 
@@ -75,7 +75,7 @@ Use this procedure to program your domain object for PDX serialization using the
         }
         ```
 
-4.  Program `IPdxSerializable FromData` to read your data fields from the serialized form into the object's fields using the `IPdxReader` read methods. Geode automatically provides `IPdxReader` to the `FromData` function for `IPdxSerializable` objects.
+4.  Program `IPdxSerializable FromData` to read your data fields from the serialized form into the object's fields using the `IPdxReader` read methods. <%=vars.product_name%> automatically provides `IPdxReader` to the `FromData` function for `IPdxSerializable` objects.
 
     Use the same names as you did in `ToData` and call the read operations in the same order as you called the write operations in your `ToData` implementation.
 
diff --git a/docs/geode-native-docs/dotnet-caching-api/simple-csharp-example.html.md.erb b/docs/geode-native-docs/dotnet-caching-api/simple-csharp-example.html.md.erb
index 326325b..c4e392d 100644
--- a/docs/geode-native-docs/dotnet-caching-api/simple-csharp-example.html.md.erb
+++ b/docs/geode-native-docs/dotnet-caching-api/simple-csharp-example.html.md.erb
@@ -19,7 +19,7 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-An example shows how to connect to Geode, create a cache and region, put and get keys and values, and disconnect.
+An example shows how to connect to <%=vars.product_name%>, create a cache and region, put and get keys and values, and disconnect.
 
 ## Simple C\# Code
 
diff --git a/docs/geode-native-docs/function-execution/executing-functions.html.md.erb b/docs/geode-native-docs/function-execution/executing-functions.html.md.erb
index 2840eac..038017a 100644
--- a/docs/geode-native-docs/function-execution/executing-functions.html.md.erb
+++ b/docs/geode-native-docs/function-execution/executing-functions.html.md.erb
@@ -31,7 +31,7 @@ See the server-side function execution information at
 
 -   **[Programming to Get Function Results](handling-function-results.html)**
 
-    Geode provides a default result collector. If you need special results handling, code a custom `ResultsCollector` implementation to replace the provided default. Use the `Execution::withCollector` method to define your custom collector.
+    <%=vars.product_name%> provides a default result collector. If you need special results handling, code a custom `ResultsCollector` implementation to replace the provided default. Use the `Execution::withCollector` method to define your custom collector.
 
 -   **[Solutions and Use Cases](solutions-use-cases.html)**
 
diff --git a/docs/geode-native-docs/function-execution/handling-function-results.html.md.erb b/docs/geode-native-docs/function-execution/handling-function-results.html.md.erb
index bc4c190..d6f569f 100644
--- a/docs/geode-native-docs/function-execution/handling-function-results.html.md.erb
+++ b/docs/geode-native-docs/function-execution/handling-function-results.html.md.erb
@@ -39,11 +39,11 @@ The `getResult` methods of the default result collector block until all results
 
 To handle the results in a custom manner:
 
-1.  Write a class that implements the `ResultCollector` interface to handle the results in a custom manner. The methods are of two types: one handles data and information from Geode and populates the results set, while the other returns the compiled results to the calling application:
+1.  Write a class that implements the `ResultCollector` interface to handle the results in a custom manner. The methods are of two types: one handles data and information from <%=vars.product_name%> and populates the results set, while the other returns the compiled results to the calling application:
     -  `addResult` is called when results arrive from the `Function` methods. Use `addResult` to add a single result to the ResultCollector.
     -  `endResults` is called to signal the end of all results from the function execution.
     -  `getResult` is available to your executing application (the one that calls `Execution.execute`) to retrieve the results. This may block until all results are available.
-    -  `clearResults` is called to clear partial results from the results collector. This is used only for highly available `onRegion` functions where the calling application waits for the results. If the call fails, before Geode retries the execution, it calls `clearResults` to ready the instance for a clean set of results.
+    -  `clearResults` is called to clear partial results from the results collector. This is used only for highly available `onRegion` functions where the calling application waits for the results. If the call fails, before <%=vars.product_name%> retries the execution, it calls `clearResults` to ready the instance for a clean set of results.
 2.  Use the `Execution` object in your executing member to call `withCollector`, passing your custom collector, as shown in the example above.
 
 
diff --git a/docs/geode-native-docs/function-execution/how-functions-execute.html.md.erb b/docs/geode-native-docs/function-execution/how-functions-execute.html.md.erb
index f22ed50..04c0984 100644
--- a/docs/geode-native-docs/function-execution/how-functions-execute.html.md.erb
+++ b/docs/geode-native-docs/function-execution/how-functions-execute.html.md.erb
@@ -30,7 +30,7 @@ This section discusses the basic function execution process, how highly availabl
 
 ## <a id="how-functions-execute__section_08C66E4B3D934ADC8587DF1E3766C9FD" class="no-quick-link"></a>How Highly Available Functions Execute after a Failure
 
-If a failure occurs in function execution, the error is returned to the calling application. You can code for high availability for `onRegion` functions that return a result, so the function is automatically retried. For information on setting this up on the server side, see [Executing a Function in Apache Geode](geodeman/developing/function_exec/function_execution.html). To use a highly available function, the client must call the results collector `getResult` method. When an execution  [...]
+If a failure occurs in function execution, the error is returned to the calling application. You can code for high availability for `onRegion` functions that return a result, so the function is automatically retried. For information on setting this up on the server side, see [Executing a Function in <%=vars.product_name_long%>](geodeman/developing/function_exec/function_execution.html). To use a highly available function, the client must call the results collector `getResult` method. Whe [...]
 
 1.  Waits for all calls to return.
 2.  Sets a boolean indicating a reexecution is being done.
diff --git a/docs/geode-native-docs/function-execution/solutions-use-cases.html.md.erb b/docs/geode-native-docs/function-execution/solutions-use-cases.html.md.erb
index 6df5f6b..c3b3cd2 100644
--- a/docs/geode-native-docs/function-execution/solutions-use-cases.html.md.erb
+++ b/docs/geode-native-docs/function-execution/solutions-use-cases.html.md.erb
@@ -21,7 +21,7 @@ limitations under the License.
 
 The function execution service provides solutions for these application use cases:
 
--   An application that executes a server-side transaction or makes data updates using the Geode distributed locking service.
+-   An application that executes a server-side transaction or makes data updates using the <%=vars.product_name%> distributed locking service.
 -   An application that initializes some of its components once on each server, which might be used later by executed functions.
 -   Initialization and startup of a third-party service, such as a messaging service.
 -   Any arbitrary aggregation operation that requires iteration over local data sets that can be done more efficiently through a single call to the cache server.
diff --git a/docs/geode-native-docs/glossary.html.md.erb b/docs/geode-native-docs/glossary.html.md.erb
index ae09a55..a2643be 100644
--- a/docs/geode-native-docs/glossary.html.md.erb
+++ b/docs/geode-native-docs/glossary.html.md.erb
@@ -23,11 +23,11 @@ This glossary defines terms used in the documentation.
 
 ## API
 
-Application Programming Interface. Geode provides APIs to cached data for C++ and .NET applications.
+Application Programming Interface. <%=vars.product_name%> provides APIs to cached data for C++ and .NET applications.
 
 ## application program
 
-A program designed to perform a specific function directly for the user or, in some cases, for another application program. Geode applications use the Geode application programming interfaces (APIs) to modify cached data.
+A program designed to perform a specific function directly for the user or, in some cases, for another application program. <%=vars.product_name%> applications use the <%=vars.product_name%> application programming interfaces (APIs) to modify cached data.
 
 ## cache
 
@@ -35,7 +35,7 @@ A cache created by an application or cache server process. For the process, its
 
 ## cache configuration file
 
-An XML file that declares the initial configuration of a cache, commonly named `cache.xml`. C++ and .NET applications can configure the cache additionally through the Geode programming APIs.
+An XML file that declares the initial configuration of a cache, commonly named `cache.xml`. C++ and .NET applications can configure the cache additionally through the <%=vars.product_name%> programming APIs.
 
 ## cache listener
 
@@ -55,7 +55,7 @@ User-implemented plug-in intended for synchronizing the cache with an outside da
 
 ## caching enabled
 
-Specifies whether data is cached in the region. Geode gives you the option of running applications without entry caching. For example, you can configure a distributed system as a simple messaging service.
+Specifies whether data is cached in the region. <%=vars.product_name%> gives you the option of running applications without entry caching. For example, you can configure a distributed system as a simple messaging service.
 
 ## client
 
@@ -67,7 +67,7 @@ An estimate of the number of threads expected to concurrently modify values in t
 
 ## connection
 
-What an application uses to access a Geode distributed system. An application can connect to a Geode system by calling the `DistributedSystem::connect` function with the appropriate parameter settings. An application must connect to a distributed system to gain access to Geode functionality.
+What an application uses to access a <%=vars.product_name%> distributed system. An application can connect to a <%=vars.product_name%> system by calling the `DistributedSystem::connect` function with the appropriate parameter settings. An application must connect to a distributed system to gain access to <%=vars.product_name%> functionality.
 
 ## destroy
 
@@ -83,7 +83,7 @@ Enables a region to automatically send entry value updates to remote caches and
 
 ## distributed system
 
-One or more Geode system members that have been configured to communicate with each other, forming a single, logical system. Also used for the object that is instantiated to create the connection between the distributed system members.
+One or more <%=vars.product_name%> system members that have been configured to communicate with each other, forming a single, logical system. Also used for the object that is instantiated to create the connection between the distributed system members.
 
 ## DTD
 
@@ -159,11 +159,11 @@ A region attribute that sets the maximum number of entries to hold in a caching
 
 ## membership
 
-Applications and cache servers connect to a Geode distributed system by invoking the static function `DistributedSystem::connect`. Through this connection, the application gains access to the APIs for distributed data caches. When a C++ or .NET application connects to a distributed system, it specifies the system it is connecting to by indicating the communication protocol and address to use to find other system members.
+Applications and cache servers connect to a <%=vars.product_name%> distributed system by invoking the static function `DistributedSystem::connect`. Through this connection, the application gains access to the APIs for distributed data caches. When a C++ or .NET application connects to a distributed system, it specifies the system it is connecting to by indicating the communication protocol and address to use to find other system members.
 
 ## <a id="nc_glossary_netSearch" class="no-quick-link"></a>netSearch
 
-The method used by Geode to search remote caches for a data entry that is not found in the local cache region. This operates only on distributed regions.
+The method used by <%=vars.product_name%> to search remote caches for a data entry that is not found in the local cache region. This operates only on distributed regions.
 
 ## <a id="nc_glossary_overflows" class="no-quick-link"></a>overflows
 
diff --git a/docs/geode-native-docs/introduction/client-configurations.html.md.erb b/docs/geode-native-docs/introduction/client-configurations.html.md.erb
index 353ea56..ca462bb 100644
--- a/docs/geode-native-docs/introduction/client-configurations.html.md.erb
+++ b/docs/geode-native-docs/introduction/client-configurations.html.md.erb
@@ -1,6 +1,4 @@
----
-title:  Apache Geode Client Configurations
----
+<% set_title(product_name_long, "Client Configurations") %>
 
 <!--
 Licensed to the Apache Software Foundation (ASF) under one or more
@@ -19,7 +17,7 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-The Apache Geode client provides access for C++ and Microsoft® .NET™ clients to the Geode distributed system. 
+The <%=vars.product_name_long%> client provides access for C++ and Microsoft® .NET™ clients to the <%=vars.product_name%> distributed system. 
 As an open source project, the client (at least theoretically) can be built on nearly any system.
 In practical terms, the client is known to have been successfully built and used on platforms running Microsoft Windows, Linux (Intel), and Sun Solaris.
 
@@ -92,7 +90,7 @@ For your convenience, this table shows configuration guidelines for some familia
 
 ## Host Machine Configuration Guidelines
 
-Each machine that runs a Geode client should meet the following guidelines:
+Each machine that runs a <%=vars.product_name%> client should meet the following guidelines:
 
 -   A system clock set to the correct time and a time synchronization
 service such as Network Time Protocol (NTP).
@@ -123,16 +121,16 @@ and can be triggered by a running distributed system.
 
 **Runtime Library**
 
-The Geode client requires the [Microsoft Visual C++ 2013 Redistributable Package](https://www.microsoft.com/en-us/download/details.aspx?id=40784). 
+The <%=vars.product_name%> client requires the [Microsoft Visual C++ 2013 Redistributable Package](https://www.microsoft.com/en-us/download/details.aspx?id=40784). 
 This package contains runtime libraries needed by the client; install it for your platform architecture on all machines that will run the client.
 
 **.NET Framework Version Support**
 
-The Geode client is supported with Microsoft .NET Framework 4.5.2.
+The <%=vars.product_name%> client is supported with Microsoft .NET Framework 4.5.2.
 
 A Microsoft .NET Framework must be installed to support the C++/CLI (Common Language Infrastructure) library for the client.
 
-The Geode supports .NET 4.5.2 and Visual Studio 2013 (for compiling C++ applications on Windows). 
+The <%=vars.product_name%> supports .NET 4.5.2 and Visual Studio 2013 (for compiling C++ applications on Windows). 
 For more information on the features of .NET and Visual Studio Community Edition 2013 Update 5, see the [Visual Studio 2013 web page](https://msdn.microsoft.com/en-us/library/dd831853(v=vs.120).aspx).
 
 ## <a id="concept_7AE0C1CB11244095A50CCB52A09A09A1__section_C5848F353C504844BAFFD3EB2BE7DA23" class="no-quick-link"></a>Linux
@@ -142,7 +140,7 @@ For Linux, you can verify that you meet the client dependencies at the library l
 ``` pre
 prompt> ldd $client-installdir/lib/libgfcppcache.so
 ```
-where _client-installdir_ is the location in which you have installed the Geode client.
+where _client-installdir_ is the location in which you have installed the <%=vars.product_name%> client.
 
 The following libraries are external dependencies of the client library, `libgfcppcache.so`. Verify that the ldd tool output includes all of these:
 
@@ -155,7 +153,7 @@ The following libraries are external dependencies of the client library, `libgfc
 
 ## <a id="concept_7AE0C1CB11244095A50CCB52A09A09A1__ssl_requirements" class="no-quick-link"></a>Software Requirements for Using SSL
 
-If you plan on using SSL in your Geode client and server deployment, you will need to download and install OpenSSL.
+If you plan on using SSL in your <%=vars.product_name%> client and server deployment, you will need to download and install OpenSSL.
 
 The client requires OpenSSL version 1.0.2. For Windows platforms, you can use either the regular or the OpenSSL "Light" version.
 
diff --git a/docs/geode-native-docs/introduction/client-intro.html.md.erb b/docs/geode-native-docs/introduction/client-intro.html.md.erb
index f926896..bacfdde 100644
--- a/docs/geode-native-docs/introduction/client-intro.html.md.erb
+++ b/docs/geode-native-docs/introduction/client-intro.html.md.erb
@@ -21,7 +21,7 @@ limitations under the License.
 
 This section shows you how to build the product and run the quick start examples.
 
-The Geode client provides access for C++ and Microsoft<sup>®</sup> .NET™ clients to a Geode distributed system.
+The <%=vars.product_name%> client provides access for C++ and Microsoft<sup>®</sup> .NET™ clients to a <%=vars.product_name%> distributed system.
 
 -   **[System Configurations](client-configurations.html)**
 
diff --git a/docs/geode-native-docs/introduction/client-overview.html.md.erb b/docs/geode-native-docs/introduction/client-overview.html.md.erb
index 0090cd2..505badf 100644
--- a/docs/geode-native-docs/introduction/client-overview.html.md.erb
+++ b/docs/geode-native-docs/introduction/client-overview.html.md.erb
@@ -19,9 +19,9 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-The Geode client delivers the full set of capabilities supplied by Java clients communicating with a Geode server.
+The <%=vars.product_name%> client delivers the full set of capabilities supplied by Java clients communicating with a <%=vars.product_name%> server.
 
-The Geode client is written entirely in C++, so its initialization process does not involve the creation of a Java virtual machine. The .NET client provides operations for the .NET Framework application developer who writes in .NET languages and needs to access the Geode server.
+The <%=vars.product_name%> client is written entirely in C++, so its initialization process does not involve the creation of a Java virtual machine. The .NET client provides operations for the .NET Framework application developer who writes in .NET languages and needs to access the <%=vars.product_name%> server.
 
 Clients in C++, Java, and .NET languages communicate only with the cache server and do not communicate with each other. The clients interface with the server at the sockets level and implement the same wire protocol to the server. These capabilities produce extremely high performance and system scalability.
 
diff --git a/docs/geode-native-docs/introduction/developing-linux.html.md.erb b/docs/geode-native-docs/introduction/developing-linux.html.md.erb
index aad075e..15ed702 100644
--- a/docs/geode-native-docs/introduction/developing-linux.html.md.erb
+++ b/docs/geode-native-docs/introduction/developing-linux.html.md.erb
@@ -21,7 +21,7 @@ limitations under the License.
 
 This section describes how to build and run a client application on Linux.
 
-**Note:** When compiling external projects or applications that are used or referenced by the Geode client, make sure that you compile them for the same target architecture as your client installation. For example, if you installed the 64-bit (x86) version of the client, compile your external projects for 64-bit (x86) architecture.
+**Note:** When compiling external projects or applications that are used or referenced by the <%=vars.product_name%> client, make sure that you compile them for the same target architecture as your client installation. For example, if you installed the 64-bit (x86) version of the client, compile your external projects for 64-bit (x86) architecture.
 
 ## <a id="developing-linux__section_4AD6E18611AE42E9942C77DF91347768" class="no-quick-link"></a>Step 1. Set Environment Variables
 
@@ -35,9 +35,9 @@ PATH=$GEODE/bin:$PATH;export PATH<br />
 LD\_LIBRARY\_PATH=$GEODE/lib:$LD\_LIBRARY\_PATH;export LD\_LIBRARY\_PATH
 </code>
 
-## <a id="developing-linux__section_EFE9D42B05B44F2F958054224BCC5F76" class="no-quick-link"></a>Step 2. Compile C++ Clients and Dynamically Link Them to the Geode Library
+## <a id="developing-linux__section_EFE9D42B05B44F2F958054224BCC5F76" class="no-quick-link"></a>Step 2. Compile C++ Clients and Dynamically Link Them to the <%=vars.product_name%> Library
 
-On Linux, the `g++` compiler is supported. To build and link a C++ client to Geode on Linux, the compilation command line must include the arguments listed in the following table.
+On Linux, the `g++` compiler is supported. To build and link a C++ client to <%=vars.product_name%> on Linux, the compilation command line must include the arguments listed in the following table.
 
 <a id="developing-linux__compiler-arguments-linux"></a>
 
@@ -48,7 +48,7 @@ On Linux, the `g++` compiler is supported. To build and link a C++ client to Geo
 | `-I$GEODE/include` | Specifies the client `include` directory.         |
 
 
-The following table lists the linker switches that must be present on the command line when dynamically linking to the Geode library.
+The following table lists the linker switches that must be present on the command line when dynamically linking to the <%=vars.product_name%> library.
 
 <a id="developing-linux__table_216E9E87FBB44E39BE26388317F3ACE4"></a>
 
@@ -100,4 +100,4 @@ cpp/plugins/DurableCacheListener.cpp \
 
 When the C++ application is dynamically linked to the client library, the library must be dynamically loadable.
 
-To ensure that the client library is available for loading, make sure you have added the path *product-dir*`/lib` to the LD\_LIBRARY\_PATH environment variable, where *product-dir* is the path to the Geode product directory.
+To ensure that the client library is available for loading, make sure you have added the path *product-dir*`/lib` to the LD\_LIBRARY\_PATH environment variable, where *product-dir* is the path to the <%=vars.product_name%> product directory.
diff --git a/docs/geode-native-docs/introduction/developing-solaris.html.md.erb b/docs/geode-native-docs/introduction/developing-solaris.html.md.erb
index e4da54f..bb753c3 100644
--- a/docs/geode-native-docs/introduction/developing-solaris.html.md.erb
+++ b/docs/geode-native-docs/introduction/developing-solaris.html.md.erb
@@ -50,7 +50,7 @@ To build and link a C++ client on Solaris, the compilation command line must inc
 | `-xarch=v9`                                                                                    | Enables 64-bit compilation.                                |
 | `-ldl`; `-lpthread`; `-lc`; `-lm`; `-lsocket`; `-lrt`; `-lnsl`; `-ldemangle`; `-lkstat`; `-lz` | Additional libraries.                                      |
 | `-library=stlport4`                                                                            | Solaris library compilation.                               |
-| `-I$ GEODE /include`                                                                           | Specifies the Geode include directory.                   |
+| `-I$ GEODE /include`                                                                           | Specifies the <%=vars.product_name%> include directory.                   |
 
 
 
@@ -58,4 +58,4 @@ To build and link a C++ client on Solaris, the compilation command line must inc
 
 When a C++ application is not statically linked to the client library, the library must be dynamically loadable.
 
-To verify that the client library is available for loading, make sure you have added the path *product-dir*`/lib` to the LD\_LIBRARY\_PATH environment variable, where *product-dir* is the path to the Geode product directory.
+To verify that the client library is available for loading, make sure you have added the path *product-dir*`/lib` to the LD\_LIBRARY\_PATH environment variable, where *product-dir* is the path to the <%=vars.product_name%> product directory.
diff --git a/docs/geode-native-docs/introduction/developing-windows.html.md.erb b/docs/geode-native-docs/introduction/developing-windows.html.md.erb
index 5dc4820..c8d2639 100644
--- a/docs/geode-native-docs/introduction/developing-windows.html.md.erb
+++ b/docs/geode-native-docs/introduction/developing-windows.html.md.erb
@@ -19,9 +19,9 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-Geode uses the Visual Studio 2010 Service Pack 1 compiler for C++ programs on Windows, which invokes Microsoft<sup>®</sup> `cl.exe` from the command line at compile time.
+<%=vars.product_name%> uses the Visual Studio 2010 Service Pack 1 compiler for C++ programs on Windows, which invokes Microsoft<sup>®</sup> `cl.exe` from the command line at compile time.
 
-The Geode client supports .NET 4.0 and Visual Studio 2010. For advantages and more information on the features of .NET 4.0 and Visual Studio 2010 SP1, see [http://msdn.microsoft.com/en-us/library/dd831853(v=vs.100).aspx](http://msdn.microsoft.com/en-us/library/dd831853(v=vs.100).aspx) and [http://msdn.microsoft.com/en-us/library/vstudio/w0x726c2(v=vs.100).aspx](http://msdn.microsoft.com/en-us/library/vstudio/w0x726c2(v=vs.100).aspx).
+The <%=vars.product_name%> client supports .NET 4.0 and Visual Studio 2010. For advantages and more information on the features of .NET 4.0 and Visual Studio 2010 SP1, see [http://msdn.microsoft.com/en-us/library/dd831853(v=vs.100).aspx](http://msdn.microsoft.com/en-us/library/dd831853(v=vs.100).aspx) and [http://msdn.microsoft.com/en-us/library/vstudio/w0x726c2(v=vs.100).aspx](http://msdn.microsoft.com/en-us/library/vstudio/w0x726c2(v=vs.100).aspx).
 
 Visual Studio 2010 SP1 is the recommended compiler. If you are using any other compiler, contact technical support for assistance.
 
@@ -60,7 +60,7 @@ If you want to use the Visual Studio user interface instead of invoking `cl.exe`
 | `/MD`                             | Memory model.                                                                                                         |
 | `/EHsc`                           | Catches C++ exceptions only and tells the compiler to assume that \*extern\* C functions never throw a C++ exception. |
 | `/GR`                             | Runtime type information.                                                                                             |
-| `-I%GEODE%\include`               | Specifies the Geode `include` directory.                                                 |
+| `-I%GEODE%\include`               | Specifies the <%=vars.product_name%> `include` directory.                                                 |
 | `%GEODE%\lib\gfcppcache.lib`      | Specifies the library file for the shared library.                                                                    |
 | `/D_CRT_SECURE_NO_DEPRECATE`      | Suppresses warnings. Required for Visual Studio 2010.                                                                 |
 | `/D_CRT_NON_CONFORMING_SWPRINTFS` | Suppresses warnings. Required for Visual Studio 2010.                                                                 |
@@ -68,6 +68,6 @@ If you want to use the Visual Studio user interface instead of invoking `cl.exe`
 
 ## <a id="developing-windows__section_B66588EC7C6F4D9BA772406CFD5F3EAE" class="no-quick-link"></a>Step 4. Verify that You Can Load the Client Library
 
-Because Geode does not provide a library that can be linked statically into an application on Windows, you must dynamically link to the client library.
+Because <%=vars.product_name%> does not provide a library that can be linked statically into an application on Windows, you must dynamically link to the client library.
 
-To make the client library available for loading, verify that the directory <code>_product-dir_/bin</code> is included in the PATH environment variable, where *product-dir* is the path to the Geode product directory.
+To make the client library available for loading, verify that the directory <code>_product-dir_/bin</code> is included in the PATH environment variable, where *product-dir* is the path to the <%=vars.product_name%> product directory.
diff --git a/docs/geode-native-docs/introduction/install-overview.html.md.erb b/docs/geode-native-docs/introduction/install-overview.html.md.erb
index 58bda3e..4044fc5 100644
--- a/docs/geode-native-docs/introduction/install-overview.html.md.erb
+++ b/docs/geode-native-docs/introduction/install-overview.html.md.erb
@@ -19,7 +19,7 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-To install the Geode Client, you build the client libraries from a source distribution.
+To install the <%=vars.product_name%> Client, you build the client libraries from a source distribution.
 To build the client libraries:
 
   1. Download the source distribution.
@@ -28,7 +28,7 @@ To build the client libraries:
 
 # Download the Source Distribution
 
-Download Geode Client sources from the [Releases page of the Apache Geode
+Download <%=vars.product_name%> Client sources from the [Releases page of the <%=vars.product_name_long%>
 website](http://geode.apache.org/releases/) and unpack the archive in a location of your choice.
 For example, if your downloaded archive is named `apache-geode-src-1.1.0.tar.gz` and your target
 directory is represented by _geode-client-installdir_:
@@ -49,10 +49,10 @@ information and `README.md` for general information.
 
 # Prerequisites
 
-In order to build the Geode Client libraries, your system must provide certain prerequisites:
+In order to build the <%=vars.product_name%> Client libraries, your system must provide certain prerequisites:
 
   - Compatible operating system
-  - Apache Geode
+  - <%=vars.product_name_long%>
   - CMake
   - C++11 compiler
   - Doxygen
@@ -62,7 +62,7 @@ See the following sections for details.
 
 ## Operating Systems
 
-The following operating systems are known to be compatible with the Apache Geode Client. 
+The following operating systems are known to be compatible with the <%=vars.product_name_long%> Client. 
 The list is not exhaustive, others may also work.
 
 | Operating System | Version |
@@ -77,18 +77,18 @@ The list is not exhaustive, others may also work.
 |                  | Solaris 11 x86 |
 
 
-## Geode
+## <%=vars.product_name%>
 
-Building the client libraries requires access to an installation of Geode. Geode libraries are referenced during the
-client build process, and the Geode executables are needed if you wish to run examples and tests. 
+Building the client libraries requires access to an installation of <%=vars.product_name%>. <%=vars.product_name%> libraries are referenced during the
+client build process, and the <%=vars.product_name%> executables are needed if you wish to run examples and tests. 
 
-If the `GEODE` environment variable is defined, CMake uses it to determine the location of your Geode installation.
-Otherwise, CMake searches some system-specific default locations. To explicitly specify the location in which Geode
+If the `GEODE` environment variable is defined, CMake uses it to determine the location of your <%=vars.product_name%> installation.
+Otherwise, CMake searches some system-specific default locations. To explicitly specify the location in which <%=vars.product_name%>
 is installed, define `GEODE_ROOT=/path/to/geode` in your initial `cmake` configuration command.
 
 ## CMake
 
-CMake version 3.4 or newer is required to build the Geode client and its QuickStart examples. To download and install
+CMake version 3.4 or newer is required to build the <%=vars.product_name%> client and its QuickStart examples. To download and install
 CMake, follow the instructions on [cmake.org] (https://cmake.org).
 
 CMake uses a "generator" to produce configuration files for use by a variety of build tools, such as
@@ -156,12 +156,12 @@ You may find some optional tools to be helpful in certain environments. Here are
 
 # Build and Install
 
-The Geode source distribution comes with CMake files for building and installing the client libraries.
+The <%=vars.product_name%> source distribution comes with CMake files for building and installing the client libraries.
 
 CMake uses a default system-specific location as the destination of the `install` target, for
 example, `/usr/local` on Unix systems. (On Unix systems, you may need to execute your `cmake`
 commands using `sudo` to allow CMake to write output files to protected locations, such as
-`/usr/local`.) To explicitly specify the location in which the Geode Client will be installed,
+`/usr/local`.) To explicitly specify the location in which the <%=vars.product_name%> Client will be installed,
 define `CMAKE_INSTALL_PREFIX=/install-destination` in the initial `cmake` configuration command.
 
 **Note:** For consistent results, avoid using the "~" (tilde) abbreviation when specifying paths on the CMake command line.
@@ -185,7 +185,7 @@ To build and install the client libraries:
     $ cmake ../src
     ```
 
-    In this example, the command includes a pointer to Geode and an installation destination:
+    In this example, the command includes a pointer to <%=vars.product_name%> and an installation destination:
 
     
     ```
diff --git a/docs/geode-native-docs/introduction/quickstart.html.md.erb b/docs/geode-native-docs/introduction/quickstart.html.md.erb
index 62e015d..b89eaab 100644
--- a/docs/geode-native-docs/introduction/quickstart.html.md.erb
+++ b/docs/geode-native-docs/introduction/quickstart.html.md.erb
@@ -44,13 +44,13 @@ The following components must be in place to run the QuickStart examples on any
 
 **For all systems:**
 
-- **Geode**: Install and configure Geode. See the Geode User's Guide for instructions.
+- **<%=vars.product_name%>**: Install and configure <%=vars.product_name%>. See the <%=vars.product_name%> User's Guide for instructions.
 
 - **Cmake** is required to build the quickstart examples. If you have not already done so, download and install cmake, following the instructions on [cmake.org] (https://cmake.org).
 
 - **Java**: You must have a compatible JRE or JDK installed. See the [Sun Java website](http://java.sun.com)
 for the latest Java version for your operating system. See the installation information in the
-Geode User's Guide for the versions of Java that are compatible with Geode. 
+<%=vars.product_name%> User's Guide for the versions of Java that are compatible with <%=vars.product_name%>. 
 
 - **Security Toolkit** (optional): The QuickStart security examples rely on a security plugin, `securityImpl`, which is based on the OpenSSL toolkit.
 
@@ -58,8 +58,8 @@ Geode User's Guide for the versions of Java that are compatible with Geode.
 
 Follow these steps to prepare your Linux or Solaris environment to run the QuickStart examples.
 
-1. Start a terminal session. Set the `GEODE_ROOT` environment variable to point to your Geode product
-installation directory. Add the Geode libraries shown here to your `CLASSPATH`:
+1. Start a terminal session. Set the `GEODE_ROOT` environment variable to point to your <%=vars.product_name%> product
+installation directory. Add the <%=vars.product_name%> libraries shown here to your `CLASSPATH`:
 
     <code>
     % GEODE\_ROOT=_geode-install-dir_; export GEODE\_ROOT <br />
@@ -143,8 +143,8 @@ See <a href="#AboutQSE">About the QuickStart Examples</a> for instructions on ru
 Follow these steps to prepare your Windows environment to run the QuickStart examples.
 
 1. Run the Visual Studio Command Prompt to create a session with preset compiler environment
-configurations. Set the `GEODE_ROOT` environment variable to your Geode installation directory. 
-Add the `%GEODE_ROOT%\bin` directory to your `PATH`. Add the Geode libraries shown here to your `CLASSPATH`:
+configurations. Set the `GEODE_ROOT` environment variable to your <%=vars.product_name%> installation directory. 
+Add the `%GEODE_ROOT%\bin` directory to your `PATH`. Add the <%=vars.product_name%> libraries shown here to your `CLASSPATH`:
 
     <code>
     \>&nbsp;GEODE\_ROOT=_geode-install-dir_<br />
@@ -235,11 +235,11 @@ The examples are briefly described in this section. Each example performs the fo
 
 1. Starts the cache server with the example's server XML.
 
-2. Creates a Geode cache.
+2. Creates a <%=vars.product_name%> cache.
 
 3. Performs operations specific to the example.
 
-4. Closes the Geode cache.
+4. Closes the <%=vars.product_name%> cache.
 
 5. Shuts down the cache server.
 
@@ -334,7 +334,7 @@ The HA Cache example uses client and server XMLs configured to provide high avai
  
 ## Exceptions
 
-The Exceptions example performs some operations in incorrect ways, then logs the exceptions thrown by Geode to demonstrate error handling.
+The Exceptions example performs some operations in incorrect ways, then logs the exceptions thrown by <%=vars.product_name%> to demonstrate error handling.
 
  
 ## Durable Client
@@ -414,7 +414,7 @@ The Transactions example shows the use of the client-server transactions API.
  
 ## PdxRemoteQuery
 
-The PdxRemoteQuery example shows the use of PDX serialized objects with Geode querying.
+The PdxRemoteQuery example shows the use of PDX serialized objects with <%=vars.product_name%> querying.
 
  
 ## PdxSerializer
@@ -456,7 +456,7 @@ Start the C++ menu.
 
 ``` pre
 > runcpp
-Please select a Geode C++ QuickStart example to run.
+Please select a <%=vars.product_name%> C++ QuickStart example to run.
 
 1. BasicOperations
 2. DataExpiration
@@ -477,7 +477,7 @@ Start the C++ menu.
 
 ``` pre
 $ ./runcpp.sh
-Please select a Geode C++ QuickStart example to run.
+Please select a <%=vars.product_name%> C++ QuickStart example to run.
 
 1. BasicOperations
 2. DataExpiration
@@ -498,7 +498,7 @@ Start the C# menu.
 
 ``` pre
 > runcs
-Please select a Geode C# QuickStart example to run.
+Please select a <%=vars.product_name%> C# QuickStart example to run.
 
 1. BasicOperations
 2. DataExpiration
@@ -521,7 +521,7 @@ This section discusses problems you might encounter when you run the examples, a
  
 ## Error Messages
 
-`Exception ... Region:put not connected to Geode`
+`Exception ... Region:put not connected to <%=vars.product_name%>`
 
 Verify that the cache server has successfully started by reviewing the cacheserver.log file in the gfecs directory. The log may indicate why the cache server failed to start.
 
@@ -542,7 +542,7 @@ script so the example can find its XML files.
  
 ## Connection Problems
 
-Geode is a network-centric distributed system, so if you have a firewall running it could cause
+<%=vars.product_name%> is a network-centric distributed system, so if you have a firewall running it could cause
 connection problems. For example, your connections may fail if your firewall places restrictions on
 inbound or outbound permissions for sockets. You may need to modify your firewall configuration to
 permit traffic to applications running on your machine. The specific configuration depends on the
@@ -551,7 +551,7 @@ firewall you're using.
 If you experience port conflicts with other distributed systems, change the `localhost` and
 `bridge-server` port numbers for each of the XML files in the `quickstart/XMLs` directory. If you need
 to specify a non-default multicast port setting for the Java cache server, place a copy of the
-Geode `geode.properties` file in the `quickstart/gfecs` directory, then change the `mcast-port=`
+<%=vars.product_name%> `geode.properties` file in the `quickstart/gfecs` directory, then change the `mcast-port=`
 setting to a unique value for your network.
 
 
diff --git a/docs/geode-native-docs/introduction/running-client-apps.html.md.erb b/docs/geode-native-docs/introduction/running-client-apps.html.md.erb
index 64c8e0b..b671eb9 100644
--- a/docs/geode-native-docs/introduction/running-client-apps.html.md.erb
+++ b/docs/geode-native-docs/introduction/running-client-apps.html.md.erb
@@ -19,7 +19,7 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-Set up the environment for the Geode client on multiple platforms. Compile and run client programs.
+Set up the environment for the <%=vars.product_name%> client on multiple platforms. Compile and run client programs.
 
 -   **[Developing C++ Programs on Linux](developing-linux.html)**
 
@@ -31,6 +31,6 @@ Set up the environment for the Geode client on multiple platforms. Compile and r
 
 -   **[Developing C++ Programs on Windows](developing-windows.html)**
 
-    Geode uses the Visual Studio 2010 Service Pack 1 compiler for C++ programs on Windows, which invokes Microsoft<sup>®</sup> `cl.exe` from the command line at compile time.
+    <%=vars.product_name%> uses the Visual Studio 2010 Service Pack 1 compiler for C++ programs on Windows, which invokes Microsoft<sup>®</sup> `cl.exe` from the command line at compile time.
 
 
diff --git a/docs/geode-native-docs/preserving-data/configuring-durable-nc.html.md.erb b/docs/geode-native-docs/preserving-data/configuring-durable-nc.html.md.erb
index 1000583..d60d2b5 100644
--- a/docs/geode-native-docs/preserving-data/configuring-durable-nc.html.md.erb
+++ b/docs/geode-native-docs/preserving-data/configuring-durable-nc.html.md.erb
@@ -27,7 +27,7 @@ The durable client can be configured in the `geode.properties` file, or in the `
 
 The `durable-timeout` setting is a tuning parameter. When setting the timeout, take into account the normal activity of your application, the average size of your messages, and the level of risk you can handle. Assuming that no messages are being removed from the queue, how long can the application run before the queue reaches the maximum message count? In addition, how long can it run before the queued messages consume all the memory on the client host? How serious is each of those fail [...]
 
-To assist with tuning, Geode statistics track message queues for durable clients through the disconnect and reconnect cycles.
+To assist with tuning, <%=vars.product_name%> statistics track message queues for durable clients through the disconnect and reconnect cycles.
 
 When the queue is full, it blocks further operations that add messages until the queue size drops to an acceptable level. Server configuration sets the action to take. See details on server configuration of the queue in the server documentation section [Implementing Durable Client/Server Messaging](geodeman/developing/events/implementing_durable_client_server_messaging.html).
 
diff --git a/docs/geode-native-docs/preserving-data/impl-cache-listeners-durable-clients.html.md.erb b/docs/geode-native-docs/preserving-data/impl-cache-listeners-durable-clients.html.md.erb
index d50da1c..ae3b520 100644
--- a/docs/geode-native-docs/preserving-data/impl-cache-listeners-durable-clients.html.md.erb
+++ b/docs/geode-native-docs/preserving-data/impl-cache-listeners-durable-clients.html.md.erb
@@ -27,7 +27,7 @@ For general instructions on implementing a cache listener, see [CacheListener](.
 
 Durable clients require special attention to cache callbacks generated by the cache listener. During the initialization window when a reconnecting client has a functioning cache but is still receiving the stored messages from the queue, the client can replay events that are long past. These events are not applied to the cache, but they are sent to the cache listener. If the listener’s callbacks invoked by these events make changes to the cache, that could conflict with current operations [...]
 
-Consequently, you need to keep your callback implementations lightweight and not do anything in the cache that could produce incorrect results during this window. For details on implementing callbacks for Geode event handlers, see [Implementing Cache Event Handlers](geodeman/developing/events/implementing_cache_event_handlers.html).
+Consequently, you need to keep your callback implementations lightweight and not do anything in the cache that could produce incorrect results during this window. For details on implementing callbacks for <%=vars.product_name%> event handlers, see [Implementing Cache Event Handlers](geodeman/developing/events/implementing_cache_event_handlers.html).
 
 ## <a id="concept_3BD651087FC4470C8BAB6AFD97AEA689__section_F39E695D88E94D518F3E1778F37FAF11" class="no-quick-link"></a>Implementing the afterRegionLive Method
 
diff --git a/docs/geode-native-docs/preserving-data/reconnection.html.md.erb b/docs/geode-native-docs/preserving-data/reconnection.html.md.erb
index efa2b4d..193e41f 100644
--- a/docs/geode-native-docs/preserving-data/reconnection.html.md.erb
+++ b/docs/geode-native-docs/preserving-data/reconnection.html.md.erb
@@ -27,7 +27,7 @@ During initialization, operations on the client cache can come from multiple sou
 
 These procedures can act on the cache concurrently, and the cache is never blocked from doing operations.
 
-Geode handles the conflicts between the application and interest registration, but you need to prevent the callback problem. Writing callback methods that do cache operations is never recommended, but it is a particularly bad idea for durable clients, as explained in [Implementing Cache Listeners for Durable Clients](impl-cache-listeners-durable-clients.html).
+<%=vars.product_name%> handles the conflicts between the application and interest registration, but you need to prevent the callback problem. Writing callback methods that do cache operations is never recommended, but it is a particularly bad idea for durable clients, as explained in [Implementing Cache Listeners for Durable Clients](impl-cache-listeners-durable-clients.html).
 
 Program the durable client to perform these steps, in order, when it reconnects:
 
diff --git a/docs/geode-native-docs/remote-querying/91-quickintro/1-quickintro-overview.html.md.erb b/docs/geode-native-docs/remote-querying/91-quickintro/1-quickintro-overview.html.md.erb
index a9c8ac7..5a19423 100644
--- a/docs/geode-native-docs/remote-querying/91-quickintro/1-quickintro-overview.html.md.erb
+++ b/docs/geode-native-docs/remote-querying/91-quickintro/1-quickintro-overview.html.md.erb
@@ -27,6 +27,6 @@ The query language for the native client is essentially a subset of OQL (ODMG 3.
 
 This section assumes that you have general familiarity with SQL querying and indexing, and with the information on the client cache.
 
-Query language features and grammar are described in the Geode manual at [Querying](geodeman/developing/querying_basics/chapter_overview.html). This section describes areas that are unique to the native client.
+Query language features and grammar are described in the <%=vars.product_name%> manual at [Querying](geodeman/developing/querying_basics/chapter_overview.html). This section describes areas that are unique to the native client.
 
 If you are using the pool API, you should obtain the QueryService from the pool. For information about the pool API, see [Client Pool API](../../connection-pools/client-pool-api.html#native-client-pool-api).
diff --git a/docs/geode-native-docs/remote-querying/91-quickintro/4-quickintro-exampleportfolioregion.html.md.erb b/docs/geode-native-docs/remote-querying/91-quickintro/4-quickintro-exampleportfolioregion.html.md.erb
index a0ce9f6..85fee97 100644
--- a/docs/geode-native-docs/remote-querying/91-quickintro/4-quickintro-exampleportfolioregion.html.md.erb
+++ b/docs/geode-native-docs/remote-querying/91-quickintro/4-quickintro-exampleportfolioregion.html.md.erb
@@ -21,7 +21,7 @@ limitations under the License.
 
 This extended example is used throughout the section to show C++ and corresponding Java class definitions and sample data for the example `portfolios` region. The region's keys are the portfolio ID.
 
-User-defined data types must implement the `Serializable` interface on the client side, while corresponding Java classes must implement the `DataSerializable` interface. The C++ objects for the client must correspond to the Java objects for the Geode cache server. This means that an object on one side should deserialize correctly at the other side.
+User-defined data types must implement the `Serializable` interface on the client side, while corresponding Java classes must implement the `DataSerializable` interface. The C++ objects for the client must correspond to the Java objects for the <%=vars.product_name%> cache server. This means that an object on one side should deserialize correctly at the other side.
 
 **Sample C++ class definition**
 
diff --git a/docs/geode-native-docs/security/LDAPserverauth.html.md.erb b/docs/geode-native-docs/security/LDAPserverauth.html.md.erb
index 08e91a7..4f31ef3 100644
--- a/docs/geode-native-docs/security/LDAPserverauth.html.md.erb
+++ b/docs/geode-native-docs/security/LDAPserverauth.html.md.erb
@@ -19,7 +19,7 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-An LDAP server can be used by a Geode cache server using the sample LDAP implementation provided in the server distribution.
+An LDAP server can be used by a <%=vars.product_name%> cache server using the sample LDAP implementation provided in the server distribution.
 
 See [Security](geodeman/managing/security/chapter_overview.html#security) in the server manual to verify authentication credentials for clients attempting to connect to the cache servers and sending user name and passwords using the sample UserPassword scheme.
 
diff --git a/docs/geode-native-docs/security/PKCS.html.md.erb b/docs/geode-native-docs/security/PKCS.html.md.erb
index d414e76..ae4be30 100644
--- a/docs/geode-native-docs/security/PKCS.html.md.erb
+++ b/docs/geode-native-docs/security/PKCS.html.md.erb
@@ -24,9 +24,9 @@ This section discusses the concepts and configurations for the sample UserPasswo
 **Note:**
 Native client samples are provided in source form only in the "templates" directory within the product directory.
 
-With PKCS, clients send encrypted authentication credentials in the form of standard PKCS signatures to a Geode cache server when they connect to the server. The credentials consist of the alias name and digital signature created using the private key that is retrieved from the provided keystore. The server uses a corresponding public key to decrypt the credentials. If decryption is successful then the client is authenticated and it connects to the cache server. For unsuccessful decrypti [...]
+With PKCS, clients send encrypted authentication credentials in the form of standard PKCS signatures to a <%=vars.product_name%> cache server when they connect to the server. The credentials consist of the alias name and digital signature created using the private key that is retrieved from the provided keystore. The server uses a corresponding public key to decrypt the credentials. If decryption is successful then the client is authenticated and it connects to the cache server. For unsu [...]
 
-When clients require authentication to connect to a cache server, they use the `PKCSAuthInit` class implementing the `AuthInitialize` interface to obtain their credentials. For the PKCS sample provided by Geode, the credentials consist of an alias and an encrypted byte array. The private key is obtained from the PKCS\#12 keystore file. To accomplish this,` PKCSAuthInit` gets the alias retrieved from the `security-alias `property, and the keystore path from the `security-keystorepath` pro [...]
+When clients require authentication to connect to a cache server, they use the `PKCSAuthInit` class implementing the `AuthInitialize` interface to obtain their credentials. For the PKCS sample provided by <%=vars.product_name%>, the credentials consist of an alias and an encrypted byte array. The private key is obtained from the PKCS\#12 keystore file. To accomplish this,` PKCSAuthInit` gets the alias retrieved from the `security-alias `property, and the keystore path from the `security- [...]
 
 **The securityImpl Library**
 
diff --git a/docs/geode-native-docs/security/authentication-levels.html.md.erb b/docs/geode-native-docs/security/authentication-levels.html.md.erb
index 69e8eb2..2bd39fd 100644
--- a/docs/geode-native-docs/security/authentication-levels.html.md.erb
+++ b/docs/geode-native-docs/security/authentication-levels.html.md.erb
@@ -27,7 +27,7 @@ Client connections can be authenticated at two levels, process and multiuser.
 
 -   **Multi-user**. Each user/pool pair creates a connection to one server and then sticks with it for operations. If the server is unable to respond to a request, the pool selects a new one for the user.
 
-    Typically, application servers or web servers that act as clients to Geode servers make multi-user connections. Multi-user allows a single application or web server process to service a large number of users with varied access permissions.
+    Typically, application servers or web servers that act as clients to <%=vars.product_name%> servers make multi-user connections. Multi-user allows a single application or web server process to service a large number of users with varied access permissions.
 
 By default, server pools use process-level authentication. Enable multi-user authentication by setting a pool's `multi-user-secure-mode-enabled` attribute to `true`.
 
diff --git a/docs/geode-native-docs/security/createsecureconnregionservice.html.md.erb b/docs/geode-native-docs/security/createsecureconnregionservice.html.md.erb
index 5fd0f9a..563dcd4 100644
--- a/docs/geode-native-docs/security/createsecureconnregionservice.html.md.erb
+++ b/docs/geode-native-docs/security/createsecureconnregionservice.html.md.erb
@@ -21,7 +21,7 @@ limitations under the License.
 
 To create multiple, secure connections to your servers from a single client, so the client can service different user types, you create an authenticated `RegionService` for each user.
 
-Typically, a Geode client embedded in an application server supports data requests from many users. Each user can be authorized to access a subset of data on the servers. For example, customer users are allowed to see and update only their own orders and shipments.
+Typically, a <%=vars.product_name%> client embedded in an application server supports data requests from many users. Each user can be authorized to access a subset of data on the servers. For example, customer users are allowed to see and update only their own orders and shipments.
 
 The authenticated users all access the same Cache through instances of the `RegionService` interface. See [RegionService](../client-cache/caching-apis.html#caching-apis__section_8F81996678B64BBE94EF352527F7F006).
 
diff --git a/docs/geode-native-docs/security/overviewauthentication.html.md.erb b/docs/geode-native-docs/security/overviewauthentication.html.md.erb
index c1e7b3b..5eeb84f 100644
--- a/docs/geode-native-docs/security/overviewauthentication.html.md.erb
+++ b/docs/geode-native-docs/security/overviewauthentication.html.md.erb
@@ -19,7 +19,7 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-A client is authenticated when it connects, with valid credentials, to a Geode cache server that is configured with the client `Authenticator` callback.
+A client is authenticated when it connects, with valid credentials, to a <%=vars.product_name%> cache server that is configured with the client `Authenticator` callback.
 
 Once the client is authenticated, the server assigns the client a unique ID and principal, used to authorize operations. The client must trust all cache servers in the server system as it may connect to any one of them. For information on configuring client/server , see [Client/Server Configuration](geodeman/topologies_and_comm/cs_configuration/chapter_overview.html).
 
@@ -43,4 +43,4 @@ Once the client is authenticated, the server assigns the client a unique ID and
 
 -   **[Using an LDAP Server for Client Authentication](LDAPserverauth.html)**
 
-    An LDAP server can be used by a Geode cache server using the sample LDAP implementation provided in Geode server product.
+    An LDAP server can be used by a <%=vars.product_name%> cache server using the sample LDAP implementation provided in <%=vars.product_name%> server product.
diff --git a/docs/geode-native-docs/security/overviewsecurity.html.md.erb b/docs/geode-native-docs/security/overviewsecurity.html.md.erb
index 038ee35..f0e1729 100644
--- a/docs/geode-native-docs/security/overviewsecurity.html.md.erb
+++ b/docs/geode-native-docs/security/overviewsecurity.html.md.erb
@@ -19,13 +19,13 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-*Security* describes how to implement the security framework for the Geode native client, including authentication, authorization, encryption, and SSL client/server communication.
+*Security* describes how to implement the security framework for the <%=vars.product_name%> native client, including authentication, authorization, encryption, and SSL client/server communication.
 
-The security framework authenticates clients that attempt to connect to a Geode cache server and authorizes client cache operations. You can also configure it for client authentication of servers, and you can plug in your own implementations for authentication and authorization.
+The security framework authenticates clients that attempt to connect to a <%=vars.product_name%> cache server and authorizes client cache operations. You can also configure it for client authentication of servers, and you can plug in your own implementations for authentication and authorization.
 
 -   **[Authentication](overviewauthentication.html)**
 
-    A client is authenticated when it connects, with valid credentials, to a Geode cache server that is configured with the client `Authenticator` callback.
+    A client is authenticated when it connects, with valid credentials, to a <%=vars.product_name%> cache server that is configured with the client `Authenticator` callback.
 
 -   **[Encrypted Authentication](encrypted-auth.html)**
 
diff --git a/docs/geode-native-docs/security/security-systemprops.html.md.erb b/docs/geode-native-docs/security/security-systemprops.html.md.erb
index d219395..492aebb 100644
--- a/docs/geode-native-docs/security/security-systemprops.html.md.erb
+++ b/docs/geode-native-docs/security/security-systemprops.html.md.erb
@@ -44,7 +44,7 @@ The table describes the security-related system properties in the `gemfire.prope
 </tr>
 <tr class="even">
 <td><code class="ph codeph">security-client-kspath</code></td>
-<td>Path to a .pem file, which contains the public certificates for all Geode cache servers to which the client can connect through specified endpoints.</td>
+<td>Path to a .pem file, which contains the public certificates for all <%=vars.product_name%> cache servers to which the client can connect through specified endpoints.</td>
 </tr>
 <tr class="odd">
 <td><code class="ph codeph">security-client-kspasswd</code></td>
diff --git a/docs/geode-native-docs/security/sslclientserver.html.md.erb b/docs/geode-native-docs/security/sslclientserver.html.md.erb
index a091a4f..ac9e48f 100644
--- a/docs/geode-native-docs/security/sslclientserver.html.md.erb
+++ b/docs/geode-native-docs/security/sslclientserver.html.md.erb
@@ -34,7 +34,7 @@ OpenSSL as described in the following section.
 
 ## Step 1. Create keystores
 
-The Geode server requires keys and keystores in the Java Key Store (JKS) format while the native client requires them in the clear PEM format. Thus you need to be able to generate private/public keypairs in either format and convert between the two using the `keytool` utility and the `openssl` command.
+The <%=vars.product_name%> server requires keys and keystores in the Java Key Store (JKS) format while the native client requires them in the clear PEM format. Thus you need to be able to generate private/public keypairs in either format and convert between the two using the `keytool` utility and the `openssl` command.
 
 There are public third party free tools and source code available to download such as the "KeyTool IUI" tool.
 
diff --git a/docs/geode-native-docs/setting-properties/propfile-sample.html.md.erb b/docs/geode-native-docs/setting-properties/propfile-sample.html.md.erb
index 9e39420..eefebea 100644
--- a/docs/geode-native-docs/setting-properties/propfile-sample.html.md.erb
+++ b/docs/geode-native-docs/setting-properties/propfile-sample.html.md.erb
@@ -19,7 +19,7 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-A sample `geode.properties` file is included with the Apache Geode native client installation in the <code>_product-dir_/defaultSystem</code> directory.
+A sample `geode.properties` file is included with the <%=vars.product_name_long%> native client installation in the <code>_product-dir_/defaultSystem</code> directory.
 
 To use this file:
 
diff --git a/docs/geode-native-docs/sqlite-persistence/windows-install.html.md.erb b/docs/geode-native-docs/sqlite-persistence/windows-install.html.md.erb
index 02b86ff..e44b89c 100644
--- a/docs/geode-native-docs/sqlite-persistence/windows-install.html.md.erb
+++ b/docs/geode-native-docs/sqlite-persistence/windows-install.html.md.erb
@@ -26,7 +26,7 @@ The library has been tested with SQLite v3.7.14.1.
 The *`product-dir`* directory refers to the path to the directory
 that contains the built library.
 
-The following libraries are required. The <code><i>product-dir</i>/bin</code> directory containing these libraries must be present in the Windows `PATH` environment variable, and that directory is added to `PATH` during the Geode product installation.
+The following libraries are required. The <code><i>product-dir</i>/bin</code> directory containing these libraries must be present in the Windows `PATH` environment variable, and that directory is added to `PATH` during the <%=vars.product_name%> product installation.
 
 -   The `sqliteimpl.dll` and `Apache.Geode.Plugins.SQLite.dll` files are provided in <code><i>product-dir</i>/bin</code>.
 -   For .NET C\# native client application development, you need to obtain the `System.Data.SQLite.dll` SQLite library, as described below. The library can be copied to <code><i>product-dir</i>/bin</code>.
diff --git a/docs/geode-native-docs/transactions/running-client-xact.html.md.erb b/docs/geode-native-docs/transactions/running-client-xact.html.md.erb
index 62759d8..c542da7 100644
--- a/docs/geode-native-docs/transactions/running-client-xact.html.md.erb
+++ b/docs/geode-native-docs/transactions/running-client-xact.html.md.erb
@@ -83,7 +83,7 @@ Before you can run a transaction, you must configure your clients and servers, d
 
 When you commit a transaction, while the commit is taking place, the changes are visible in the cache. This is also known as transition commits. This provides better performance than locking everything to do the transaction updates, but it means that another process accessing data used in the transaction might get some data in the pre-transaction state and some in the post-transaction state.
 
-For example, keys 1 and 2 are written to in a transaction so both of their values change from A to B. In another thread, it is possible to read key 1 with value B and key 2 with value A, while the transaction is being committed. This can happen because of how Geode performs reads. This choice sacrifices atomic visibility in favor of performance. Reads do not block writes. Writes do not block reads.
+For example, keys 1 and 2 are written to in a transaction so both of their values change from A to B. In another thread, it is possible to read key 1 with value B and key 2 with value A, while the transaction is being committed. This can happen because of how <%=vars.product_name%> performs reads. This choice sacrifices atomic visibility in favor of performance. Reads do not block writes. Writes do not block reads.
 
 Because the client cache waits during transaction execution, and client regions are not distributed, the only activities that interact with a client transaction are those that occur on the server.
 
diff --git a/docs/geode-native-docs/transactions/suspend-resume-xacts.html.md.erb b/docs/geode-native-docs/transactions/suspend-resume-xacts.html.md.erb
index e8f280b..3c7d821 100644
--- a/docs/geode-native-docs/transactions/suspend-resume-xacts.html.md.erb
+++ b/docs/geode-native-docs/transactions/suspend-resume-xacts.html.md.erb
@@ -27,7 +27,7 @@ When a transaction is resumed, the resuming thread assumes the transactional vie
 
 If the member with the primary copy of the data crashes, the transactional view that applied to that data is lost. The secondary member for the data cannot resume transactions suspended on the crashed member. You need to take remedial steps to retry the transaction on a new primary copy of the data.
 
-If a suspended transaction is not touched for a period of time, Geode cleans it up automatically. By default, the timeout for a suspended transaction is 30 minutes and can be configured by using the `suspended-tx-timeout` property of the `geode.properties` file. The suspended transaction timeout value is specified in milliseconds.
+If a suspended transaction is not touched for a period of time, <%=vars.product_name%> cleans it up automatically. By default, the timeout for a suspended transaction is 30 minutes and can be configured by using the `suspended-tx-timeout` property of the `geode.properties` file. The suspended transaction timeout value is specified in milliseconds.
 
 See [Running a Client Transaction](running-client-xact.html) for code examples that show a how to suspend and resume a transaction.
 

-- 
To stop receiving notification emails like this one, please contact
['"commits@geode.apache.org" <commits@geode.apache.org>'].

Mime
View raw message