Jira DOC-958: RS - Admin security index page typos (#1627)

* Initial fixes.

* Editorial feedback changes.

* More typos; more fixes.

content/rs/security/admin-console-security/_index.md

@@ -12,15 +12,17 @@ Redis Enterprise comes with a web-based user interface known as the **admin cons
 * User authentication using LDAP
 * Role-based access control
 
-We recommend that you use the features to implement the following best practices:
+We recommend the following practices:
 
-- **Integrate with an external identity provider**: Redis Enterprise supports integrations with an external identity provider, such as Active Directory, through an [LDAP integration]({{< relref "/rs/security/admin-console-security/user-security.md#setting-up-ldap" >}}). 
+- **Integrate with an external identity provider**: Redis Enterprise uses [LDAP integration]({{< relref "/rs/security/admin-console-security/user-security.md#setting-up-ldap" >}}) to support external identity providers, such as Active Directory.
 
-- **Implement standard authenticaion practices**: If your organization does not support LDAP, you can still use Redis Enterprise's [user account security]({{< relref "/rs/security/admin-console-security/user-security.md#user-account-security" >}}). Features include basic password complexity requirements, password expiration, and user login lockouts.
+- **Implement standard authentication practices**: If your organization does not support LDAP, you can still use Redis Enterprise's [user account security]({{< relref "/rs/security/admin-console-security/user-security.md#user-account-security" >}}). Features include basic password complexity requirements, password expiration, and user login lockouts.
 
-- **Limit session timeouts**: Session timeouts, or automatic logout, help to prevent inadvertent unauthorized access. You can configure the [A session will only be available for a set amount of time]({{< relref "/rs/security/passwords-users-roles.md#session-timeout" >}}) before the user is required to re-authenticate. By default, Redis Enterprise logs user out of the admin console after 15 minutes of inactivity.
+- **Limit session timeouts**: Session timeouts, also known as _automatic sign out_, help prevent unauthorized access. Admin console sessions are allowed to idle for [a period of time]({{< relref "/rs/security/passwords-users-roles.md#session-timeout" >}}) before users are required to re-authenticate. 
 
-- **Require HTTPS for API endpoints** - Redis Enterprise comes with an API that users are able to use to automate frequent manual tasks. This API is availible in both an encrypted and unencrypted endpoint for backwards compatibility. You can [disable the unencrypted endpoint]({{< relref "/rs/security/admin-console-security/encryption.md#requiring-https-for-api-endpoints" >}}) if its not in use without any impact.
+    By default, users are signed out after 15 minutes of inactivity.  You can set the [timeout period]({{< relref "/rs/security/admin-console-security/user-security#session-timeout" >}}).
+
+- **Require HTTPS for API endpoints** - Redis Enterprise comes with a REST API to help automate tasks. This API is available in both an encrypted and unencrypted endpoint for backward compatibility. You can [disable the unencrypted endpoint]({{< relref "/rs/security/admin-console-security/encryption.md#requiring-https-for-api-endpoints" >}}) with no loss in functionality.
 
 - **Configure Transport Layer Security (TLS)** - A common compliance requirement is to [set a minimum version of TLS]({{< relref "rs/security/admin-console-security/encryption.md#tls-configuration" >}}). This helps to make sure that only secure versions of TLS are allowed when accessing the cluster.