diff --git a/umbraco-heartcore/getting-started/images/addWebhook-1.png b/umbraco-heartcore/getting-started/images/addWebhook-1.png
new file mode 100644
index 00000000000..302c91a934c
Binary files /dev/null and b/umbraco-heartcore/getting-started/images/addWebhook-1.png differ
diff --git a/umbraco-heartcore/getting-started/images/manageWebhooks-1.png b/umbraco-heartcore/getting-started/images/manageWebhooks-1.png
new file mode 100644
index 00000000000..9328e1384bd
Binary files /dev/null and b/umbraco-heartcore/getting-started/images/manageWebhooks-1.png differ
diff --git a/umbraco-heartcore/getting-started/images/webhooksDashboards-1.png b/umbraco-heartcore/getting-started/images/webhooksDashboards-1.png
new file mode 100644
index 00000000000..7d075615581
Binary files /dev/null and b/umbraco-heartcore/getting-started/images/webhooksDashboards-1.png differ
diff --git a/umbraco-heartcore/getting-started/webhooks.md b/umbraco-heartcore/getting-started/webhooks.md
index 9621f91a587..c85d4d9e714 100644
--- a/umbraco-heartcore/getting-started/webhooks.md
+++ b/umbraco-heartcore/getting-started/webhooks.md
@@ -1,8 +1,8 @@
 # Webhooks
 
-In this article you can learn more about how to use Webhooks, and how to set them up.
+In this article, you can learn more about how to use Webhooks and set them up.
 
-Webhooks from the backoffice works the same way as the webhooks from the portal. It gives you an option to hook into different actions in order to post information about the action elsewhere.
+Webhooks from the backoffice work the same way as the Webhooks from the portal. It gives you an option to hook into different actions to post information about the action elsewhere.
 
 ## Usage
 
@@ -12,34 +12,39 @@ By adding a webhook to a specific URL and selecting an **Event Trigger**, you ca
 
 ## Setting up a webhook
 
-From the Webhooks menu under the Settings section you can create and manage your webhooks.
+To set up a Webhook:
 
-![Webhooks Dashboard](images/webhooksDashboards.png)
+1. Go to the **Settings** section.
+2. Expand the **Headless** folder in the **Settings** tree.
+3. Select **Webhooks**.
 
-Clicking **Create Webhook** will open the creation menu on the right side.
+   ![Webhooks Dashboard](images/webhooksDashboards-1.png)
+4. Click **Create Webhook**.
+5. The **Add webhook** menu opens on the right side.
 
-![Add Webhooks Menu](images/addWebhook.png)
+   ![Add Webhooks Menu](images/addWebhook-1.png)
 
-From here you add the URL that the webhook should call and select the **Event** that should trigger the webhook. Lastly, you can choose a Content Type you wish the webhook to trigger on.
+6. Enter the **URL** that the webhook should call.
+7. Select the **Event** for which the webhook should be triggered.
+8. Choose a **Content Type** you wish the webhook to be triggered on.
 
-{% hint style="info" %}
+    {% hint style="info" %}
+    Selecting the Content Type is the initial step. This field is not mandatory.
+    {% endhint %}
 
-Selecting the event type is the initial step. Also, this field is not mandatory.
+9. Click **Create**.
 
-{% endhint %}
+Once the webhook is created, you can manage it from the list.
 
+![Manage Webhooks](images/manageWebhooks-1.png)
 
-Once the webhook has been created you can manage it from the list. 
-
-![Manage Webhooks](images/manageWebhooks.png)
-
-Should you at some point need to temporarily pause the webhook, you can disable them by selecting **Edit** and uncheck **Enabled**.
+To temporarily pause/disable the webhook, click on **Edit** and toggle the **Enabled** field.
 
 ## Outgoing IPs for webhooks
 
 Webhooks will be fired from either of the two static IPs listed below.
 
-When working with an external service behind a firewall, your service needs to communicate with your Umbraco Cloud project and receive webhook data. This can be done by ensuring that the following IPs are allowed to pass from the firewall
+When working with an external service behind a firewall, your service needs to communicate with your Umbraco Cloud project and receive webhook data. This can be done by ensuring that the following IPs are allowed to pass from the firewall.
 
 ```
 20.86.53.156