Add minor changes

Author: cdpark

articles/connectors/connectors-native-webhook.md

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 06/20/2025
+ms.date: 06/26/2025
 ---
 
 # Subscribe and wait for events to run workflows using HTTP webhooks in Azure Logic Apps
@@ -75,7 +75,7 @@ This built-in trigger calls the subscribe endpoint on the target service and reg
 
 1. On the workflow sidebar menu, under **Tools**, select the designer to open the workflow.
 
-1. Add the trigger named **HTTP Webhook** to your workflow by following the [general steps to add a trigger](../logic-apps/add-trigger-action-workflow.md?tabs=standard#add-trigger).
+1. Add the **HTTP Webhook** trigger to your workflow by following the [general steps to add a trigger](../logic-apps/add-trigger-action-workflow.md?tabs=standard#add-trigger).
 
    This example renames the trigger to **HTTP Webhook trigger** so that the step has a more descriptive name. Also, the example later adds an HTTP Webhook action, and both names must be unique.
 
@@ -99,7 +99,7 @@ This built-in trigger calls the subscribe endpoint on the target service and reg
 
    :::image type="content" source="media/connectors-native-webhook/webhook-trigger-parameters-standard.png" alt-text="Screenshot shows Standard workflow with HTTP Webhook trigger parameters." lightbox="media/connectors-native-webhook/webhook-trigger-parameters-standard.png":::
 
-   If you need to use authentication, you can add the **Subscribe Authentication** and **Unsubscribe Authentication** properties. For more information about authentication types available for HTTP Webhook, see [Add authentication to outbound calls](../logic-apps/logic-apps-securing-a-logic-app.md#add-authentication-outbound).
+   If you need to use authentication, you can add the **Subscribe Authentication** and **Unsubscribe Authentication** properties. For more information about authentication types available for **HTTP Webhook**, see [Add authentication to outbound calls](../logic-apps/logic-apps-securing-a-logic-app.md#add-authentication-outbound).
 
 1. Continue building your workflow with actions that run when the trigger fires.
 
@@ -111,7 +111,7 @@ This built-in trigger calls the subscribe endpoint on the target service and reg
 
 1. On the sidebar menu, under **Development Tools**, select the designer to open the blank workflow.
 
-1. Add the trigger named **HTTP Webhook** to your workflow by following the [general steps to add a trigger](../logic-apps/add-trigger-action-workflow.md?tabs=consumption#add-trigger).
+1. Add the **HTTP Webhook** trigger to your workflow by following the [general steps to add a trigger](../logic-apps/add-trigger-action-workflow.md?tabs=consumption#add-trigger).
 
    This example renames the trigger to **HTTP Webhook trigger** so that the step has a more descriptive name. Also, the example later adds an HTTP Webhook action, and both names must be unique.
 
@@ -132,7 +132,7 @@ This built-in trigger calls the subscribe endpoint on the target service and reg
 
    :::image type="content" source="media/connectors-native-webhook/webhook-trigger-add-properties-consumption.png" alt-text="Screenshot shows Consumption workflow with HTTP Webhook trigger and more properties." lightbox="media/connectors-native-webhook/webhook-trigger-add-properties-consumption.png":::
 
-   For example, if you need to use authentication, you can add the **Subscribe Authentication** and **Unsubscribe Authentication** properties. For more information about authentication types available for HTTP Webhook, see [Add authentication to outbound calls](../logic-apps/logic-apps-securing-a-logic-app.md#add-authentication-outbound).
+   For example, if you need to use authentication, you can add the **Subscribe Authentication** and **Unsubscribe Authentication** properties. For more information about authentication types available for **HTTP Webhook**, see [Add authentication to outbound calls](../logic-apps/logic-apps-securing-a-logic-app.md#add-authentication-outbound).
 
 1. Continue building your workflow with actions that run when the trigger fires.
 
@@ -156,11 +156,11 @@ This built-in action calls the subscribe endpoint on the target service and regi
 
    This example uses the **HTTP Webhook** trigger as the first step.
 
-1. Add the action named **HTTP Webhook** to your workflow by following the [general steps to add a action](../logic-apps/add-trigger-action-workflow.md?tabs=standard#add-action).
+1. Add the **HTTP Webhook** action to your workflow by following the [general steps to add a action](../logic-apps/add-trigger-action-workflow.md?tabs=standard#add-action).
 
    This example renames the action to **HTTP Webhook action** so that the step has a more descriptive name.
 
-1. Provide the values for the HTTP Webhook action parameters, which are similar to the [HTTP Webhook trigger parameters](../logic-apps/logic-apps-workflow-actions-triggers.md#http-webhook-trigger), that you want to use for the subscribe and unsubscribe calls.
+1. Provide the values for the **HTTP Webhook** action parameters, which are similar to the [HTTP Webhook trigger parameters](../logic-apps/logic-apps-workflow-actions-triggers.md#http-webhook-trigger), that you want to use for the subscribe and unsubscribe calls.
 
    | Property | Required | Description |
    |----------|----------|-------------|
@@ -182,7 +182,7 @@ This built-in action calls the subscribe endpoint on the target service and regi
 
 1. To add other action properties, open the **Advanced parameters** list.
 
-   For example, if you need to use authentication, you can add the **Subscribe Authentication** and **Unsubscribe Authentication** properties. For more information about authentication types available for HTTP Webhook, see [Add authentication to outbound calls](../logic-apps/logic-apps-securing-a-logic-app.md#add-authentication-outbound).
+   For example, if you need to use authentication, you can add the **Subscribe Authentication** and **Unsubscribe Authentication** properties. For more information about authentication types available for **HTTP Webhook**, see [Add authentication to outbound calls](../logic-apps/logic-apps-securing-a-logic-app.md#add-authentication-outbound).
 
 1. When you're done, save your workflow. On the designer toolbar, select **Save**.
 
@@ -192,11 +192,11 @@ This built-in action calls the subscribe endpoint on the target service and regi
 
    This example uses the **HTTP Webhook** trigger as the first step.
 
-1. Add the action named **HTTP Webhook** to your workflow by following the [general steps to add an action](../logic-apps/add-trigger-action-workflow.md?tabs=consumption#add-action).
+1. Add the **HTTP Webhook** action to your workflow by following the [general steps to add an action](../logic-apps/add-trigger-action-workflow.md?tabs=consumption#add-action).
 
    This example renames the action to **HTTP Webhook action** so that the step has a more descriptive name.
 
-1. Provide the values for the HTTP Webhook action parameters, which are similar to the [HTTP Webhook trigger parameters](../logic-apps/logic-apps-workflow-actions-triggers.md#http-webhook-trigger), that you want to use for the subscribe and unsubscribe calls.
+1. Provide the values for the **HTTP Webhook** action parameters, which are similar to the [HTTP Webhook trigger parameters](../logic-apps/logic-apps-workflow-actions-triggers.md#http-webhook-trigger), that you want to use for the subscribe and unsubscribe calls.
 
    | Property | Required | Description |
    |----------|----------|-------------|
@@ -213,7 +213,7 @@ This built-in action calls the subscribe endpoint on the target service and regi
 
    :::image type="content" source="media/connectors-native-webhook/webhook-action-add-properties-consumption.png" alt-text="Screenshot shows Consumption workflow with HTTP Webhook action and more properties." lightbox="media/connectors-native-webhook/webhook-action-add-properties-consumption.png":::
 
-   For example, if you need to use authentication, you can add the **Subscribe Authentication** and **Unsubscribe Authentication** properties. For more information about authentication types available for HTTP Webhook, see [Add authentication to outbound calls](../logic-apps/logic-apps-securing-a-logic-app.md#add-authentication-outbound).
+   For example, if you need to use authentication, you can add the **Subscribe Authentication** and **Unsubscribe Authentication** properties. For more information about authentication types available for **HTTP Webhook**, see [Add authentication to outbound calls](../logic-apps/logic-apps-securing-a-logic-app.md#add-authentication-outbound).
 
 1. When you're done, save your workflow. On the designer toolbar, select **Save**.
 
@@ -223,7 +223,7 @@ When this action runs, your workflow calls the subscribe endpoint on the target
 
 ## Trigger and action outputs
 
-Here is more information about the outputs from an HTTP Webhook trigger or action, which returns this information:
+Here is more information about the outputs from an **HTTP Webhook** trigger or action, which returns this information:
 
 | Property name | Type | Description |
 |---------------|------|-------------|
@@ -249,7 +249,7 @@ To use the secondary key instead for callback URL generation, follow these steps
 
 1. From the workflow designer, switch to code view.
 
-1. In the **HttpWebhook** trigger definition. find the `accessKeyType` parameter.
+1. In the `HttpWebhook` trigger definition, find the `accessKeyType` parameter.
 
 1. Specify the word `Secondary` as the parameter value.
 

articles/logic-apps/logic-apps-diagnosing-failures.md

@@ -6,7 +6,7 @@ ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
 ms.custom: engagement-fy23
-ms.date: 06/20/2025
+ms.date: 06/26/2025
 ---
 
 # Troubleshoot and diagnose workflow failures in Azure Logic Apps
@@ -23,7 +23,7 @@ Each workflow run starts with a trigger, which either fires on a schedule or wai
 
 ### [Consumption](#tab/consumption)
 
-1. To check the trigger's status in your Consumption logic app, [review the trigger history](monitor-logic-apps.md#review-trigger-history). To view more information about the trigger attempt, select that trigger event, for example:
+1. To check the trigger's status in your Consumption logic app, review the [workflow's trigger history](monitor-logic-apps.md#review-trigger-history). To view more information about the trigger attempt, select that trigger event, for example:
 
    :::image type="content" source="media/logic-apps-diagnosing-failures/logic-app-trigger-history-consumption.png" alt-text="Screenshot showing Azure portal with Consumption logic app workflow trigger history." lightbox="media/logic-apps-diagnosing-failures/logic-app-trigger-history-consumption.png":::
 
@@ -48,7 +48,7 @@ Each workflow run starts with a trigger, which either fires on a schedule or wai
 
 ### [Standard](#tab/standard)
 
-1. To check the trigger's status in your Standard logic app, [review the trigger history](monitor-logic-apps.md#review-trigger-history). To view more information about the trigger attempt, select that trigger event, for example:
+1. To check the trigger's status in your Standard logic app, review the [workflow's trigger history](monitor-logic-apps.md#review-trigger-history). To view more information about the trigger attempt, select that trigger event, for example:
 
    :::image type="content" source="media/logic-apps-diagnosing-failures/logic-app-trigger-history-standard.png" alt-text="Screenshot showing Azure portal with Standard logic app workflow trigger history." lightbox="media/logic-apps-diagnosing-failures/logic-app-trigger-history-standard.png":::
 
@@ -81,7 +81,7 @@ Each time that the trigger fires, Azure Logic Apps creates a workflow instance a
 
 ### [Consumption](#tab/consumption)
 
-1. To check the workflow's run status in your Consumption logic app, [review the runs history](monitor-logic-apps.md#review-runs-history). To view more information about a failed run, including all the steps in that run in their status, select the failed run.
+1. To check the workflow's run status in your Consumption logic app, review the [workflow's run history](monitor-logic-apps.md#review-runs-history). To view more information about a failed run, including all the steps in that run in their status, select the failed run.
 
    :::image type="content" source="media/logic-apps-diagnosing-failures/logic-app-runs-history-consumption.png" alt-text="Screenshot showing Azure portal with Consumption logic app workflow runs and a failed run selected." lightbox="media/logic-apps-diagnosing-failures/logic-app-runs-history-consumption.png":::
 
@@ -99,7 +99,7 @@ Each time that the trigger fires, Azure Logic Apps creates a workflow instance a
 
 ### [Standard](#tab/standard)
 
-1. To check the workflow's run status in your Standard logic app, [review the runs history](monitor-logic-apps.md#review-runs-history). To view more information about a failed run, including all the steps in that run in their status, select the failed run.
+1. To check the workflow's run status in your Standard logic app, review the [workflow's run history](monitor-logic-apps.md#review-runs-history). To view more information about a failed run, including all the steps in that run in their status, select the failed run.
 
    :::image type="content" source="media/logic-apps-diagnosing-failures/logic-app-runs-history-standard.png" alt-text="Screenshot showing Azure portal with Standard logic app workflow runs and a failed run selected." lightbox="media/logic-apps-diagnosing-failures/logic-app-runs-history-standard.png":::
 
@@ -123,13 +123,13 @@ To help with debugging, you can add diagnostic steps to a logic app workflow, al
 
 1. In a browser, go to the [Webhook Tester](https://webhook.site/) site, and copy the generated unique URL.
 
-1. In your logic app, add an HTTP POST action with the body content that you want to test, for example, an expression or another step output.
+1. In your logic app, add an **HTTP POST** action with the body content that you want to test, for example, an expression or another step output.
 
-1. Paste your URL from Webhook Tester into the HTTP POST action.
+1. Paste your URL from Webhook Tester into the **HTTP POST** action.
 
 1. To review how Azure Logic Apps generates and forms a request, run the logic app workflow. You can then revisit the Webhook Tester site for more information.
 
-## Frequently asked questions (FAQ)
+## Frequently asked questions
 
 ### Why is the workflow run duration longer than the sum of all the workflow action durations?
 
@@ -213,7 +213,7 @@ The following list includes possible causes for these errors and steps to help t
 
      * If the storage service has a [private endpoint](../private-link/private-endpoint-overview.md), the service resolves to the respective network interface controller (NIC) private IP addresses.
 
-   1. If the previous domain name server (DNS) queries resolve successfully, run the `psping` or `tcpping` commands to check connectivity to the storage account over port 443:
+  1. If the previous domain name server (DNS) queries resolve successfully, run the `psping` or `tcpping` commands to check connectivity to the storage account over port 443:
 
       Syntax: `psping [StorageaccountHostName] [Port] [OptionalDNSServer]`
 
@@ -225,13 +225,13 @@ The following list includes possible causes for these errors and steps to help t
 
       Queue: `psping {StorageaccountName}.queue.core.windows.net:443`
 
-   1. If each storage service is resolvable from your Azure virtual machine, find the DNS that's used by the virtual machine for resolution. 
+  1. If each storage service is resolvable from your Azure virtual machine, find the DNS that's used by the virtual machine for resolution. 
 
       1. Set your logic app's **WEBSITE_DNS_SERVER** app setting to the DNS, and confirm that the DNS works successfully.
 
       1. Confirm that virtual network integration is set up correctly with appropriate virtual network and subnet in your Standard logic app.
 
-   1. If you use [private Azure DNS zones](../dns/private-dns-privatednszone.md) for your storage account's private endpoint services, check that a [virtual network link](../dns/private-dns-virtual-network-links.md) was created to your logic app's integrated virtual network.
+  1. If you use [private Azure DNS zones](../dns/private-dns-privatednszone.md) for your storage account's private endpoint services, check that a [virtual network link](../dns/private-dns-virtual-network-links.md) was created to your logic app's integrated virtual network.
 
 For more information, see [Deploy Standard logic app to a storage account behind a firewall using service or private endpoints](https://techcommunity.microsoft.com/t5/integrations-on-azure-blog/deploying-standard-logic-app-to-storage-account-behind-firewall/ba-p/2626286).