geode-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kl...@apache.org
Subject [19/51] [abbrv] geode git commit: GEODE-3395 Variable-ize product version and name in user guide - Tools & Modules
Date Sat, 19 Aug 2017 00:10:14 GMT
GEODE-3395 Variable-ize product version and name in user guide - Tools & Modules


Project: http://git-wip-us.apache.org/repos/asf/geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/geode/commit/bb988caa
Tree: http://git-wip-us.apache.org/repos/asf/geode/tree/bb988caa
Diff: http://git-wip-us.apache.org/repos/asf/geode/diff/bb988caa

Branch: refs/heads/feature/GEODE-1279
Commit: bb988caa5969d35948fd603f73bb1a32e879ef78
Parents: c5dd26b
Author: Dave Barnes <dbarnes@pivotal.io>
Authored: Tue Aug 15 14:26:11 2017 -0700
Committer: Dave Barnes <dbarnes@pivotal.io>
Committed: Tue Aug 15 16:27:12 2017 -0700

----------------------------------------------------------------------
 geode-docs/tools_modules/book_intro.html.md.erb | 18 +++----
 .../gemcached/about_gemcached.html.md.erb       |  6 +--
 .../gemcached/advantages.html.md.erb            | 14 +++---
 .../gemcached/chapter_overview.html.md.erb      |  4 +-
 .../gemcached/deploying_gemcached.html.md.erb   |  4 +-
 .../tools_modules/gfsh/about_gfsh.html.md.erb   | 12 ++---
 .../gfsh/cache_xml_2_gfsh.html.md.erb           |  2 +-
 .../gfsh/chapter_overview.html.md.erb           |  8 ++--
 .../gfsh/command-pages/alter.html.md.erb        |  4 +-
 .../gfsh/command-pages/change.html.md.erb       |  2 +-
 .../gfsh/command-pages/configure.html.md.erb    |  2 +-
 .../gfsh/command-pages/create.html.md.erb       | 26 +++++-----
 .../gfsh/command-pages/export.html.md.erb       |  4 +-
 .../gfsh/command-pages/list.html.md.erb         | 14 +++---
 .../gfsh/command-pages/query.html.md.erb        |  2 +-
 .../gfsh/command-pages/show.html.md.erb         |  4 +-
 .../gfsh/command-pages/start.html.md.erb        | 50 ++++++++++----------
 .../gfsh/command-pages/status.html.md.erb       |  8 ++--
 .../gfsh/command-pages/stop.html.md.erb         | 10 ++--
 .../gfsh/configuring_gfsh.html.md.erb           |  8 ++--
 .../gfsh/getting_started_gfsh.html.md.erb       |  2 +-
 .../gfsh/gfsh_command_index.html.md.erb         |  8 ++--
 .../gfsh/gfsh_quick_reference.html.md.erb       |  4 +-
 .../gfsh/quick_ref_commands_by_area.html.md.erb | 32 ++++++-------
 .../gfsh/starting_gfsh.html.md.erb              | 10 ++--
 .../tools_modules/gfsh/tour_of_gfsh.html.md.erb | 14 +++---
 .../useful_gfsh_shell_variables.html.md.erb     |  2 +-
 .../chapter_overview.html.md.erb                | 10 ++--
 .../common_gemfire_topologies.html.md.erb       |  2 +-
 .../http_why_use_gemfire.html.md.erb            | 16 +++----
 .../interactive_mode_ref.html.md.erb            | 38 +++++++--------
 .../http_session_mgmt/quick_start.html.md.erb   |  8 ++--
 .../session_mgmt_tcserver.html.md.erb           |  4 +-
 .../session_mgmt_tomcat.html.md.erb             |  6 +--
 .../session_mgmt_weblogic.html.md.erb           |  6 +--
 .../session_state_log_files.html.md.erb         | 20 ++++----
 .../tc_additional_info.html.md.erb              | 14 +++---
 .../tc_changing_gf_default_cfg.html.md.erb      | 16 +++----
 .../tc_installing_the_module.html.md.erb        |  2 +-
 .../tc_setting_up_the_module.html.md.erb        |  8 ++--
 .../tomcat_changing_gf_default_cfg.html.md.erb  | 38 +++++++--------
 .../tomcat_installing_the_module.html.md.erb    |  2 +-
 .../tomcat_setting_up_the_module.html.md.erb    | 18 +++----
 ...weblogic_changing_gf_default_cfg.html.md.erb | 48 +++++++++----------
 ...gic_common_configuration_changes.html.md.erb |  4 +-
 .../weblogic_setting_up_the_module.html.md.erb  | 20 ++++----
 .../lucene_integration.html.md.erb              |  4 +-
 .../tools_modules/pulse/pulse-auth.html.md.erb  |  4 +-
 .../pulse/pulse-embedded.html.md.erb            | 12 ++---
 .../pulse/pulse-hosted.html.md.erb              | 14 +++---
 .../pulse/pulse-overview.html.md.erb            | 16 +++----
 .../tools_modules/pulse/pulse-views.html.md.erb | 40 ++++++++--------
 .../tools_modules/redis_adapter.html.md.erb     | 34 ++++++-------
 53 files changed, 332 insertions(+), 346 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/book_intro.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/book_intro.html.md.erb b/geode-docs/tools_modules/book_intro.html.md.erb
index 2bf0930..c86f925 100644
--- a/geode-docs/tools_modules/book_intro.html.md.erb
+++ b/geode-docs/tools_modules/book_intro.html.md.erb
@@ -19,32 +19,32 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-*Tools and Modules* describes tools and modules associated with Apache Geode.
+*Tools and Modules* describes tools and modules associated with <%=vars.product_name_long%>.
 
 <a id="deploy_run__section_tool_intro"></a>
 
 -   **[gfsh](gfsh/chapter_overview.html)**
 
-    `gfsh` (pronounced "jee-fish") provides a single, powerful command-line interface from which you can launch, manage, and monitor Geode processes, data, and applications.
+    `gfsh` (pronounced "jee-fish") provides a single, powerful command-line interface from which you can launch, manage, and monitor <%=vars.product_name%> processes, data, and applications.
 
 -   **[Gemcached](gemcached/chapter_overview.html)**
 
-    Gemcached is a Geode adapter that allows Memcached clients to communicate with a Geode server cluster, as if the servers were memcached servers. Memcached is an open-source caching solution that uses a distributed, in-memory hash map to store key-value pairs of string or object data.
+    Gemcached is a <%=vars.product_name%> adapter that allows Memcached clients to communicate with a <%=vars.product_name%> server cluster, as if the servers were memcached servers. Memcached is an open-source caching solution that uses a distributed, in-memory hash map to store key-value pairs of string or object data.
 
 -   **[HTTP Session Management Modules](http_session_mgmt/chapter_overview.html)**
 
-    The Apache Geode HTTP Session Management modules provide fast, scalable, and reliable session replication for HTTP servers without requiring application changes.
+    The <%=vars.product_name_long%> HTTP Session Management modules provide fast, scalable, and reliable session replication for HTTP servers without requiring application changes.
 
--   **[Geode Pulse](pulse/pulse-overview.html)**
+-   **[<%=vars.product_name%> Pulse](pulse/pulse-overview.html)**
 
-    Geode Pulse is a Web Application that provides a graphical dashboard for monitoring vital, real-time health and performance of Geode clusters, members, and regions.
+    <%=vars.product_name%> Pulse is a Web Application that provides a graphical dashboard for monitoring vital, real-time health and performance of <%=vars.product_name%> clusters, members, and regions.
 
--   **[Geode Redis Adapter](redis_adapter.html)**
+-   **[<%=vars.product_name%> Redis Adapter](redis_adapter.html)**
 
-    The Geode Redis adapter allows Geode to function as a drop-in replacement for a Redis data store, letting Redis applications take advantage of Geode’s scaling capabilities without changing their client code. Redis clients connect to a Geode server in the same way they connect to a Redis server, using an IP address and a port number.
+    The <%=vars.product_name%> Redis adapter allows <%=vars.product_name%> to function as a drop-in replacement for a Redis data store, letting Redis applications take advantage of <%=vars.product_name%>’s scaling capabilities without changing their client code. Redis clients connect to a <%=vars.product_name%> server in the same way they connect to a Redis server, using an IP address and a port number.
 
 
 -   **[Apache Lucene&reg; Integration](lucene_integration.html)**
 
-    The Apache Lucene&reg; integration enables users to create Lucene indexes and execute Lucene searches on data stored in Geode.
+    The Apache Lucene&reg; integration enables users to create Lucene indexes and execute Lucene searches on data stored in <%=vars.product_name%>.
 

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gemcached/about_gemcached.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gemcached/about_gemcached.html.md.erb b/geode-docs/tools_modules/gemcached/about_gemcached.html.md.erb
index 3bf9a9e..4083d0a 100644
--- a/geode-docs/tools_modules/gemcached/about_gemcached.html.md.erb
+++ b/geode-docs/tools_modules/gemcached/about_gemcached.html.md.erb
@@ -23,7 +23,7 @@ Applications use memcached clients to access data stored in embedded Gemcached s
 
 Applications can use memcached clients that are written in Python, C\#, Ruby, PHP, and other programming languages. Each memcached server in a cluster stores data as key/value pairs. A memcached client maintains a list of these servers, determines which server has the required data, and accesses the data directly on that server.
 
