From 578135411e8b179195adc00cb254696880a1c527 Mon Sep 17 00:00:00 2001
From: Nite <55684536+nitehu@users.noreply.github.com>
Date: Thu, 16 Sep 2021 08:23:11 +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 9cb629a..a4c226a 100644
--- a/Authentication-used-in-the-Subsonic-API.md
+++ b/Authentication-used-in-the-Subsonic-API.md
@@ -42,7 +42,7 @@ Subsonic-like servers have a few solution to this problem:
 As you can see, there are usually multiple configuration options on both the server and the client side, and it is very easy to end up with something that isn't working or isn't secure.
 
 ### What is the best practice
-DISCLAIMER: Please always follow industry security best practices when you configure your server and your client. We won't take any responsibility if your data is stolen or your account is compromised in any way.  
+DISCLAIMER: Please always follow industry standard security best practices when you configure your server and your client. We won't take any responsibility if your data is stolen or your account is compromised in any way.  
 
 That out of the way, some tips:
 - Always use a separate, strong password for your Subsonic user account. If you can't remember so much strong passwords, use a password manager (like for example [KeePass](https://keepass.info/))