FInish update to webhook naming

Author: MarkvanMents

content/en/docs/apidocs-mxsdk/apidocs/webhooks-sprints.md

@@ -9,22 +9,24 @@ weight: 75
 ## 1 Introduction
 
 {{% alert color="warning" %}}
-The webhook payloads described in this document are for app Sprints and stories. These webhooks were enabled via **General Settings** > **Webhooks** or via your app. These webhooks have been deprecated. For more information, see the deprecation note in [Webhooks](/developerportal/collaborate/general-settings/#webhooks).
+The webhook payloads described in this document are for app stories and Sprints. These webhooks were enabled via **General Settings** > **Webhooks** or via your app.
+
+The webhooks for stories and Sprints have been deprecated. For more information, see the deprecation note in the [Webhooks](/developerportal/collaborate/general-settings/#webhooks) section of *General Settings*.
 {{% /alert %}}
 
 {{% alert color="info" %}}
-You can now set deployment webhooks for your app. These are described in [Webhooks](/developerportal/deploy/webhooks/).
+You can also set deployment webhooks for your app. These are described in [Webhooks](/developerportal/deploy/webhooks/).
 {{% /alert %}}
 
-Webhooks allow you to build or set up Mendix Platform connectors that subscribe to certain events on the Developer Portal. When one of those events is triggered, Mendix sends an HTTP POST payload to the webhook's configured URL. Webhooks can be used to update an external application to keep it up-to-date with the changes happening in the Developer Portal.
+Webhooks for stories and Sprints allow you to build or set up Mendix Platform connectors that subscribe to certain events on the Developer Portal. When one of those events is triggered, Mendix sends an HTTP POST payload to the webhook's configured URL. Webhooks for stories and Sprints can be used to update an external application to keep it up-to-date with the changes happening in the Developer Portal.
 
 Every POST payload contains the following delivery information as part of the header:
 
 * `MxAPI-Projects-EventCategory` – the types of event subscribed to (for example, Sprints)
 * `MxAPI-Projects-Delivery` – a random UUID
 * `MxAPI-Signature` –  the HMAC hex digest (asymmetric hash using the *HMAC_SHA256* hash algorithm) of the response body, which is calculated using the hash (the hashes secret provided in the webhooks setting using the *SHA-256* hash algorithm with the length as 50)
     * For example, `(gNh407kBD1wkpHfwIrjWcTMjw4rKxIKX0s5b48FYOys=)`
-* `MxAPI-Webhooks-Version` – the version of the webhooks payload (for example, 1)
+* `MxAPI-Webhooks-Version` – the version of the webhooks for stories and Sprints payload (for example, 1)
 * `MxAPI-Webhooks-Version-Expiry` – the expiry date for this version (empty if it is the latest version)
 * `User-Agent` – `Mx-Platform`
 
@@ -36,7 +38,7 @@ The required event category subscription is **Sprints**.
 
 ## 3 Stories
 
-Webhooks event are generated when a [story](/developerportal/collaborate/stories/) is created or updated.
+Webhooks for stories and Sprints event are generated when a [story](/developerportal/collaborate/stories/) is created or updated.
 
 The required event category subscription is **Stories**.
 

content/en/docs/developerportal/deploy/mendix-cloud-deploy/webhooks.md

@@ -25,7 +25,7 @@ The webhooks contain a retry mechanism if an error response is received from the
 {{% alert color="info" %}}
 Webhooks are only available for licensed Mendix apps which are deployed to the Mendix Cloud.
 
-They are set up and work independently of the [webhooks used for Sprints and stories](/developerportal/collaborate/general-settings/#webhooks), which are deprecated.
+They are set up and work independently of the deprecated [webhooks for Sprints and Stories](/developerportal/collaborate/general-settings/#webhooks).
 {{% /alert %}}
 
 ## 2 Configuring a Webhook{#setting-up}

content/en/docs/releasenotes/developer-portal/_index.md

@@ -26,7 +26,7 @@ To see the current status of the Mendix Developer Portal and Control Center, see
 
 #### Deprecations
 
-* We have deprecated **General Settings** > **Webhooks** for app Sprints and stories. For more information, see the deprecation note in [Webhooks](/developerportal/collaborate/general-settings/#webhooks). You can now set webhooks for your app. These are described in [Webhooks](/developerportal/deploy/webhooks/).
+* We have deprecated **General Settings** > **Webhooks** for stories and Sprints. For more information, see the deprecation note in the [Webhooks](/developerportal/collaborate/general-settings/#webhooks) section of *General Settings*. You can now set webhooks for building and deploying your app. These are described in [Webhooks](/developerportal/deploy/webhooks/).
 
 ### March 9th, 2023
 
@@ -963,7 +963,7 @@ In Portfolio Management, you can do the following
 
 #### Webhooks Available
 
-* We have added the ability to create webhooks for your apps. These webhooks can be configured to send information when Sprints change and/or stories change.
+* We have added the ability to create webhooks for stories and Sprints for your apps. These webhooks can be configured to send information when Sprints change and/or stories change.
 
 ### April 5th, 2019