-To integrate memcached with Apache Geode, you embed a Gemcached server within a Geode cache server. These *Gemcached* servers take the place of memcached servers. The memcached client uses its normal wire protocol to communicate with the Gemcached servers, which appear to the client as memcached servers. No code changes in the clients are needed. Geode manages the distribution and access to data among the embedded Gemcached servers.
+To integrate memcached with <%=vars.product_name_long%>, you embed a Gemcached server within a <%=vars.product_name%> cache server. These *Gemcached* servers take the place of memcached servers. The memcached client uses its normal wire protocol to communicate with the Gemcached servers, which appear to the client as memcached servers. No code changes in the clients are needed. <%=vars.product_name%> manages the distribution and access to data among the embedded Gemcached servers.
 
 As shown in [Gemcached Architecture](about_gemcached.html#concept_4C654CA7F6B34E4CA1B0318BC9644536__fig_8BF351B5FAF1490F8B0D0E7F3098BC73), memcached clients, which ordinarily maintain a list of memcached servers, now maintain a list of embedded Gemcached servers. If more embedded Gemcached servers are added to the cluster, the new servers automatically become part of the cluster. The memcached clients can continue to communicate with the servers on the list, without having to update their list of servers.
 
@@ -32,11 +32,11 @@ As shown in [Gemcached Architecture](about_gemcached.html#concept_4C654CA7F6B34E
 
 <img src="../../images/Gemcached.png" id="concept_4C654CA7F6B34E4CA1B0318BC9644536__image_98B6222F29B940CD93381D03325C4455" class="image" />
 
-Memcached clients use the memcached API to read and write data that is stored in memcached servers; therefore, client-side Geode features are not available to these clients. Gemcached servers, however, can use Geode's server-side features and API. These features include the following. (For more detail, see [Advantages of Gemcached over Memcached](advantages.html#topic_849581E507544E63AF23793FBC47D778).)
+Memcached clients use the memcached API to read and write data that is stored in memcached servers; therefore, client-side <%=vars.product_name%> features are not available to these clients. Gemcached servers, however, can use <%=vars.product_name%>'s server-side features and API. These features include the following. (For more detail, see [Advantages of Gemcached over Memcached](advantages.html#topic_849581E507544E63AF23793FBC47D778).)
 
 -   Data consistency and scalability.
 -   High availability.
--   Read-through, write through, and write behind to a database, implemented from within the distributed Geode cache.
+-   Read-through, write through, and write behind to a database, implemented from within the distributed <%=vars.product_name%> cache.
 -   Storage keys and values of any type and size.
 -   For applications, a choice among partitioned and replicated region configurations.
 -   Automatic overflow of data to disk in low-memory scenarios.

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gemcached/advantages.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gemcached/advantages.html.md.erb b/geode-docs/tools_modules/gemcached/advantages.html.md.erb
index 6fbe8fb..96f9e30 100644
--- a/geode-docs/tools_modules/gemcached/advantages.html.md.erb
+++ b/geode-docs/tools_modules/gemcached/advantages.html.md.erb
@@ -19,18 +19,18 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-The standard memcached architecture has inherent architectural challenges that make memcached applications difficult to write, maintain, and scale. Using Gemcached with Geode addresses these challenges.
+The standard memcached architecture has inherent architectural challenges that make memcached applications difficult to write, maintain, and scale. Using Gemcached with <%=vars.product_name%> addresses these challenges.
 
-**Data consistency**. Memcached clients must maintain a list of servers where the distributed data is stored. Each client must maintain an identical list, with each list ordered in the same way. It is the responsibility of the application logic to maintain and propagate this list. If some clients do not have the correct list, the client can retrieve stale data. In Geode clusters, all members communicate with each other to maintain data consistency, which eliminates the need to code these behaviors in the memcached clients.
+**Data consistency**. Memcached clients must maintain a list of servers where the distributed data is stored. Each client must maintain an identical list, with each list ordered in the same way. It is the responsibility of the application logic to maintain and propagate this list. If some clients do not have the correct list, the client can retrieve stale data. In <%=vars.product_name%> clusters, all members communicate with each other to maintain data consistency, which eliminates the need to code these behaviors in the memcached clients.
 
-**High availability**. When a memcached server becomes unavailable, memcached clusters are subject to failures or degraded performance because clients must directly query the backend database. Memcached-based applications must be coded to handle these failures, while Geode clusters handle such failures natively.
+**High availability**. When a memcached server becomes unavailable, memcached clusters are subject to failures or degraded performance because clients must directly query the backend database. Memcached-based applications must be coded to handle these failures, while <%=vars.product_name%> clusters handle such failures natively.
 
-**Faster cluster startup time**. When a memcached cluster fails and a restart is required, the data must be reloaded and distributed to the cluster members while simultaneously processing requests for data. These startup activities can be time-consuming. When a Geode cluster restarts, data can be reloaded from other in-memory, redundant copies of the data or from disk, without having to query the back end database.
+**Faster cluster startup time**. When a memcached cluster fails and a restart is required, the data must be reloaded and distributed to the cluster members while simultaneously processing requests for data. These startup activities can be time-consuming. When a <%=vars.product_name%> cluster restarts, data can be reloaded from other in-memory, redundant copies of the data or from disk, without having to query the back end database.
 
-**Better handling of network segmentation**. Large deployments of memcached can use hundreds of servers to manage data. If, due to network segmentation, some clients cannot connect to all nodes of a partition, the clients will have to fetch the data from the backend database to avoid hosting stale data. Geode clusters handle network segmentation to ensure that client responses are consistent.
+**Better handling of network segmentation**. Large deployments of memcached can use hundreds of servers to manage data. If, due to network segmentation, some clients cannot connect to all nodes of a partition, the clients will have to fetch the data from the backend database to avoid hosting stale data. <%=vars.product_name%> clusters handle network segmentation to ensure that client responses are consistent.
 
-**Automatic scalability**. If you need to add capacity to a memcached cluster, you must propagate a new server list to all clients. As new clients come on line with the new list, older clients may not have a consistent view of the data in the cluster, which can result in inconsistent data in the servers. Because new Geode cache server members automatically discover each other, memcached clients do not need to maintain a complete server list. You can add capacity simply by adding servers.
+**Automatic scalability**. If you need to add capacity to a memcached cluster, you must propagate a new server list to all clients. As new clients come on line with the new list, older clients may not have a consistent view of the data in the cluster, which can result in inconsistent data in the servers. Because new <%=vars.product_name%> cache server members automatically discover each other, memcached clients do not need to maintain a complete server list. You can add capacity simply by adding servers.
 
-**Scalable client connections**. A memcached client may need to access multiple pieces of data stored on multiple servers, which can result in clients having a TCP connection open to every server. When a memcached client accesses a Gemcached server, only a single connection to a Gemcached server instance is required. The Gemcached server manages the distribution of data using Geode's standard features.
+**Scalable client connections**. A memcached client may need to access multiple pieces of data stored on multiple servers, which can result in clients having a TCP connection open to every server. When a memcached client accesses a Gemcached server, only a single connection to a Gemcached server instance is required. The Gemcached server manages the distribution of data using <%=vars.product_name%>'s standard features.
 
 

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gemcached/chapter_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gemcached/chapter_overview.html.md.erb b/geode-docs/tools_modules/gemcached/chapter_overview.html.md.erb
index 5fef3e3..8e029ff 100644
--- a/geode-docs/tools_modules/gemcached/chapter_overview.html.md.erb
+++ b/geode-docs/tools_modules/gemcached/chapter_overview.html.md.erb
@@ -21,7 +21,7 @@ limitations under the License.
 <a id="topic_3751C8A924884B7F88F993CAD350D4FE"></a>
 
 
-Gemcached is a Geode adapter that allows Memcached clients to communicate with a Geode server cluster, as if the servers were memcached servers. Memcached is an open-source caching solution that uses a distributed, in-memory hash map to store key-value pairs of string or object data.
+Gemcached is a <%=vars.product_name%> adapter that allows Memcached clients to communicate with a <%=vars.product_name%> server cluster, as if the servers were memcached servers. Memcached is an open-source caching solution that uses a distributed, in-memory hash map to store key-value pairs of string or object data.
 
 For information about Memcached, see [http://www.memcached.org](http://www.memcached.org).
 
@@ -35,6 +35,6 @@ For information about Memcached, see [http://www.memcached.org](http://www.memca
 
 -   **[Advantages of Gemcached over Memcached](advantages.html)**
 
-    The standard memcached architecture has inherent architectural challenges that make memcached applications difficult to write, maintain, and scale. Using Gemcached with Geode addresses these challenges.
+    The standard memcached architecture has inherent architectural challenges that make memcached applications difficult to write, maintain, and scale. Using Gemcached with <%=vars.product_name%> addresses these challenges.
 
 

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gemcached/deploying_gemcached.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gemcached/deploying_gemcached.html.md.erb b/geode-docs/tools_modules/gemcached/deploying_gemcached.html.md.erb
index 2c4724e..68801eb 100644
--- a/geode-docs/tools_modules/gemcached/deploying_gemcached.html.md.erb
+++ b/geode-docs/tools_modules/gemcached/deploying_gemcached.html.md.erb
@@ -23,9 +23,9 @@ You can configure and deploy Gemcached servers in a Java class or by using the g
 
 The following sections describe how to configure and deploy an embedded Gemcached server. You can configure and start a GemCached server either by invoking a Java class that calls the cache server's `start()` method, or by starting the cache server using the gfsh command line.
 
-## <a id="topic_7B158074B27A4FEF9D38E7C369905C72__section_17E7E4058D914334B9C5AC2E3DC1F7F2" class="no-quick-link"></a>Embedding a Gemcached server in a Geode Java Application
+## <a id="topic_7B158074B27A4FEF9D38E7C369905C72__section_17E7E4058D914334B9C5AC2E3DC1F7F2" class="no-quick-link"></a>Embedding a Gemcached server in a <%=vars.product_name%> Java Application
 
-The `org.apache.geode.memcached` package contains a single class, `GemFireMemcachedServer`. (See the [Geode Javadocs](http://static.springsource.org/spring-gemfire/docs/current/api/).) Use this class to configure and embed a Gemcached server in a Geode cache server. For example, the following statement creates and starts an embedded Gemcached server on port number 5555 using the binary protocol:
+The `org.apache.geode.memcached` package contains a single class, `GemFireMemcachedServer` (see the <%=vars.product_name%> Javadocs.) Use this class to configure and embed a Gemcached server in a <%=vars.product_name%> cache server. For example, the following statement creates and starts an embedded Gemcached server on port number 5555 using the binary protocol:
 
 ``` pre
 GemFireMemcachedServer server = 

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gfsh/about_gfsh.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gfsh/about_gfsh.html.md.erb b/geode-docs/tools_modules/gfsh/about_gfsh.html.md.erb
index b440bfa..1f54575 100644
--- a/geode-docs/tools_modules/gfsh/about_gfsh.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/about_gfsh.html.md.erb
@@ -19,24 +19,24 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-`gfsh` supports the administration, debugging, and deployment of Apache Geode processes and applications.
+`gfsh` supports the administration, debugging, and deployment of <%=vars.product_name_long%> processes and applications.
 
 With `gfsh`, you can:
 
--   Start and stop Apache Geode processes, such as locators and cache servers
+-   Start and stop <%=vars.product_name_long%> processes, such as locators and cache servers
 -   Start and stop gateway sender and gateway receiver processes
 -   Deploy applications
 -   Create and destroy regions
 -   Execute functions
 -   Manage disk stores
 -   Import and export data
--   Monitor Apache Geode processes
--   Launch Apache Geode monitoring tools
+-   Monitor <%=vars.product_name_long%> processes
+-   Launch <%=vars.product_name_long%> monitoring tools
 
-The `gfsh` command line interface lets developers spend less time configuring cache instance XML, properties, logs, and statistics. gfsh commands generate reports; capture cluster-wide statistics; and support the export of statistics, logs, and configurations. Like Spring Roo, gfsh features command completion (so you do not have to know the syntax), context-sensitive help, scripting, and the ability to invoke any commands from within an application by using a simple API. The gfsh interface uses JMX/RMI to communicate with Apache Geode processes.
+The `gfsh` command line interface lets developers spend less time configuring cache instance XML, properties, logs, and statistics. gfsh commands generate reports; capture cluster-wide statistics; and support the export of statistics, logs, and configurations. Like Spring Roo, gfsh features command completion (so you do not have to know the syntax), context-sensitive help, scripting, and the ability to invoke any commands from within an application by using a simple API. The gfsh interface uses JMX/RMI to communicate with <%=vars.product_name_long%> processes.
 
 You can connect gfsh to a remote distributed system using the HTTP protocol. See [Using gfsh to Manage a Remote Cluster Over HTTP or HTTPS](../../configuring/cluster_config/gfsh_remote.html).
 
-By default, the cluster configuration service saves the configuration of your Apache Geode cluster as you create Apache Geode objects using gfsh. You can export this configuration and import it into another Apache Geode cluster. See [Overview of the Cluster Configuration Service](../../configuring/cluster_config/gfsh_persist.html#concept_r22_hyw_bl).
+By default, the cluster configuration service saves the configuration of your <%=vars.product_name_long%> cluster as you create <%=vars.product_name_long%> objects using gfsh. You can export this configuration and import it into another <%=vars.product_name_long%> cluster. See [Overview of the Cluster Configuration Service](../../configuring/cluster_config/gfsh_persist.html#concept_r22_hyw_bl).
 
 

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gfsh/cache_xml_2_gfsh.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gfsh/cache_xml_2_gfsh.html.md.erb b/geode-docs/tools_modules/gfsh/cache_xml_2_gfsh.html.md.erb
index e4bab4e..c845823 100644
--- a/geode-docs/tools_modules/gfsh/cache_xml_2_gfsh.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/cache_xml_2_gfsh.html.md.erb
@@ -19,7 +19,7 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-You can configure a Geode cluster using either cache.xml files,
+You can configure a <%=vars.product_name%> cluster using either cache.xml files,
 or you can use gfsh and the cluster configuration service
 to configure a cluster.
 This table maps `cache.xml` elements to the gfsh commands that

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gfsh/chapter_overview.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gfsh/chapter_overview.html.md.erb b/geode-docs/tools_modules/gfsh/chapter_overview.html.md.erb
index 2cb90b5..318dc99 100644
--- a/geode-docs/tools_modules/gfsh/chapter_overview.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/chapter_overview.html.md.erb
@@ -19,11 +19,11 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-`gfsh` (pronounced "jee-fish") provides a single, powerful command-line interface from which you can launch, manage, and monitor Geode processes, data, and applications.
+`gfsh` (pronounced "jee-fish") provides a single, powerful command-line interface from which you can launch, manage, and monitor <%=vars.product_name%> processes, data, and applications.
 
 -   **[What You Can Do with gfsh](about_gfsh.html)**
 
-    `gfsh` supports the administration, debugging, and deployment of Apache Geode processes and applications.
+    `gfsh` supports the administration, debugging, and deployment of <%=vars.product_name_long%> processes and applications.
 
 -   **[Starting gfsh](starting_gfsh.html)**
 
@@ -31,7 +31,7 @@ limitations under the License.
 
 -   **[Configuring the gfsh Environment](configuring_gfsh.html)**
 
-    The `gfsh.bat` and `gfsh` bash script automatically append the required Apache Geode and JDK .jar libraries to your existing CLASSPATH. There are user-configurable properties you can set for security, environment variables, logging, and troubleshooting.
+    The `gfsh.bat` and `gfsh` bash script automatically append the required <%=vars.product_name_long%> and JDK .jar libraries to your existing CLASSPATH. There are user-configurable properties you can set for security, environment variables, logging, and troubleshooting.
 
 -   **[Useful gfsh Shell Variables](useful_gfsh_shell_variables.html)**
 
@@ -61,6 +61,6 @@ limitations under the License.
 
 -   **[Mapping of cache.xml Elements to gfsh Configuration Commands.](cache_xml_2_gfsh.html)**
 
-    You can configure a Geode cluster using either cache.xml files, or you can use `gfsh` and the cluster configuration service to configure a cluster. This section maps cache.xml elements to the `gfsh` commands that configure and manage a cluster.
+    You can configure a <%=vars.product_name%> cluster using either cache.xml files, or you can use `gfsh` and the cluster configuration service to configure a cluster. This section maps cache.xml elements to the `gfsh` commands that configure and manage a cluster.
 
 

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb
index f28c1ce..cbe44b8 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb
@@ -21,7 +21,7 @@ limitations under the License.
 <a id="topic_9323467A645D4F2B82EC236448030D14"></a>
 
 
-Modify an existing Geode resource.
+Modify an existing <%=vars.product_name%> resource.
 
 -   **[alter disk-store](../../../tools_modules/gfsh/command-pages/alter.html#topic_99BCAD98BDB5470189662D2F308B68EB)**
 
@@ -39,7 +39,7 @@ Modify an existing Geode resource.
 
 Modify or remove a region from an offline disk-store.
 
-When modifying a region's configuration, it is customary to take the region off-line and restart using the new configuration. You can use the `alter                         disk-store` command to change the configuration of the region stored in the disk-store to match the configuration you will use at restart.
+When modifying a region's configuration, it is customary to take the region off-line and restart using the new configuration. You can use the `alter disk-store` command to change the configuration of the region stored in the disk-store to match the configuration you will use at restart.
 
 **Availability:** Offline.
 

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb
index 8ff5e9b..92a8696 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/change.html.md.erb
@@ -49,7 +49,7 @@ change loglevel --loglevel=value [--members=value(nullvalue)*] [--groups=value(n
 <tbody>
 <tr class="odd">
 <td><span class="keyword parmname">\-\-members</span></td>
-<td>Name or ID of one or more Geode distributed system member(s) whose logging level you want to change.</td>
+<td>Name or ID of one or more <%=vars.product_name%> distributed system member(s) whose logging level you want to change.</td>
 <td> </td>
 </tr>
 <tr class="even">

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gfsh/command-pages/configure.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gfsh/command-pages/configure.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/configure.html.md.erb
index c6ce59e..ad4ecae 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/configure.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/configure.html.md.erb
@@ -27,7 +27,7 @@ Configure Portable Data eXchange for all the cache(s) in the cluster.
 ## <a id="topic_jdkdiqbgphqh" class="no-quick-link"></a>configure pdx
 
 <a id="topic_jdkdiqbgphqh__section_C27BE964CE554180A65968DBEBF50B23"></a>
-Configures Geode's Portable Data eXchange for all the cache(s) in the cluster. This command does not effect on the running members in the system. This command persists the pdx configuration in the locator with cluster configuration service.
+Configures <%=vars.product_name%>'s Portable Data eXchange for all the cache(s) in the cluster. This command does not effect on the running members in the system. This command persists the pdx configuration in the locator with cluster configuration service.
 
 **Note:**
 This command should be issued before starting any data members.

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb
index 01efcd8..5d20794 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb
@@ -121,13 +121,13 @@ create async-event-queue --id=value --listener=value [--group=value(nullvalue)*]
 </tr>
 <tr class="odd">
 <td><span class="keyword parmname">\-\-persistent</span></td>
-<td>Boolean value that determines whether Geode persists this queue.</td>
+<td>Boolean value that determines whether <%=vars.product_name%> persists this queue.</td>
 <td>false
 <p>If specified with out a value, default is true.</p></td>
 </tr>
 <tr class="even">
 <td><span class="keyword parmname">\-\-disk-store</span></td>
-<td>Named disk store to use for storing queue overflow, or for persisting the queue. If you specify a value, the named disk store must exist. If you specify a null value, Geode uses the default disk store for overflow and queue persistence.</td>
+<td>Named disk store to use for storing queue overflow, or for persisting the queue. If you specify a value, the named disk store must exist. If you specify a null value, <%=vars.product_name%> uses the default disk store for overflow and queue persistence.</td>
 <td> </td>
 </tr>
 <tr class="odd">
@@ -397,14 +397,14 @@ create gateway-receiver [--group=value(,value)*] [--member=value(,value)*]
 </tr>
 <tr class="even">
 <td><span class="keyword parmname">\-\-start-port</span></td>
-<td><p>Starting port number to use when specifying the range of possible port numbers this gateway receiver will use to connects to gateway senders in other sites. Geode chooses an unused port number in the specified port number range to start the receiver. If no port numbers in the range are available, an exception is thrown.</p>
-<p>The <code class="ph codeph">STARTPORT</code> value is inclusive while the <code class="ph codeph">ENDPORT</code> value is exclusive. For example, if you specify <code class="ph codeph">STARTPORT=&quot;50510&quot;</code> and <code class="ph codeph">ENDPOINT=&quot;50520&quot;</code>, Geode chooses a port value from 50510 to 50519.</p></td>
+<td><p>Starting port number to use when specifying the range of possible port numbers this gateway receiver will use to connects to gateway senders in other sites. <%=vars.product_name%> chooses an unused port number in the specified port number range to start the receiver. If no port numbers in the range are available, an exception is thrown.</p>
+<p>The <code class="ph codeph">STARTPORT</code> value is inclusive while the <code class="ph codeph">ENDPORT</code> value is exclusive. For example, if you specify <code class="ph codeph">STARTPORT=&quot;50510&quot;</code> and <code class="ph codeph">ENDPOINT=&quot;50520&quot;</code>, <%=vars.product_name%> chooses a port value from 50510 to 50519.</p></td>
 <td>5000</td>
 </tr>
 <tr class="odd">
 <td><span class="keyword parmname">\-\-end-port</span></td>
-<td><p>Defines the upper bound port number to use when specifying the range of possible port numbers this gateway receiver will use to for connections from gateway senders in other sites. Geode chooses an unused port number in the specified port number range to start the receiver. If no port numbers in the range are available, an exception is thrown.</p>
-<p>The <code class="ph codeph">ENDPORT</code> value is exclusive while the <code class="ph codeph">STARTPORT</code> value is inclusive. For example, if you specify <code class="ph codeph">STARTPORT=&quot;50510&quot;</code> and <code class="ph codeph">ENDPOINT=&quot;50520&quot;</code>, Geode chooses a port value from 50510 to 50519.</p></td>
+<td><p>Defines the upper bound port number to use when specifying the range of possible port numbers this gateway receiver will use to for connections from gateway senders in other sites. <%=vars.product_name%> chooses an unused port number in the specified port number range to start the receiver. If no port numbers in the range are available, an exception is thrown.</p>
+<p>The <code class="ph codeph">ENDPORT</code> value is exclusive while the <code class="ph codeph">STARTPORT</code> value is inclusive. For example, if you specify <code class="ph codeph">STARTPORT=&quot;50510&quot;</code> and <code class="ph codeph">ENDPOINT=&quot;50520&quot;</code>, <%=vars.product_name%> chooses a port value from 50510 to 50519.</p></td>
 <td>5500</td>
 </tr>
 <tr class="even">
@@ -452,7 +452,7 @@ Creates a gateway sender on one or more members of a distributed system.
 See [Gateway Senders](../../../topologies_and_comm/topology_concepts/multisite_overview.html#topic_9AA37B43642D4DE19072CA3367C849BA).
 
 **Note:**
-The gateway sender configuration for a specific sender `id` must be identical on each Geode member that hosts the gateway sender.
+The gateway sender configuration for a specific sender `id` must be identical on each <%=vars.product_name%> member that hosts the gateway sender.
 
 **Availability:** Online. You must be connected in `gfsh` to a JMX Manager member to use this command.
 
@@ -512,7 +512,7 @@ create gateway-sender --id=value --remote-distributed-system-id=value
 </tr>
 <tr class="even">
 <td><span class="keyword parmname">\-\-enable-batch-conflation</span></td>
-<td>Boolean value that determines whether Geode should conflate messages.</td>
+<td>Boolean value that determines whether <%=vars.product_name%> should conflate messages.</td>
 <td>false</td>
 </tr>
 <tr class="odd">
@@ -542,12 +542,12 @@ create gateway-sender --id=value --remote-distributed-system-id=value
 </tr>
 <tr class="even">
 <td><span class="keyword parmname">\-\-enable-persistence</span></td>
-<td>Boolean value that determines whether Geode persists the gateway queue.</td>
+<td>Boolean value that determines whether <%=vars.product_name%> persists the gateway queue.</td>
 <td>false</td>
 </tr>
 <tr class="odd">
 <td><span class="keyword parmname">\-\-disk-store-name</span></td>
-<td>Named disk store to use for storing the queue overflow, or for persisting the queue. If you specify a value, the named disk store must exist. If you specify a null value, Geode uses the default disk store for overflow and queue persistence.</td>
+<td>Named disk store to use for storing the queue overflow, or for persisting the queue. If you specify a value, the named disk store must exist. If you specify a null value, <%=vars.product_name%> uses the default disk store for overflow and queue persistence.</td>
 <td> </td>
 </tr>
 <tr class="even">
@@ -562,7 +562,7 @@ create gateway-sender --id=value --remote-distributed-system-id=value
 </tr>
 <tr class="even">
 <td><span class="keyword parmname">\-\-alert-threshold</span></td>
-<td>Maximum number of milliseconds that a region event can remain in the gateway sender queue before Geode logs an alert.</td>
+<td>Maximum number of milliseconds that a region event can remain in the gateway sender queue before <%=vars.product_name%> logs an alert.</td>
 <td>0</td>
 </tr>
 <tr class="odd">
@@ -578,7 +578,7 @@ create gateway-sender --id=value --remote-distributed-system-id=value
 <dt><b>thread</b></dt>
 <dd>When distributing region events from the local queue, multiple dispatcher threads preserve the order in which a given thread added region events to the queue.</dd>
 <dt><b>partition</b></dt>
-<dd>When distributing region events from the local queue, multiple dispatcher threads preserve the order in which region events were added to the local queue. For a partitioned region, this means that all region events delivered to a specific partition are delivered in the same order to the remote Geode site. For a distributed region, this means that all key updates delivered to the local gateway sender queue are distributed to the remote site in the same order.</dd>
+<dd>When distributing region events from the local queue, multiple dispatcher threads preserve the order in which region events were added to the local queue. For a partitioned region, this means that all region events delivered to a specific partition are delivered in the same order to the remote <%=vars.product_name%> site. For a distributed region, this means that all key updates delivered to the local gateway sender queue are distributed to the remote site in the same order.</dd>
 
 <p>You cannot configure the <code class="ph codeph">order-policy</code> for a parallel event queue, because parallel queues cannot preserve event ordering for regions. Only the ordering of events for a given partition (or in a given queue of a distributed region) can be preserved.</p></td>
 <td>key</td>
@@ -942,7 +942,7 @@ See [Region Data Storage and Distribution](../../../developing/region_options/ch
 </tr>
 <tr class="even">
 <td><span class="keyword parmname">\-\-compressor</span></td>
-<td>Java class name that implements compression for the region. You can write a custom compressor that implements <code class="ph codeph">org.apache.geode.compression.Compressor</code> or you can specify the Snappy compressor (<code class="ph codeph">org.apache.geode.compression.SnappyCompressor</code>), which is bundled with Geode. See <a href="../../../managing/region_compression/region_compression.html#topic_r43_wgc_gl">Region Compression</a>.</td>
+<td>Java class name that implements compression for the region. You can write a custom compressor that implements <code class="ph codeph">org.apache.geode.compression.Compressor</code> or you can specify the Snappy compressor (<code class="ph codeph">org.apache.geode.compression.SnappyCompressor</code>), which is bundled with <%=vars.product_name%>. See <a href="../../../managing/region_compression/region_compression.html#topic_r43_wgc_gl">Region Compression</a>.</td>
 <td>no compression</td>
 </tr>
 <tr class="odd">

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gfsh/command-pages/export.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gfsh/command-pages/export.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/export.html.md.erb
index e9c79d3..4fe2140 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/export.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/export.html.md.erb
@@ -25,7 +25,7 @@ Export configurations, data, logs and stack-traces.
 
 -   **[export cluster-configuration](#topic_mdv_jgz_ck)**
 
-    Exports a cluster configuration zip file that contains the `cache.xml` files, `gemfire.properties` files, and application jar files needed to configure and operate a Geode distributed system.
+    Exports a cluster configuration zip file that contains the `cache.xml` files, `gemfire.properties` files, and application jar files needed to configure and operate a <%=vars.product_name%> distributed system.
 
 -   **[export config](#topic_C7C69306F93743459E65D46537F4A1EE)**
 
@@ -49,7 +49,7 @@ Export configurations, data, logs and stack-traces.
 
 ## <a id="topic_mdv_jgz_ck" class="no-quick-link"></a>export cluster-configuration
 
-Exports a cluster configuration zip file that contains the `cache.xml` files, `gemfire.properties` files, and application jar files needed to configure and operate a Geode distributed system.
+Exports a cluster configuration zip file that contains the `cache.xml` files, `gemfire.properties` files, and application jar files needed to configure and operate a <%=vars.product_name%> distributed system.
 
 **Availability:** Online. You must be connected in `gfsh` to a JMX Manager member to use this command.
 

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb
index f7601b2..2933973 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/list.html.md.erb
@@ -21,7 +21,7 @@ limitations under the License.
 
 
 
-List existing Geode resources such as deployed applications, disk-stores, functions, members, servers, and regions.
+List existing <%=vars.product_name%> resources such as deployed applications, disk-stores, functions, members, servers, and regions.
 
 -   **[list async-event-queues](#topic_j22_kzk_2l)**
 
@@ -37,7 +37,7 @@ List existing Geode resources such as deployed applications, disk-stores, functi
 
 -   **[list disk-stores](#topic_BC14AD57EA304FB3845766898D01BD04)**
 
-    List all available disk stores across the Geode cluster
+    List all available disk stores across the <%=vars.product_name%> cluster
 
 -   **[list durable-cqs](#topic_66016A698C334F4EBA19B99F51B0204B)**
 
@@ -65,7 +65,7 @@ List existing Geode resources such as deployed applications, disk-stores, functi
 
 -   **[list regions](#topic_F0ECEFF26086474498598035DD83C588)**
 
-    Display regions of a member or members. If no parameter is specified, all regions in the Geode distributed system are listed.
+    Display regions of a member or members. If no parameter is specified, all regions in the <%=vars.product_name%> distributed system are listed.
 
 ## <a id="topic_j22_kzk_2l" class="no-quick-link"></a>list async-event-queues
 
@@ -163,7 +163,7 @@ No JAR Files Found
 
 ## <a id="topic_BC14AD57EA304FB3845766898D01BD04" class="no-quick-link"></a>list disk-stores
 
-List all available disk stores across the Geode cluster
+List all available disk stores across the <%=vars.product_name%> cluster
 
 The command also lists the configured disk directories and any Regions, Cache Servers, Gateways, PDX Serialization and Async Event Queues using Disk Stores to either overflow and/or persist information to disk. Use the `describe                         disk-store` command to see the details for a particular Disk Store.
 
@@ -307,7 +307,7 @@ gfsh> list functions --matches=reconcile.*
   excalibur | reconcileDailyExpenses
 
 
-Example of 'list functions' when no functions are found in Geode :
+Example of 'list functions' when no functions are found in <%=vars.product_name%> :
 
 gfsh> list functions
 No Functions Found.
@@ -389,7 +389,7 @@ ps...        | 192...    | /producers  | pidIdx   | RANGE | id                 |
 
 **Error Messages:**
 
-Example of output when no indexes are found in Geode:
+Example of output when no indexes are found in <%=vars.product_name%>:
 
 ``` pre
 gfsh> list indexes
@@ -479,7 +479,7 @@ locator1 | 192.0.2.0(locator1:216:locator):33368
 
 ## <a id="topic_F0ECEFF26086474498598035DD83C588" class="no-quick-link"></a>list regions
 
-Display regions of a member or members. If no parameter is specified, all regions in the Geode distributed system are listed.
+Display regions of a member or members. If no parameter is specified, all regions in the <%=vars.product_name%> distributed system are listed.
 
 **Syntax:**
 

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gfsh/command-pages/query.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gfsh/command-pages/query.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/query.html.md.erb
index 8df594e..9708e7c 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/query.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/query.html.md.erb
@@ -19,7 +19,7 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-Run queries against Geode regions.
+Run queries against <%=vars.product_name%> regions.
 
 If a limit restricting the result size is not set in the query,
 then a default limit of the gfsh environment variable `APP_FETCH_SIZE`,

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gfsh/command-pages/show.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gfsh/command-pages/show.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/show.html.md.erb
index 881c1c6..1d2a0da 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/show.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/show.html.md.erb
@@ -25,7 +25,7 @@ Display deadlocks, logs, metrics and missing disk-stores.
 
 -   **[show dead-locks](#topic_1125347FAD6541DF995C9999650165B1)**
 
-    Display any deadlocks in the Geode distributed system.
+    Display any deadlocks in the <%=vars.product_name%> distributed system.
 
 -   **[show log](#topic_45AAEDAC3AFF46EC9BB68B24FC9A32B3)**
 
@@ -45,7 +45,7 @@ Display deadlocks, logs, metrics and missing disk-stores.
 
 ## <a id="topic_1125347FAD6541DF995C9999650165B1" class="no-quick-link"></a>show dead-locks
 
-Display any deadlocks in the Geode distributed system.
+Display any deadlocks in the <%=vars.product_name%> distributed system.
 
 **Availability:** Online. You must be connected in `gfsh` to a JMX Manager member to use this command.
 

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb
index 17fefa5..e6a63dc 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb
@@ -45,11 +45,11 @@ Start servers, locators, gateway senders and gateway receivers, and monitoring t
 
 -   **[start pulse](#topic_E906BA7D9E7F4C5890FEFA7ECD40DD77)**
 
-    Launch the Geode Pulse monitoring dashboard tool in the user's default system browser and navigates the user to the landing page (login page).
+    Launch the <%=vars.product_name%> Pulse monitoring dashboard tool in the user's default system browser and navigates the user to the landing page (login page).
 
 -   **[start server](#topic_3764EE2DB18B4AE4A625E0354471738A)**
 
-    Start a Geode cache server process.
+    Start a <%=vars.product_name%> cache server process.
 
 ## <a id="topic_67738A5B68E84DEE95D1C92DAB2E26E5" class="no-quick-link"></a>start gateway-receiver
 
@@ -160,7 +160,7 @@ JConsole automatically connects to a running JMX Manager node if one is availabl
 
 Note that you must have a JDK installed (not just a JRE) and the correct PATH and JAVA\_HOME environment variables set.
 
-See [Browsing Geode MBeans through JConsole](../../../managing/management/mbeans_jconsole.html) for an example of using JConsole with the Geode management and monitoring system.
+See [Browsing <%=vars.product_name%> MBeans through JConsole](../../../managing/management/mbeans_jconsole.html) for an example of using JConsole with the <%=vars.product_name%> management and monitoring system.
 
 **Availability:** Online or offline.
 
@@ -209,7 +209,7 @@ The JConsole application appears and auto-connects to a JMX Manager node if one
 ``` pre
 An error occurred while launching JConsole = %1$s
 
-Connecting by the Geode member's name or ID is not currently supported.
+Connecting by the <%=vars.product_name%> member's name or ID is not currently supported.
 Please specify the member as '<hostname|IP>[PORT].
 
 An IO error occurred while launching JConsole.
@@ -256,7 +256,7 @@ The command creates a subdirectory and log file named after the locator. If the
 
 In addition, if gfsh is not already connected to a JMX Manager, the gfsh console will automatically connect to the new embedded JMX Manager started by the new locator.
 
-**Note:** When both `--max-heap` and `--initial-heap` are specified during locator startup, additional GC parameters are specified internally by Geode's Resource Manager. If you do not want the additional default GC properties set by the Resource Manager, then use the`-Xms` and `-Xmx` JVM options. See [Controlling Heap Use with the Resource Manager](../../../managing/heap_use/heap_management.html#configuring_resource_manager) for more information.
+**Note:** When both `--max-heap` and `--initial-heap` are specified during locator startup, additional GC parameters are specified internally by <%=vars.product_name%>'s Resource Manager. If you do not want the additional default GC properties set by the Resource Manager, then use the`-Xms` and `-Xmx` JVM options. See [Controlling Heap Use with the Resource Manager](../../../managing/heap_use/heap_management.html#configuring_resource_manager) for more information.
 
 **Availability:** Online or offline.
 
@@ -288,7 +288,7 @@ start locator --name=value [--bind-address=value] [--force(=value)] [--group=val
 <tbody>
 <tr class="odd">
 <td><span class="keyword parmname">\-\-name</span></td>
-<td>Name to be used for this Geode locator service. If not specified, gfsh generates a random name.</td>
+<td>Name to be used for this <%=vars.product_name%> locator service. If not specified, gfsh generates a random name.</td>
 <td> </td>
 </tr>
 <tr class="even">
@@ -313,7 +313,7 @@ start locator --name=value [--bind-address=value] [--force(=value)] [--group=val
 </tr>
 <tr class="even">
 <td><span class="keyword parmname">\-\-locators</span></td>
-<td>List of locators used by this locator to join the appropriate Geode cluster.</td>
+<td>List of locators used by this locator to join the appropriate <%=vars.product_name%> cluster.</td>
 <td> </td>
 </tr>
 <tr class="odd">
@@ -323,12 +323,12 @@ start locator --name=value [--bind-address=value] [--force(=value)] [--group=val
 </tr>
 <tr class="even">
 <td><span class="keyword parmname">\-\-mcast-address </span></td>
-<td>IP address or hostname used to bind the UPD socket for multi-cast networking so the locator can locate other members in the Geode cluster. If mcast-port is zero, then mcast-address is ignored.</td>
+<td>IP address or hostname used to bind the UPD socket for multi-cast networking so the locator can locate other members in the <%=vars.product_name%> cluster. If mcast-port is zero, then mcast-address is ignored.</td>
 <td> </td>
 </tr>
 <tr class="odd">
 <td><span class="keyword parmname">\-\-mcast-port</span></td>
-<td>Port used for multi-cast networking so the locator can locate other members of the Geode cluster. A zero value disables mcast.</td>
+<td>Port used for multi-cast networking so the locator can locate other members of the <%=vars.product_name%> cluster. A zero value disables mcast.</td>
 <td> </td>
 </tr>
 <tr class="even">
@@ -355,7 +355,7 @@ start locator --name=value [--bind-address=value] [--force(=value)] [--group=val
 <td><span class="keyword parmname">\-\-initial-heap</span></td>
 <td>Size has the same format as the <code class="ph codeph">-Xmx</code>/<code class="ph codeph">-Xms</code> JVM options.
 <div class="note note">
-<b>Note:</b> If you use the <code class="ph codeph">-J-Xms</code> and <code class="ph codeph">-J-Xmx</code> JVM properties instead of <code class="ph codeph">-initial-heap</code> and <code class="ph codeph">-max-heap</code>, then Geode does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.
+<b>Note:</b> If you use the <code class="ph codeph">-J-Xms</code> and <code class="ph codeph">-J-Xmx</code> JVM properties instead of <code class="ph codeph">-initial-heap</code> and <code class="ph codeph">-max-heap</code>, then <%=vars.product_name%> does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.
 </div></td>
 <td> </td>
 </tr>
@@ -363,7 +363,7 @@ start locator --name=value [--bind-address=value] [--force(=value)] [--group=val
 <td><span class="keyword parmname">\-\-max-heap</span></td>
 <td>Size has the same format as the <code class="ph codeph">-Xmx</code>/<code class="ph codeph">-Xms</code> JVM options
 <div class="note note">
-<b>Note:</b> If you use the <code class="ph codeph">-J-Xms</code> and <code class="ph codeph">-J-Xmx</code> JVM properties instead of <code class="ph codeph">-initial-heap</code> and <code class="ph codeph">-max-heap</code>, then Geode does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.
+<b>Note:</b> If you use the <code class="ph codeph">-J-Xms</code> and <code class="ph codeph">-J-Xmx</code> JVM properties instead of <code class="ph codeph">-initial-heap</code> and <code class="ph codeph">-max-heap</code>, then <%=vars.product_name%> does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.
 </div></td>
 <td> </td>
 </tr>
@@ -423,9 +423,9 @@ start locator --name=locator1
 
 ## <a id="topic_E906BA7D9E7F4C5890FEFA7ECD40DD77" class="no-quick-link"></a>start pulse
 
-Launch the Geode Pulse monitoring dashboard tool in the user's default system browser and navigates the user to the landing page (login page).
+Launch the <%=vars.product_name%> Pulse monitoring dashboard tool in the user's default system browser and navigates the user to the landing page (login page).
 
-For more information on Geode Pulse, see [Geode Pulse](../../pulse/pulse-overview.html).
+For more information on <%=vars.product_name%> Pulse, see [<%=vars.product_name%> Pulse](../../pulse/pulse-overview.html).
 
 **Availability:** Online or offline.
 
@@ -448,13 +448,13 @@ start pulse
 start pulse --url=http://gemfire.example.com:7070/pulse
 ```
 
-**Sample Output:** See [Geode Pulse](../../pulse/pulse-overview.html) for examples of Pulse.
+**Sample Output:** See [<%=vars.product_name%> Pulse](../../pulse/pulse-overview.html) for examples of Pulse.
 
 ## <a id="topic_3764EE2DB18B4AE4A625E0354471738A" class="no-quick-link"></a>start server
 
-Start a Geode cache server process.
+Start a <%=vars.product_name%> cache server process.
 
-**Note:** When both <span class="keyword parmname">\\-\\-max-heap</span> and <span class="keyword parmname">\\-\\-initial-heap</span> are specified during locator startup, additional GC parameters are specified internally by Geode's Resource Manager. If you do not want the additional default GC properties set by the Resource Manager, then use the `-Xms` and `-Xmx` JVM options. See [Controlling Heap Use with the Resource Manager](../../../managing/heap_use/heap_management.html#configuring_resource_manager) for more information.
+**Note:** When both <span class="keyword parmname">\\-\\-max-heap</span> and <span class="keyword parmname">\\-\\-initial-heap</span> are specified during locator startup, additional GC parameters are specified internally by <%=vars.product_name%>'s Resource Manager. If you do not want the additional default GC properties set by the Resource Manager, then use the `-Xms` and `-Xmx` JVM options. See [Controlling Heap Use with the Resource Manager](../../../managing/heap_use/heap_management.html#configuring_resource_manager) for more information.
 
 **Availability:** Online or offline.
 
@@ -500,7 +500,7 @@ start server --name=value [--assign-buckets(=value)] [--bind-address=value]
 <tbody>
 <tr class="odd">
 <td><span class="keyword parmname">\-\-name</span></td>
-<td>Member name for this Geode Cache Server service. If not specified, gfsh generates a random name.</td>
+<td>Member name for this <%=vars.product_name%> Cache Server service. If not specified, gfsh generates a random name.</td>
 <td> </td>
 </tr>
 <tr class="even">
@@ -540,7 +540,7 @@ start server --name=value [--assign-buckets(=value)] [--bind-address=value]
 </tr>
 <tr class="odd">
 <td><span class="keyword parmname">\-\-enable-time-statistics</span></td>
-<td>Causes additional time-based statistics to be gathered for Geode operations.</td>
+<td>Causes additional time-based statistics to be gathered for <%=vars.product_name%> operations.</td>
 <td>true</td>
 </tr>
 <tr class="even">
@@ -565,7 +565,7 @@ start server --name=value [--assign-buckets(=value)] [--bind-address=value]
 </tr>
 <tr class="even">
 <td><span class="keyword parmname">\-\-locators </span></td>
-<td>Sets the list of locators used by the Cache Server to join the appropriate Geode cluster.</td>
+<td>Sets the list of locators used by the Cache Server to join the appropriate <%=vars.product_name%> cluster.</td>
 <td> </td>
 </tr>
 <tr class="odd">
@@ -580,12 +580,12 @@ start server --name=value [--assign-buckets(=value)] [--bind-address=value]
 </tr>
 <tr class="odd">
 <td><span class="keyword parmname">\-\-mcast-address</span></td>
-<td>The IP address or hostname used to bind the UDP socket for multi-cast networking so the Cache Server can locate other members in the Geode cluster. If mcast-port is zero, then mcast-address is ignored.</td>
+<td>The IP address or hostname used to bind the UDP socket for multi-cast networking so the Cache Server can locate other members in the <%=vars.product_name%> cluster. If mcast-port is zero, then mcast-address is ignored.</td>
 <td> </td>
 </tr>
 <tr class="even">
 <td><span class="keyword parmname">\-\-mcast-port</span></td>
-<td>Sets the port used for multi-cast networking so the Cache Server can locate other members of the Geode cluster. A zero value disables mcast.</td>
+<td>Sets the port used for multi-cast networking so the Cache Server can locate other members of the <%=vars.product_name%> cluster. A zero value disables mcast.</td>
 <td> </td>
 </tr>
 <tr class="odd">
@@ -610,13 +610,13 @@ start server --name=value [--assign-buckets(=value)] [--bind-address=value]
 </tr>
 <tr class="odd">
 <td><span class="keyword parmname">\-\-spring-xml-location</span></td>
-<td>Specifies the location of a Spring XML configuration file(s) for bootstrapping and configuring a Geode Server. This configuration file can exist on the CLASSPATH (default) or any location supported by Spring's Resource(Loader) location specifiers (for example, classpath:, file:, etc). ResourceLoader is described in the 
+<td>Specifies the location of a Spring XML configuration file(s) for bootstrapping and configuring a <%=vars.product_name%> Server. This configuration file can exist on the CLASSPATH (default) or any location supported by Spring's Resource(Loader) location specifiers (for example, classpath:, file:, etc). ResourceLoader is described in the 
 <a href="http://docs.spring.io/spring/docs/4.0.9.RELEASE/spring-framework-reference/htmlsingle/#resources-resourceloader">Spring documentation</a>.</td>
 <td> </td>
 </tr>
 <tr class="even">
 <td><span class="keyword parmname">\-\-rebalance</span></td>
-<td>Whether to initiate rebalancing across the Geode cluster.</td>
+<td>Whether to initiate rebalancing across the <%=vars.product_name%> cluster.</td>
 <td>false</td>
 </tr>
 <tr class="odd">
@@ -633,7 +633,7 @@ start server --name=value [--assign-buckets(=value)] [--bind-address=value]
 <td><span class="keyword parmname">\-\-initial-heap</span></td>
 <td>Initial size of the heap in the same format as the JVM -Xms parameter.
 <div class="note note">
-<b>Note:</b> If you use the <code class="ph codeph">--J=-Xms</code> and <code class="ph codeph">--J=-Xmx</code> JVM properties instead of <code class="ph codeph">--initial-heap</code> and <code class="ph codeph">--max-heap</code>, then Geode does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.
+<b>Note:</b> If you use the <code class="ph codeph">--J=-Xms</code> and <code class="ph codeph">--J=-Xmx</code> JVM properties instead of <code class="ph codeph">--initial-heap</code> and <code class="ph codeph">--max-heap</code>, then <%=vars.product_name%> does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.
 </div></td>
 <td> </td>
 </tr>
@@ -641,7 +641,7 @@ start server --name=value [--assign-buckets(=value)] [--bind-address=value]
 <td><span class="keyword parmname">\-\-max-heap</span></td>
 <td>Maximum size of the heap in the same format as the JVM -Xmx parameter.
 <div class="note note">
-<b>Note:</b> If you use the <code class="ph codeph">--J=-Xms</code> and <code class="ph codeph">--J=-Xmx</code> JVM properties instead of <code class="ph codeph">--initial-heap</code> and <code class="ph codeph">--max-heap</code>, then Geode does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.
+<b>Note:</b> If you use the <code class="ph codeph">--J=-Xms</code> and <code class="ph codeph">--J=-Xmx</code> JVM properties instead of <code class="ph codeph">--initial-heap</code> and <code class="ph codeph">--max-heap</code>, then <%=vars.product_name%> does not use default JVM resource management properties. If you use the JVM properties, you must then specify all properties manually for eviction, garbage collection, heap percentage, and so forth.
 </div></td>
 <td> </td>
 </tr>

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gfsh/command-pages/status.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gfsh/command-pages/status.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/status.html.md.erb
index 01e4874..6129069 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/status.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/status.html.md.erb
@@ -21,7 +21,7 @@ limitations under the License.
 <a id="topic_7BCB054803CF48FE8688394C5C39000A"></a>
 
 
-Check the status of the cluster configuration service and Geode member processes, including locators, gateway receivers, gateway senders, and servers.
+Check the status of the cluster configuration service and <%=vars.product_name%> member processes, including locators, gateway receivers, gateway senders, and servers.
 
 -   **[status cluster-config-service](#topic_ts1_qb1_dk2)**
 
@@ -41,7 +41,7 @@ Check the status of the cluster configuration service and Geode member processes
 
 -   **[status server](#topic_E5DB49044978404D9D6B1971BF5D400D)**
 
-    Display the status of the specified Geode cache server.
+    Display the status of the specified <%=vars.product_name%> cache server.
 
 ## <a id="topic_ts1_qb1_dk2" class="no-quick-link"></a>status cluster-config-service
 
@@ -235,7 +235,7 @@ status locator --name=locator1
 
 ## <a id="topic_E5DB49044978404D9D6B1971BF5D400D" class="no-quick-link"></a>status server
 
-Display the status of the specified Geode cache server.
+Display the status of the specified <%=vars.product_name%> cache server.
 
 **Availability:** Online or offline. If you want to obtain the status of a server while you are offline, use the `--dir` option.
 
@@ -250,7 +250,7 @@ status server [--name=value] [--dir=value]
 | Name                                         | Description                                                                                                                                                                                                                                                                                                                                                                                                                           | Default Value     |
 |----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|
 | <span class="keyword parmname">&#8209;&#8209;name</span> | Name or ID of the Cache Server for which to display status. You must be connected to the JMX Manager to use this option. Can be used to obtain status of remote servers. See [Using gfsh to Manage a Remote Cluster Over HTTP or HTTPS](../../../configuring/cluster_config/gfsh_remote.html). |                   |
-| <span class="keyword parmname">\\-\\-dir </span> | Directory in which the Geode Cache Server was started.                                                                                                                                                                                                                                                                                                                                                   | current directory |
+| <span class="keyword parmname">\\-\\-dir </span> | Directory in which the <%=vars.product_name%> Cache Server was started.                                                                                                                                                                                                                                                                                                                                                   | current directory |
 
 <span class="tablecap">Table 4. Status Server Parameters</span>
 

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gfsh/command-pages/stop.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gfsh/command-pages/stop.html.md.erb b/geode-docs/tools_modules/gfsh/command-pages/stop.html.md.erb
index e9d5820..f923dfc 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/stop.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/stop.html.md.erb
@@ -37,7 +37,7 @@ Stop gateway receivers, gateway senders, locators and servers.
 
 -   **[stop server](#topic_723EE395A63A40D6819618AFC2902115)**
 
-    Stop a Geode cache server.
+    Stop a <%=vars.product_name%> cache server.
 
 ## <a id="topic_CD1D526FD6F84A7B80B25C741129ED30" class="no-quick-link"></a>stop gateway-receiver
 
@@ -158,7 +158,7 @@ stop locator [--name=value] [--host=value] [--port=value] [--dir=value]
 
 | Name                                         | Description                                                                                                                                                                                                                                                                                                                                                                                                                                     | Default Value     |
 |----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|
-| <span class="keyword parmname">&#8209;&#8209;name</span> | The Geode member name or id of the Locator to stop. You must be connected to the JMX Manager to use this option. Can be used to stop remote locators. See [Using gfsh to Manage a Remote Cluster Over HTTP or HTTPS](../../../configuring/cluster_config/gfsh_remote.html). |                   |
+| <span class="keyword parmname">&#8209;&#8209;name</span> | The <%=vars.product_name%> member name or id of the Locator to stop. You must be connected to the JMX Manager to use this option. Can be used to stop remote locators. See [Using gfsh to Manage a Remote Cluster Over HTTP or HTTPS](../../../configuring/cluster_config/gfsh_remote.html). |                   |
 | <span class="keyword parmname">\\-\\-dir</span>  | Directory in which the Locator was started.                                                                                                                                                                                                                                                                                                                                                                                                     | current directory |
 
 <span class="tablecap">Table 3. Stop Locator Parameters</span>
@@ -171,7 +171,7 @@ stop locator [--name=value] [--host=value] [--port=value] [--dir=value]
 
 ## <a id="topic_723EE395A63A40D6819618AFC2902115" class="no-quick-link"></a>stop server
 
-Stop a Geode cache server.
+Stop a <%=vars.product_name%> cache server.
 
 **Availability:** Online or offline. If you want to stop a cache server while you are offline, use the `--dir` option.
 
@@ -185,8 +185,8 @@ stop server [--name=value] [--dir=value]
 
 | Name                                          | Description                                                                                                                                                                                                                                                                                                                                                                                                                           | Default Value     |
 |-----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|
-| <span class="keyword parmname">&#8209;&#8209;name </span> | Name/Id of the Geode Cache Server to stop. You must be connected to the JMX Manager to use this option. Can be used to stop remote servers. See [Using gfsh to Manage a Remote Cluster Over HTTP or HTTPS](../../../configuring/cluster_config/gfsh_remote.html). |                   |
-| <span class="keyword parmname">\\-\\-dir </span>  | Directory in which the Geode Cache Server was started.                                                                                                                                                                                                                                                                                                                                                   | current directory |
+| <span class="keyword parmname">&#8209;&#8209;name </span> | Name/Id of the <%=vars.product_name%> Cache Server to stop. You must be connected to the JMX Manager to use this option. Can be used to stop remote servers. See [Using gfsh to Manage a Remote Cluster Over HTTP or HTTPS](../../../configuring/cluster_config/gfsh_remote.html). |                   |
+| <span class="keyword parmname">\\-\\-dir </span>  | Directory in which the <%=vars.product_name%> Cache Server was started.                                                                                                                                                                                                                                                                                                                                                   | current directory |
 
 <span class="tablecap">Table 4. Stop Server Parameters</span>
 

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gfsh/configuring_gfsh.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gfsh/configuring_gfsh.html.md.erb b/geode-docs/tools_modules/gfsh/configuring_gfsh.html.md.erb
index 6c31756..a8cd350 100644
--- a/geode-docs/tools_modules/gfsh/configuring_gfsh.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/configuring_gfsh.html.md.erb
@@ -19,7 +19,7 @@ See the License for the specific language governing permissions and
 limitations under the License.
 -->
 
-The `gfsh.bat` and `gfsh` bash script automatically append the required Apache Geode and JDK .jar libraries to your existing CLASSPATH. There are user-configurable properties you can set for security, environment variables, logging, and troubleshooting.
+The `gfsh.bat` and `gfsh` bash script automatically append the required <%=vars.product_name_long%> and JDK .jar libraries to your existing CLASSPATH. There are user-configurable properties you can set for security, environment variables, logging, and troubleshooting.
 
 
 ## <a id="concept_3B9C6CE2F64841E98C33D9F6441DF487__section_0D2EEA7A9ED54DFDB2E1EE955E47921E" class="no-quick-link"></a>JAR Libraries in CLASSPATH
@@ -34,7 +34,7 @@ On some operating systems, you may need to ensure that the hostname of your mach
 
 ## <a id="concept_3B9C6CE2F64841E98C33D9F6441DF487__section_3FA4CD2B451B4A30A12D30DDE8DF8619" class="no-quick-link"></a>Configuring gfsh Security
 
-Since `gfsh` must connect to a JMX Manager member to run certain commands (namely those commands that manage and monitor other members), JMX Manager configuration properties can affect `gfsh` security. In `gemfire.properties`, the following Geode properties can affect `gfsh` connection settings to the JMX Manager:
+Since `gfsh` must connect to a JMX Manager member to run certain commands (namely those commands that manage and monitor other members), JMX Manager configuration properties can affect `gfsh` security. In `gemfire.properties`, the following <%=vars.product_name%> properties can affect `gfsh` connection settings to the JMX Manager:
 
 -   `jmx-manager-ssl`
 -   `jmx-manager-port`
@@ -110,9 +110,9 @@ A history of commands that have been executed successfully is logged in `.gfsh.h
 
 ## <a id="concept_3B9C6CE2F64841E98C33D9F6441DF487__section_C84414FF16AB4279A43A41C6C8B61A7E" class="no-quick-link"></a>JMX Manager Update Rate and System Monitoring
 
-When you perform data operations (such as put) and then monitor the state of the system (such as using the gfsh `show metrics` command or Apache Geode Pulse), the monitored system may not immediately reflect the most recent operations. For example, if you perform a put operation and then immediately execute the `show metrics` gfsh command, you may not see the correct number of entries in the region. The management layer updates every 2 seconds. Wait a few seconds after performing operational activity to see the most accurate results.
+When you perform data operations (such as put) and then monitor the state of the system (such as using the gfsh `show metrics` command or <%=vars.product_name%> Pulse), the monitored system may not immediately reflect the most recent operations. For example, if you perform a put operation and then immediately execute the `show metrics` gfsh command, you may not see the correct number of entries in the region. The management layer updates every 2 seconds. Wait a few seconds after performing operational activity to see the most accurate results.
 
-You can modify the `jmx-manager-update-rate` property in `gemfire.properties` to increase or decrease the rate (specified in milliseconds) at which updates are pushed to the JMX Manager. This property setting should be greater than or equal to the `statistic-sample-rate`. You may want to increase this rate if you are experiencing performance issues; however, setting this value too high will cause stale values to be seen in `gfsh` and Apache Geode Pulse.
+You can modify the `jmx-manager-update-rate` property in `gemfire.properties` to increase or decrease the rate (specified in milliseconds) at which updates are pushed to the JMX Manager. This property setting should be greater than or equal to the `statistic-sample-rate`. You may want to increase this rate if you are experiencing performance issues; however, setting this value too high will cause stale values to be seen in `gfsh` and <%=vars.product_name%> Pulse.
 
 ## Formatting of Results
 

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gfsh/getting_started_gfsh.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gfsh/getting_started_gfsh.html.md.erb b/geode-docs/tools_modules/gfsh/getting_started_gfsh.html.md.erb
index 3a2b8f9..c09add0 100644
--- a/geode-docs/tools_modules/gfsh/getting_started_gfsh.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/getting_started_gfsh.html.md.erb
@@ -25,7 +25,7 @@ The `gfsh` utility provides useful features for a shell environment, including c
 
 **To view a list of available gfsh commands, press Tab at an empty prompt.**
 
-The list of commands you see depends on whether you are connected to a Geode distributed system. If you are not connected, you see a list of local commands that are available.
+The list of commands you see depends on whether you are connected to a <%=vars.product_name%> distributed system. If you are not connected, you see a list of local commands that are available.
 
 **Use the hint command to get information on a particular topic.**
 

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gfsh/gfsh_command_index.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gfsh/gfsh_command_index.html.md.erb b/geode-docs/tools_modules/gfsh/gfsh_command_index.html.md.erb
index e921fdc..2798096 100644
--- a/geode-docs/tools_modules/gfsh/gfsh_command_index.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/gfsh_command_index.html.md.erb
@@ -23,7 +23,7 @@ This section provides help and usage information on all `gfsh` commands, listed
 
 -   **[alter](../../tools_modules/gfsh/command-pages/alter.html)**
 
-    Modify an existing Geode resource.
+    Modify an existing <%=vars.product_name%> resource.
 
 -   **[backup disk-store](../../tools_modules/gfsh/command-pages/backup.html)**
 
@@ -127,7 +127,7 @@ This section provides help and usage information on all `gfsh` commands, listed
 
 -   **[list](../../tools_modules/gfsh/command-pages/list.html)**
 
-    List existing Geode resources such as deployed applications, disk-stores, functions, members, servers, and regions.
+    List existing <%=vars.product_name%> resources such as deployed applications, disk-stores, functions, members, servers, and regions.
 
 -   **[load-balance gateway-sender](../../tools_modules/gfsh/command-pages/load-balance.html)**
 
@@ -155,7 +155,7 @@ This section provides help and usage information on all `gfsh` commands, listed
 
 -   **[query](../../tools_modules/gfsh/command-pages/query.html)**
 
-    Run queries against Geode regions.
+    Run queries against <%=vars.product_name%> regions.
 
 -   **[rebalance](../../tools_modules/gfsh/command-pages/rebalance.html)**
 
@@ -203,7 +203,7 @@ This section provides help and usage information on all `gfsh` commands, listed
 
 -   **[status](../../tools_modules/gfsh/command-pages/status.html)**
 
-    Check the status of the cluster configuration service and Geode member processes, including locators, gateway receivers, gateway senders, and servers.
+    Check the status of the cluster configuration service and <%=vars.product_name%> member processes, including locators, gateway receivers, gateway senders, and servers.
 
 -   **[stop](../../tools_modules/gfsh/command-pages/stop.html)**
 

http://git-wip-us.apache.org/repos/asf/geode/blob/bb988caa/geode-docs/tools_modules/gfsh/gfsh_quick_reference.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/tools_modules/gfsh/gfsh_quick_reference.html.md.erb b/geode-docs/tools_modules/gfsh/gfsh_quick_reference.html.md.erb
index 4c78194..03a08ee 100644
--- a/geode-docs/tools_modules/gfsh/gfsh_quick_reference.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/gfsh_quick_reference.html.md.erb
@@ -25,7 +25,7 @@ This quick reference sorts all commands into functional areas.
 
 Click a command to see additional information, including syntax, a list of options, and examples.
 
--   **[Basic Geode gfsh Commands](quick_ref_commands_by_area.html#topic_77DA6E3929404EB4AC24230CC7C21493)**
+-   **[Basic <%=vars.product_name%> gfsh Commands](quick_ref_commands_by_area.html#topic_77DA6E3929404EB4AC24230CC7C21493)**
 
 -   **[Configuration Commands](quick_ref_commands_by_area.html#topic_EB854534301A477BB01058B3B142AE1D)**
 
@@ -41,7 +41,7 @@ Click a command to see additional information, including syntax, a list of optio
 
 -   **[Gateway (WAN) Commands](quick_ref_commands_by_area.html#topic_F0AE5CE40D6D49BF92247F5EF4F871D2)**
 
--   **[Geode Monitoring Commands](quick_ref_commands_by_area.html#topic_B742E9E862BA457082E2346581C97D03)**
+-   **[<%=vars.product_name%> Monitoring Commands](quick_ref_commands_by_area.html#topic_B742E9E862BA457082E2346581C97D03)**
 
 -   **[Index Commands](quick_ref_commands_by_area.html#topic_688C66526B4649AFA51C0F72F34FA45E)**
 


Mime
View raw message