diff --git a/docs/content/2.docs/2.hooks.md b/docs/content/2.docs/2.hooks.md
index fc370c4..58e0a85 100644
--- a/docs/content/2.docs/2.hooks.md
+++ b/docs/content/2.docs/2.hooks.md
@@ -7,7 +7,7 @@ Hooks in Backrest allow you to respond to various operation lifecycle events, en
 Hooks can be triggered by the following events:
 
 ### Snapshot Events
-- `CONDITION_SNAPSHOT_START`: Triggered when a backup operation begins and will complete before the snapshot starts. The [Error Handling](#error-handling) configuration can be used to stop the backup if the command isnt successful.
+- `CONDITION_SNAPSHOT_START`: Triggered when a backup operation begins and will complete before the snapshot starts. The [Error Handling](#error-handling) configuration can be used to stop the backup if the command isn't successful.
 - `CONDITION_SNAPSHOT_END`: Triggered when a backup operation completes (regardless of success/failure)
 - `CONDITION_SNAPSHOT_SUCCESS`: Triggered when a backup operation completes successfully
 - `CONDITION_SNAPSHOT_ERROR`: Triggered when a backup operation fails
@@ -41,7 +41,7 @@ Backrest supports multiple notification services for hook delivery:
 | Slack    | Send notifications to Slack channels   | [Slack Webhooks Guide](https://api.slack.com/messaging/webhooks)                                    |
 | Gotify   | Send notifications via Gotify server   | [Gotify Documentation](https://github.com/gotify/server)                                            |
 | Shoutrrr | Multi-provider notification service    | [Shoutrrr Documentation](https://containrrr.dev/shoutrrr/v0.8/)                                     |
-| Command  | Execute custom commands                | See command cookbook                                                                                |
+| Command  | Execute custom commands                | See [command cookbook](../../cookbooks/command-hook-examples)                                       |
 
 ## Error Handling