SONAR-17232 Improve SAML documentation

diff --git a/server/sonar-docs/src/pages/instance-administration/authentication/saml/overview.md b/server/sonar-docs/src/pages/instance-administration/authentication/saml/overview.md
index 1122f01ad512b32567432d7ba5d5b255b1efc5cc..53ff545ab9e4713886fb49b91a0599625d73ac43 100644 (file)
--- a/server/sonar-docs/src/pages/instance-administration/authentication/saml/overview.md
+++ b/server/sonar-docs/src/pages/instance-administration/authentication/saml/overview.md
@@ -8,7 +8,7 @@ You can delegate authentication to a SAML 2.0 Identity Provider using SAML Authe
 ## SAML authentication flow
 
 1. When a user requests a SonarQube web page and is not already authenticated, SonarQube will start a SAML authentication process.
-2. SonarQube creates a SAML request for the configured Identity Provider and sends it back to the user.
+2. SonarQube creates a SAML request for the configured Identity Provider and sends it back to the user's browser.
 3. The user's browser automatically relays the SAML request to the Identity Provider.
 4. The Identity Provider authenticates the user and creates a SAML assertion containing the user information and privilege. Optionally, it can encrypt this assertion with the SonarQube certificate.
 5. The Identity Provider sends a SAML assertion back to the web browser