From c7bf771dd7c752dc9737e8807bd0a2ae29f69e0f Mon Sep 17 00:00:00 2001
From: Ralf Dyllick-Brenzinger <41058728+dada-dudu@users.noreply.github.com>
Date: Wed, 18 May 2022 10:28:11 +0200
Subject: [PATCH] Improved language

---
 manual/deploy/outlook_addin_config.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/manual/deploy/outlook_addin_config.md b/manual/deploy/outlook_addin_config.md
index 0e4a5fef..a0cbc4ab 100644
--- a/manual/deploy/outlook_addin_config.md
+++ b/manual/deploy/outlook_addin_config.md
@@ -2,10 +2,10 @@
 
 The Seafile Add-in for Outlook natively supports authentication via username and password. In order to authenticate with SSO, the add-in utilizes SSO support integrated in Seafile's webinterface Seahub. 
 
-Specifically, this is how the add-in makes use of  :
+Specifically, this is how SSO with the add-in works :
 * When clicking the SSO button in the add-in, the add-in opens a browser window and requests `http(s)://SEAFILE_SERVER_URL/outlook/`
 * A PHP script redirects the request to `http(s)://SEAFILE_SERVER_URL/accounts/login/` including a redirect request to /outlook/ following a successful authentication (e.g., `https://demo.seafile.com/accounts/login/?next=/jwt-sso/?page=/outlook/`)
-* The identity provider signals to Seafile that the user's successful authentication
+* The identity provider signals to Seafile the user's successful authentication
 * The PHP script sends an API-token to the add-in
 * The add-in authorizes all API calls with the API-token