Skip to content

Commit bff03fb

Browse files
committed
Acrolinx fixes
1 parent 45cd5e7 commit bff03fb

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

articles/logic-apps/logic-apps-batch-process-send-receive-messages.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.suite: integration
1717
To send and process messages together in a specific way as groups,
1818
you can create a batching solution that collects messages into a
1919
*batch* until your specified criteria are met for releasing and
20-
and processing the batched messages. Batching can reduce how often
20+
processing the batched messages. Batching can reduce how often
2121
your logic app processes messages. This article shows how to build
2222
a batching solution by creating two logic apps within the same
2323
Azure subscription, Azure region, and following this specific order:
@@ -90,8 +90,8 @@ Select this trigger: **Batch messages**
9090

9191
| Property | Description |
9292
|----------|-------------|
93-
| **Batch Mode** | - **Inline**: For when you define a single release criteria configuration inside the batch trigger <br>- **Integration Account**: For when you define multiple release criteria configurations through an integration account |
94-
| **Batch Name** | The name for your batch, which is "TestBatch" in this example. Applies only to **Inline** batch mode. |
93+
| **Batch Mode** | - **Inline**: For defining release criteria inside the batch trigger <br>- **Integration Account**: For defining multiple release criteria configurations through an integration account |
94+
| **Batch Name** | The name for your batch, which is "TestBatch" in this example, and applies only to **Inline** batch mode |
9595
| **Release Criteria** | Applies only to **Inline** batch mode and specifies the criteria to meet before processing each batch: <p>- **Message count based**: The number of messages to collect in the batch, for example, 10 messages <br>- **Size based**: The maximum batch size in bytes, for example, 100 MB <br>- **Schedule based**: The interval and frequency between batch releases, for example, 10 minutes. You can also specify a start date and time. <br>- **Select all**: Use all the specified criteria. |
9696
|||
9797

@@ -148,8 +148,8 @@ Select this trigger: **Batch messages**
148148
* In the **Body** box, when the dynamic content list appears,
149149
select the **Message Id** field.
150150

151-
A **For each** loop automatically appears around the send
152-
email action because that action accepts an array as input.
151+
The Logic Apps Designer automatically adds a "For each" loop around
152+
the send email action because that action accepts an array as input.
153153
This loop sends an email for each message in the batch.
154154
So, when the batch trigger is set to 10 messages,
155155
you get 10 emails each time the trigger fires.

articles/logic-apps/logic-apps-scenario-edi-send-batch-messages.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ messages go to the trading partner or other destination.
3030
To learn more about the batch trigger and action, see
3131
[Batch process messages](../logic-apps/logic-apps-batch-process-send-receive-messages.md).
3232

33-
In this article, you'll buld a batching solution by
33+
In this article, you'll build a batching solution by
3434
creating two logic apps within the same Azure subscription,
3535
Azure region, and following this specific order:
3636

0 commit comments

Comments
 (0)