Skip to content

Commit 18ccdc8

Browse files
Fix typo in HTTP request trigger name
1 parent 637bf87 commit 18ccdc8

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

articles/logic-apps/logic-apps-content-type.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ In Azure Logic Apps, you can generate user-friendly tokens that represent the pr
6666

6767
The following list describes common workflow operations and the corresponding ways that you can generate tokens for properties in JSON content:
6868

69-
- **Request** trigger named **When a HTTP request is received**
69+
- **Request** trigger named **When an HTTP request is received**
7070

7171
When you work in the designer with the **Request** trigger, you can optionally provide a JSON schema that defines the JSON objects, properties, and the expected data types for each property value. If you don't have a JSON schema, you can provide an example payload to generate a JSON schema that you can use.
7272

@@ -80,7 +80,7 @@ The following list describes common workflow operations and the corresponding wa
8080

8181
1. In the **Enter or paste a sample JSON payload** box, enter a sample payload, then select **Done**.
8282

83-
:::image type="content" source="./media/logic-apps-content-type/request-trigger.png" alt-text="Screenshot shows the Request trigger named When a HTTP request is received plus a sample JSON payload." lightbox="./media/logic-apps-content-type/request-trigger.png":::
83+
:::image type="content" source="./media/logic-apps-content-type/request-trigger.png" alt-text="Screenshot shows the Request trigger named When an HTTP request is received plus a sample JSON payload." lightbox="./media/logic-apps-content-type/request-trigger.png":::
8484

8585
The generated schema now appears in your trigger.
8686

0 commit comments

Comments
 (0)