From 907b3fd227958ee60a520c44bcfc74c9e19daea8 Mon Sep 17 00:00:00 2001
From: GreaterFire <32649575+GreaterFire@users.noreply.github.com>
Date: Thu, 4 Oct 2018 21:39:50 -0700
Subject: [PATCH] refine doc

---
 docs/authenticator.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/authenticator.md b/docs/authenticator.md
index 2c900f36..4217b86d 100644
--- a/docs/authenticator.md
+++ b/docs/authenticator.md
@@ -28,7 +28,7 @@ CREATE TABLE users (
 );
 ```
 
-Note that trojan will only read/write the `password`, `quota`, `download`, and `upload` fields. Other fields exist for management convenience. The passwords stored in the table have to be hashed by SHA224 for efficiency and security reasons. You can use [trojan-manager](https://github.com/trojan-gfw/trojan-manager) (which stores passwords as `SHA224(username:password)` so that clients have to prepend `username:` to the passwords in their config files) to manage users in the database.
+Note that trojan will only read/write the `password`, `quota`, `download`, and `upload` fields. Other fields exist for management convenience. The passwords stored in the table have to be hashed by SHA224 for efficiency and security reasons.
 
 Upon receiving a Trojan Request, **if the server fails to match the password with any passwords set in the config file**, it will query the database for the user. If it succeeds, trojan will check whether `download + upload < quota`; if so, the connection is granted. **A negative `quota` value means infinite quota.** After a connection is closed, trojan will increment `download` and `upload` fields of that user by the amount of data the user has used.