[DOCS] Refreshes security tutorial

Author: lcawl

docs/en/stack/get-started-trial.asciidoc

@@ -9,8 +9,8 @@ For more information about Elastic license levels, see
 https://www.elastic.co/subscriptions.
 
 You can start a 30-day trial to try out all of the platinum features, including 
-{security} and {ml}. Click **Start trial** on the **License Management** page in 
-{kib}.
+{security-features} and {ml-features}. Click **Start trial** on the 
+**License Management** page in {kib}.
 
 IMPORTANT: If your cluster has already activated a trial license for the current 
 major version, you cannot start a new trial. For example, if you have already 

docs/en/stack/security/get-started-builtin-users.asciidoc

@@ -1,6 +1,6 @@
-There are <<built-in-users,built-in users>> that you can use for specific administrative purposes:
-`elastic`, `kibana`, `logstash_system`, `apm_system`, `beats_system`, and 
-`remote_monitoring_user`. 
+There are <<built-in-users,built-in users>> that you can use for specific
+administrative purposes: `apm_system`, `beats_system`, `elastic`, `kibana`,
+`logstash_system`,  and `remote_monitoring_user`. 
 
 Before you can use them, you must set their passwords:
 

docs/en/stack/security/get-started-enable-security.asciidoc

@@ -1,4 +1,5 @@
-When you use the trial license, {security} is disabled by default. To enable it:
+When you use the trial license, the {es} {security-features} are disabled by
+default. To enable them:
 
 . Stop {kib}. The method for starting and stopping {kib} varies depending on 
 how you installed it. For example, if you installed {kib} from an archive 
@@ -29,11 +30,11 @@ xpack.security.enabled: true
 TIP: If you have a basic or trial license, the default value for this setting is 
 `false`. If you have a gold or higher license, the default value is `true`. 
 Therefore, it is a good idea to explicitly add this setting to avoid confusion 
-about whether {security} is enabled.  
+about whether {security-features} are enabled.  
 
 --
 
-When you enable {security}, basic authentication is enabled by default. To 
-communicate with the cluster, you must specify a username and password.
-Unless you <<anonymous-access,enable anonymous access>>, all requests that don't 
-include a user name and password are rejected.
+When you enable {es} {security-features}, basic authentication is enabled by
+default. To communicate with the cluster, you must specify a username and
+password. Unless you <<anonymous-access,enable anonymous access>>, all requests
+that don't include a user name and password are rejected.

docs/en/stack/security/get-started-kibana-users.asciidoc

@@ -1,5 +1,5 @@
-When {security} is enabled, users must log in to {kib} with a valid user ID and 
-password. 
+When the {es} {security-features} are enabled, users must log in to {kib}
+with a valid user ID and password. 
 
 {kib} also performs some tasks under the covers that require use of the 
 built-in `kibana` user. 

docs/en/stack/security/get-started-security.asciidoc

@@ -71,9 +71,9 @@ manage all the other users.
 
 The {stack} _authenticates_ users to ensure that they are valid. The 
 authentication process is handled by _realms_. You can use one or more built-in 
-realms, such as the native, file, LDAP, PKI, Active Directory, or SAML realms. 
-Alternatively, you can create your own custom realms. In this tutorial, we'll  
-use a native realm. 
+realms, such as the native, file, LDAP, PKI, Active Directory, SAML, or Kerberos
+realms. Alternatively, you can create your own custom realms. In this tutorial,
+we'll use a native realm. 
 
 In general, you configure realms by adding `xpack.security.authc.realms` 
 settings in the `elasticsearch.yml` file. However, the native realm is available 
@@ -98,10 +98,10 @@ Let's create two users in the native realm.
 [role="screenshot"]
 image::security/images/management-builtin-users.jpg["User management screenshot in Kibana"]
 
-In this example, you can see all of the built-in users. 
+In this example, you can see a list of built-in users. 
 --
 
-. Click *Create user* to make a new user. For example, create a user for yourself:
+. Click *Create new user*. For example, create a user for yourself:
 +
 --
 [role="screenshot"]
@@ -111,7 +111,7 @@ You'll notice that when you create a user, you can assign it a role. Don't
 choose a role yet--we'll come back to that in subsequent steps.
 --
 
-. Click *Create user* and create a `logstash_internal` user.
+. Click *Create new user* and create a `logstash_internal` user.
 +
 --
 In {stack-gs}/get-started-elastic-stack.html[Geting started with the {stack}],