[geode] branch support/1.14 updated: GEODE-9316: user guide typo repairs (#6541)

[db...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

dbarnes pushed a commit to branch support/1.14
in repository https://gitbox.apache.org/repos/asf/geode.git


The following commit(s) were added to refs/heads/support/1.14 by this push:
     new 9d7ed44  GEODE-9316: user guide typo repairs (#6541)
9d7ed44 is described below

commit 9d7ed44ff7e068872671e278e953c94a54fd345d
Author: Dave Barnes <db...@apache.org>
AuthorDate: Tue Jun 1 14:00:28 2021 -0700

    GEODE-9316: user guide typo repairs (#6541)
---
 .../managing/management/management_and_monitoring_features.html.md.erb  | 2 +-
 .../system_member_performance_distributed_system_member.html.md.erb     | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/geode-docs/managing/management/management_and_monitoring_features.html.md.erb b/geode-docs/managing/management/management_and_monitoring_features.html.md.erb
index ba36020..ffcafaa 100644
--- a/geode-docs/managing/management/management_and_monitoring_features.html.md.erb
+++ b/geode-docs/managing/management/management_and_monitoring_features.html.md.erb
@@ -27,7 +27,7 @@ Application and manager development is much easier because you do not have to fi
 Some other key advantages and features of <%=vars.product_name%> administration architecture:
 
 -   <%=vars.product_name%> monitoring is tightly integrated into <%=vars.product_name%>'s processes instead of running in a separately installed and configured monitoring agent. You can use the same framework to actually manage <%=vars.product_name%> and perform administrative operations, not just monitor it.
--   All <%=vars.product_name%> MBeans are *MXBeans*. They represent useful and relevant information on the state of the cluster and all its members. Because MXBeans use the Open MBean model with a predefined set of types, clients and remote management programs no longer require access to model-specific classes representing your MBean types. Using MXBeans adds flexibility to your selection of clients and makes the <%=vars.product_name%> management and monitoring much easier to use.
+-   All <%=vars.product_name%> MBeans are *MXBeans*. They represent useful and relevant information on the state of the cluster and all its members. Because MXBeans use the Open MBean model with a predefined set of types, clients and remote management programs do not require access to model-specific classes representing your MBean types. Using MXBeans adds flexibility to your selection of clients and makes the <%=vars.product_name%> management and monitoring much easier to use.
 -   Each member in the cluster is manageable through MXBeans, and each member hosts its own MXBeans in a Platform MBeanServer.
 -   Any <%=vars.product_name%> member can be configured to provide a federated view of all the MXBeans for all members in a <%=vars.product_name%> cluster.
 -   <%=vars.product_name%> has also modified its use of JMX to be industry-standard and friendly to generic JMX clients. You can now easily monitor or manage the cluster by using any third-party tool that is compliant with JMX. For example, JConsole.
diff --git a/geode-docs/managing/monitor_tune/system_member_performance_distributed_system_member.html.md.erb b/geode-docs/managing/monitor_tune/system_member_performance_distributed_system_member.html.md.erb
index 89001ed..ba60d33 100644
--- a/geode-docs/managing/monitor_tune/system_member_performance_distributed_system_member.html.md.erb
+++ b/geode-docs/managing/monitor_tune/system_member_performance_distributed_system_member.html.md.erb
@@ -21,7 +21,7 @@ limitations under the License.
 
 Several performance-related properties apply to a cache server or application that connects to the cluster.
 
--   **statistic-sampling-enabled**.Turning off statistics sampling saves resources, but it also takes away potentially valuable information for ongoing system tuning and unexpected system problems. If LRU eviction is configured, then statistics sampling must be on.
+-   **statistic-sampling-enabled**. Turning off statistics sampling saves resources, but it also takes away potentially valuable information for ongoing system tuning and unexpected system problems. If LRU eviction is configured, then statistics sampling must be on.
 -   **statistic-sample-rate**. Increasing the sample rate for statistics reduces system resource use while still providing some statistics for system tuning and failure analysis.
 -   **log-level**. As with the statistic sample rate, lowering this setting reduces system resource consumption. See [Logging](../logging/logging.html#concept_30DB86B12B454E168B80BB5A71268865).