Bläddra i källkod

[DOCS] Remove unneeded spaces (#64759) (#64781)

Co-authored-by: Johannes Mahne <johannes.mahne@elastic.co>
James Rodewig 5 år sedan
förälder
incheckning
678c11c367
1 ändrade filer med 2 tillägg och 2 borttagningar
  1. 2 2
      x-pack/docs/en/security/authentication/saml-guide.asciidoc

+ 2 - 2
x-pack/docs/en/security/authentication/saml-guide.asciidoc

@@ -889,8 +889,8 @@ in {es}. See <<saml-guide-authentication>>
 
 The realm is designed with the assumption that there needs to be a privileged entity
 acting as an authentication proxy. In this case, the custom web application is the
-authentication proxy handling the authentication of end users ( more correctly,
-"delegating" the authentication to the SAML Identity Provider ). The SAML related
+authentication proxy handling the authentication of end users (more correctly,
+"delegating" the authentication to the SAML Identity Provider). The SAML related
 APIs require authentication and the necessary authorization level for the authenticated
 user. For this reason, you must create a Service Account user and assign it a role
 that gives it the `manage_saml` cluster privilege. The use of the `manage_token`