fix(github-webhook): fix enumeration mistake (#2597)

* fix(github-webhook): fix enumeration mistake

* chore(github-webhook): improve intendation for readibility

* style(formatting): technical review

* pop links back

---------

Co-authored-by: Christina Ausley <[email protected]>

docs/components/connectors/out-of-the-box-connectors/github-webhook.md

@@ -39,13 +39,12 @@ Please refer to the [update guide](/components/connectors/custom-built-connector
 
 6. If you are using the GitHub Webhook Connector with an **Intermediate Catch Event**, fill in the **Correlation key (process)** and **Correlation key (payload)**.
 
-- **Correlation key (process)** is a FEEL expression that defines the correlation key for the subscription. This corresponds to the **Correlation key** property of a regular **Message Intermediate Catch Event**.
-- **Correlation key (payload)** is a FEEL expression used to extract the correlation key from the incoming message. This expression is evaluated in the Connector Runtime and the result is used to correlate the message.
+   - **Correlation key (process)** is a FEEL expression that defines the correlation key for the subscription. This corresponds to the **Correlation key** property of a regular **Message Intermediate Catch Event**.
+   - **Correlation key (payload)** is a FEEL expression used to extract the correlation key from the incoming message. This expression is evaluated in the Connector Runtime and the result is used to correlate the message.
 
-For example, given that your correlation key is defined with `pullRequestId` process variable, and the request body contains `{"pull_request": {"id": 123}}`, your correlation key settings will look like this:
-
-- **Correlation key (process)**: `=pullRequestId`
-- **Correlation key (payload)**: `=request.body.pull_request.id`
+   - For example, given that your correlation key is defined with `pullRequestId` process variable, and the request body contains `{"pull_request": {"id": 123}}`, your correlation key settings will look like this:
+     - **Correlation key (process)**: `=pullRequestId`
+     - **Correlation key (payload)**: `=request.body.pull_request.id`
 
 Learn more about correlation keys in the [messages guide](../../../concepts/messages).
 
@@ -76,10 +75,10 @@ In that case, GitHub Webhook Connector deployments and URLs will not be displaye
 1. Ensure you have administrator rights for the repository where you wish to enable a webhook.
 2. Open a repository in your web browser and navigate to the **Settings** page.
 3. Click **Webhooks > Add webhook**.
-4. Fill the required fields.
-   5.1. **Payload URL** - a URL of your webhook.
-   5.2. **Content type** - choose `application/json`.
-   5.3. **Secret** - is a shared secret between GitHub and your BPMN diagram.
+4. Fill out the required fields:
+   1. **Payload URL** - URL of your webhook.
+   2. **Content type** - Select `application/json`.
+   3. **Secret** - Shared secret between GitHub and your BPMN diagram.
 5. Confirm by clicking **Add webhook**.
 
 Refer to the [GitHub documentation](https://docs.github.com/en/rest/webhooks) for more details.

versioned_docs/version-8.1/components/connectors/out-of-the-box-connectors/github-webhook.md

@@ -20,7 +20,7 @@ Please refer to the [update guide](/guides/update-guide/connectors/060-to-070.md
 3. Fill in all required properties.
 4. Complete your BPMN diagram.
 5. Deploy the diagram to activate the webhook.
-6. Navigate to the **Webhooks** tab in the properties panel to see the webhook URL.
+6. Navigate to the **Webhooks** tab in the properties panel to observe the webhook URL.
 
 ## Make your GitHub Webhook Connector for receiving messages executable
 
@@ -39,13 +39,12 @@ Please refer to the [update guide](/guides/update-guide/connectors/060-to-070.md
 
 6. If you are using the GitHub Webhook Connector with an **Intermediate Catch Event**, fill in the **Correlation key (process)** and **Correlation key (payload)**.
 
-- **Correlation key (process)** is a FEEL expression that defines the correlation key for the subscription. This corresponds to the **Correlation key** property of a regular **Message Intermediate Catch Event**.
-- **Correlation key (payload)** is a FEEL expression used to extract the correlation key from the incoming message. This expression is evaluated in the Connector Runtime and the result is used to correlate the message.
+   - **Correlation key (process)** is a FEEL expression that defines the correlation key for the subscription. This corresponds to the **Correlation key** property of a regular **Message Intermediate Catch Event**.
+   - **Correlation key (payload)** is a FEEL expression used to extract the correlation key from the incoming message. This expression is evaluated in the Connector Runtime and the result is used to correlate the message.
 
-For example, given that your correlation key is defined with `pullRequestId` process variable, and the request body contains `{"pull_request": {"id": 123}}`, your correlation key settings will look like this:
-
-- **Correlation key (process)**: `=pullRequestId`
-- **Correlation key (payload)**: `=request.body.pull_request.id`
+   - For example, given that your correlation key is defined with `pullRequestId` process variable, and the request body contains `{"pull_request": {"id": 123}}`, your correlation key settings will look like this:
+     - **Correlation key (process)**: `=pullRequestId`
+     - **Correlation key (payload)**: `=request.body.pull_request.id`
 
 Learn more about correlation keys in the [messages guide](../../../concepts/messages).
 
@@ -76,10 +75,10 @@ In that case, GitHub Webhook Connector deployments and URLs will not be displaye
 1. Ensure you have administrator rights for the repository where you wish to enable a webhook.
 2. Open a repository in your web browser and navigate to the **Settings** page.
 3. Click **Webhooks > Add webhook**.
-4. Fill the required fields.
-   5.1. **Payload URL** - a URL of your webhook.
-   5.2. **Content type** - choose `application/json`.
-   5.3. **Secret** - is a shared secret between GitHub and your BPMN diagram.
+4. Fill out the required fields:
+   1. **Payload URL** - URL of your webhook.
+   2. **Content type** - Select `application/json`.
+   3. **Secret** - Shared secret between GitHub and your BPMN diagram.
 5. Confirm by clicking **Add webhook**.
 
 Refer to the [GitHub documentation](https://docs.github.com/en/rest/webhooks) for more details.

versioned_docs/version-8.2/components/connectors/out-of-the-box-connectors/github-webhook.md

@@ -20,7 +20,7 @@ Please refer to the [update guide](/guides/update-guide/connectors/060-to-070.md
 3. Fill in all required properties.
 4. Complete your BPMN diagram.
 5. Deploy the diagram to activate the webhook.
-6. Navigate to the **Webhooks** tab in the properties panel to see the webhook URL.
+6. Navigate to the **Webhooks** tab in the properties panel to observe the webhook URL.
 
 ## Make your GitHub Webhook Connector for receiving messages executable
 
@@ -39,13 +39,12 @@ Please refer to the [update guide](/guides/update-guide/connectors/060-to-070.md
 
 6. If you are using the GitHub Webhook Connector with an **Intermediate Catch Event**, fill in the **Correlation key (process)** and **Correlation key (payload)**.
 
-- **Correlation key (process)** is a FEEL expression that defines the correlation key for the subscription. This corresponds to the **Correlation key** property of a regular **Message Intermediate Catch Event**.
-- **Correlation key (payload)** is a FEEL expression used to extract the correlation key from the incoming message. This expression is evaluated in the Connector Runtime and the result is used to correlate the message.
+   - **Correlation key (process)** is a FEEL expression that defines the correlation key for the subscription. This corresponds to the **Correlation key** property of a regular **Message Intermediate Catch Event**.
+   - **Correlation key (payload)** is a FEEL expression used to extract the correlation key from the incoming message. This expression is evaluated in the Connector Runtime and the result is used to correlate the message.
 
-For example, given that your correlation key is defined with `pullRequestId` process variable, and the request body contains `{"pull_request": {"id": 123}}`, your correlation key settings will look like this:
-
-- **Correlation key (process)**: `=pullRequestId`
-- **Correlation key (payload)**: `=request.body.pull_request.id`
+   - For example, given that your correlation key is defined with `pullRequestId` process variable, and the request body contains `{"pull_request": {"id": 123}}`, your correlation key settings will look like this:
+     - **Correlation key (process)**: `=pullRequestId`
+     - **Correlation key (payload)**: `=request.body.pull_request.id`
 
 Learn more about correlation keys in the [messages guide](../../../concepts/messages).
 
@@ -76,10 +75,10 @@ In that case, GitHub Webhook Connector deployments and URLs will not be displaye
 1. Ensure you have administrator rights for the repository where you wish to enable a webhook.
 2. Open a repository in your web browser and navigate to the **Settings** page.
 3. Click **Webhooks > Add webhook**.
-4. Fill the required fields.
-   5.1. **Payload URL** - a URL of your webhook.
-   5.2. **Content type** - choose `application/json`.
-   5.3. **Secret** - is a shared secret between GitHub and your BPMN diagram.
+4. Fill out the required fields:
+   1. **Payload URL** - URL of your webhook.
+   2. **Content type** - Select `application/json`.
+   3. **Secret** - Shared secret between GitHub and your BPMN diagram.
 5. Confirm by clicking **Add webhook**.
 
 Refer to the [GitHub documentation](https://docs.github.com/en/rest/webhooks) for more details.