📝 Some fixes in README

Androz2091 · Androz2091 · commit a2cd2c78380e · 2021-02-13T14:02:44.000+01:00
diff --git a/README.md b/README.md
@@ -37,4 +37,4 @@ Slash Commands GUI relies on a CORS proxy to make requests to the Discord API. T
 
 ## Security
 
-Authentication was one of the difficult things to do in this application. In v0.0.1, users had to enter their bot tokens. After talking with API contributors to get their opinion, it was removed in favor of authentication using client ID and client secrecy. This allows the application to generate and store an oAuth2 token with the scope `applications.commands.update` only, without having to store the bot token. Note that in any case, this application does not need a backend to work. All requests are made with the client (only through a CORS proxy, whose URL is configurable), so the risk of token hacking is almost null (someone would have to install a virus on your computer, and they would then only have access to an oauth token with the scope `applications.commands.update`).
+Authentication was one of the difficult things to do in this application. In v0.0.1, users had to enter their bot tokens. After talking with API contributors to get their opinion, it was removed in favor of authentication using the client ID and the client secret. This allows the application to generate and store an oAuth2 token with the scope `applications.commands.update` only, without having to store the bot token. Note that in any case, this application does not need a backend to work. All requests are made with the client (only through a CORS proxy, whose URL is configurable), so the risk of token hacking is almost null (someone would have to install a virus on your computer, and they would then only have access to an oauth token with the scope `applications.commands.update`).

Original file line number	Diff line number	Diff line change
`@@ -37,4 +37,4 @@ Slash Commands GUI relies on a CORS proxy to make requests to the Discord API. T`
`37`	`37`
`38`	`38`	`## Security`
`39`	`39`
`40`		-Authentication was one of the difficult things to do in this application. In v0.0.1, users had to enter their bot tokens. After talking with API contributors to get their opinion, it was removed in favor of authentication using client ID and client secrecy. This allows the application to generate and store an oAuth2 token with the scope `applications.commands.update` only, without having to store the bot token. Note that in any case, this application does not need a backend to work. All requests are made with the client (only through a CORS proxy, whose URL is configurable), so the risk of token hacking is almost null (someone would have to install a virus on your computer, and they would then only have access to an oauth token with the scope `applications.commands.update`).
	`40`	+Authentication was one of the difficult things to do in this application. In v0.0.1, users had to enter their bot tokens. After talking with API contributors to get their opinion, it was removed in favor of authentication using the client ID and the client secret. This allows the application to generate and store an oAuth2 token with the scope `applications.commands.update` only, without having to store the bot token. Note that in any case, this application does not need a backend to work. All requests are made with the client (only through a CORS proxy, whose URL is configurable), so the risk of token hacking is almost null (someone would have to install a virus on your computer, and they would then only have access to an oauth token with the scope `applications.commands.update`).