Small extension of docs.

Author: JC5

docs/docs/how-to/firefly-iii/features/webhooks.md

@@ -12,9 +12,9 @@ Webhooks need to be enabled before they work. Set `ALLOW_WEBHOOKS=true`, either
 
 There are a bunch of triggers for webhooks in Firefly III:
 
-- When a transaction is created, updated or removed
+- When a transaction is created, updated or removed.
 - When a budget is created, updated or removed
-- (some other trigger)
+- When a budget amount is set or changed
 - When any of the above happens
 
 A webhook can respond to multiple triggers. BUT, you cannot combine the  "After any event" with other triggers, it would have to be the only trigger. I hope this makes sense, because "After any event" already includes everything.
@@ -31,6 +31,12 @@ If you select "Relevant details" as the response, Firefly III will send the rele
 
 It is mandatory to select "Relevant details" when you select "After any event" as the trigger. This is because "After any event" can trigger on many different events, and Firefly III cannot know what you want to receive. Therefore, it will always send the relevant details for the event that triggered the webhook.
 
+Relevant details consist of:
+
+- For transaction related events: the transaction itself
+- For budget related events: the budget itself
+- For budget amount related events: the "budget limit", i.e. the amount for that particular period.
+
 ### Transaction details
 
 You can choose to receive the transaction details for transaction related events.

docs/docs/references/firefly-iii/api/index.md

@@ -48,7 +48,7 @@ Firefly III supports webhooks, which you can read more about on the page about [
 
 A webhook needs a title and a URL to work, and three important things.
 
-1. A set of triggers. Use `GET api/v1/configuration/webhook.triggers` to get the available values. This may change in the future.
+1. A set of triggers. Use `GET api/v1/configuration/webhook.triggers` to get the available values, because they may change in the future.
 2. A response. Use `GET api/v1/configuration/webhook.responses` to see what is available. New responses may be added in the future.
 3. A delivery format. Use `GET api/v1/configuration/webhook.deliveries` to see what is available. This is only `JSON` right now.