Readme Updated

3 years ago · fd3c5d2245
parent 798d38cb74
commit fd3c5d2245
1 changed files with 1 additions and 1 deletions
--- a/README.md
+++ b/README.md
@ -690,4 +690,4 @@ For any unsuccsesful attempt or wrong token, you will receive a 401 error respon
 When a new user is created, the `user` role is aassigned to them. To change this behavior, open your `.env` file and set the value of `DEFAULT_ROLE_ID` to any existing role id and newly created users will have that role by default. For example, if you want your new users to have a `customer` role, set `DEFAULT_ROLE_ID=3` in your `.env` file.

 ### Single Session or Multiple Session
-When a user authenticates, Hydra doesn't invalidate the previously issued access token. So, all access tokens including the newly created token will remain balid. If you want to change this behavior and delete all previous tokens when a user authenticates, set `DELETE_PREVIOUS_ACCESS_TOKENS_ON_LOGIN` to `true`. The value of `DELETE_PREVIOUS_ACCESS_TOKENS_ON_LOGIN` is `false` by default.
+When a user authenticates, Hydra doesn't invalidate the previously issued access token. So, all access tokens including the newly created token will remain balid. If you want to change this behavior and delete all previous tokens when a user authenticates, set `DELETE_PREVIOUS_ACCESS_TOKENS_ON_LOGIN` to `true` in your `.env` file. The value of `DELETE_PREVIOUS_ACCESS_TOKENS_ON_LOGIN` is set to `false` by default.