[geode] branch support/1.14 updated: GEODE-9797: User guide typo repairs (#7085)

[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 120165b  GEODE-9797: User guide typo repairs (#7085)
120165b is described below

commit 120165b9dc188e5f212fa7347636f7a3070cc988
Author: Dave Barnes <db...@apache.org>
AuthorDate: Fri Nov 5 09:17:08 2021 -0700

    GEODE-9797: User guide typo repairs (#7085)
---
 geode-docs/managing/security/authentication_examples.html.md.erb     | 2 +-
 geode-docs/managing/security/implementing_authentication.html.md.erb | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/geode-docs/managing/security/authentication_examples.html.md.erb b/geode-docs/managing/security/authentication_examples.html.md.erb
index ce73399..b57ce38 100644
--- a/geode-docs/managing/security/authentication_examples.html.md.erb
+++ b/geode-docs/managing/security/authentication_examples.html.md.erb
@@ -34,7 +34,7 @@ spoof the system.
 
 This example assumes that a set of user name and password pairs
 representing users that may be successfully authenticated 
-has been read into a data structure upon intialization.
+has been read into a data structure upon initialization.
 Any component that presents the correct password for a user name
 successfully authenticates,
 and its identity is verified as that user.
diff --git a/geode-docs/managing/security/implementing_authentication.html.md.erb b/geode-docs/managing/security/implementing_authentication.html.md.erb
index 4429708..3a5e01d 100644
--- a/geode-docs/managing/security/implementing_authentication.html.md.erb
+++ b/geode-docs/managing/security/implementing_authentication.html.md.erb
@@ -57,7 +57,7 @@ For example:
 security-username=admin
 security-password=xyz1234
 ```
-The username and password are stored in the clear, so the
+The username and password are stored in cleartext, so the
 `gfsecurity.properties` file must be protected by restricting access with
 file system permissions.