[DOCS] Clarify that security is enabled and configured when starting …

…ES (elastic#83285) Previously, running a configuration command was required to enable and configure security for Elasticsearch. This requirement is no longer necessary, and this change updates the text to reflect that. Co-authored-by: Elastic Machine <[email protected]>
vijay2308 · Jan 31, 2022 · 6152ffd · 6152ffd
1 parent 50fcaac
commit 6152ffd
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/x-pack/docs/en/security/index.asciidoc b/x-pack/docs/en/security/index.asciidoc
@@ -12,8 +12,8 @@ safe, adhere to the <<es-security-principles,{es} security principles>>.
 The first principle is to run {es} with security enabled. Configuring security
 can be complicated, so we made it easy to
 <<configuring-stack-security,start the {stack} with security enabled>> by
-default. Run a single configuration command and then start {es} to enable the
-{stack} security features. You can then connect a {kib} instance to your
+default. Just start {es} to enable and configure the {stack} security features.
+You can then connect a {kib} instance to your
 secured {es} cluster and enroll additional nodes. You'll have password
 protection, internode communication secured with Transport Layer Security (TLS),
 and encrypted connections between {es} and {kib}.