fix(readme): made webhook part less confusing (#60)

Author: s0up4200

README.md

@@ -252,9 +252,9 @@ When run as a service it exposes an HTTP server as well. Generate an **API Token
 
 To refresh the filters you can make a **POST** or **GET** request to the following:
 
-- `http://localhost:7441/api/webhook/trigger/arr`. - This will trigger all arr filters. (Use this in you arr instances)
-- `http://localhost:7441/api/webhook/trigger/lists`. - This will trigger all lists filters.
-- `http://localhost:7441/api/webhook/trigger`. - This will trigger all filters.
+- `http://localhost:7441/api/webhook/trigger/arr?apikey=MY_NEW_LONG_SECURE_TOKEN` - This will trigger all arr filters. (Use this in you arr instances)
+- `http://localhost:7441/api/webhook/trigger/lists?apikey=MY_NEW_LONG_SECURE_TOKEN` - This will trigger all lists filters.
+- `http://localhost:7441/api/webhook/trigger?apikey=MY_NEW_LONG_SECURE_TOKEN` - This will trigger all filters.
 
 The API Token can be set as either an HTTP header like `X-API-Token`, or be passed in the url as a query param like `?apikey=MY_NEW_LONG_SECURE_TOKEN`.
 
@@ -326,4 +326,4 @@ If you are not running a reverse proxy change host in the `config.toml` to `0.0.
 
 On first run it will create a default config, `~/.config/omegabrr/config.yaml` that you will need to edit.
 
-After the config is edited you need to restart the service `systemctl restart omegabrr@$USERNAME.service`.
+After the config is edited you need to restart the service `systemctl restart omegabrr@$USERNAME.service`.