From a32a0c49a8d1e517b0f4934a77f3d615b82cefcf Mon Sep 17 00:00:00 2001
From: Nite <55684536+nitehu@users.noreply.github.com>
Date: Thu, 16 Sep 2021 08:14:19 +0200
Subject: [PATCH] Updated Authentication used in the Subsonic API (markdown)

---
 Authentication-used-in-the-Subsonic-API.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Authentication-used-in-the-Subsonic-API.md b/Authentication-used-in-the-Subsonic-API.md
index aa5c5dd..9cb629a 100644
--- a/Authentication-used-in-the-Subsonic-API.md
+++ b/Authentication-used-in-the-Subsonic-API.md
@@ -1,6 +1,6 @@
 The Subsonic-like servers use two distinct format of authentication, usually based on what version of the Subsonic API they support. These are called Plain Password (or LDAP), and Token-based. Ultrasonic tries to use the slightly more secure Token-based if it is available, but the servers not always support that - the Subsonic error "Authentication by token is not supported for LDAP users" tries to tell this.  
 
-If Authentication by Token is not supported, you can try the plain password one by turning "Force plain password authentication" on. Also, if your server only supports Tokens (e.g. like Ampache when configured to use API Keys), turn this setting off.  
+If Authentication by Token is not supported, you can try the plain password one by turning "Force plain password authentication" on in the server settings. Also, if your server only supports Tokens (e.g. like Ampache when configured to use API Keys), turn this setting off.  
 
 ### What is the difference between the two methods