Skip to content

Commit 96a8962

Browse files
authored
Acrolinx fixes
1 parent 1b970b7 commit 96a8962

File tree

1 file changed

+12
-9
lines changed

1 file changed

+12
-9
lines changed

articles/logic-apps/logic-apps-pricing.md

Lines changed: 12 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@ ms.suite: logic-apps
77
author: kevinlam1
88
ms.author: klam
99
ms.reviewer: estfan, LADocs
10+
manager: carmonm
1011
ms.assetid: f8f528f5-51c5-4006-b571-54ef74532f32
1112
ms.topic: article
1213
ms.date: 10/16/2018
@@ -75,9 +76,11 @@ For example, you can set up a recurrence trigger that runs every three days or o
7576

7677
## Actions
7778

78-
Logic Apps meters built-in actions, such as HTTP calls, Azure Functions, and API Management,
79-
and control flow steps, as native actions, which have their own action types. Actions that
80-
call [connectors](https://docs.microsoft.com/connectors) have the "ApiConnection" type.
79+
Logic Apps meters built-in actions as native actions. For example,
80+
built-in actions include calls over HTTP, calls from Azure Functions
81+
or API Management, and control flow steps such as loops and conditions
82+
- each with their own action type. Actions that call
83+
[connectors](https://docs.microsoft.com/connectors) have the "ApiConnection" type.
8184
These connectors are classified as standard or enterprise connectors,
8285
which are metered based on their respective [pricing][pricing].
8386
Enterprise connectors in *Preview* are charged as standard connectors.
@@ -95,10 +98,10 @@ because they can't create new instances.
9598
> After you disable a logic app, any currently running instances
9699
> might take some time before they completely stop.
97100
98-
Actions that run inside loops are counted per each cycle in the loop.
99-
For example, Logic Apps meters an action in a "for each" loop that
100-
processes a list by multiplying the number of list items by the number
101-
of actions in the loop plus the action that starts the loop.
101+
For actions that run inside loops, Logic Apps counts each action per cycle in the loop.
102+
For example, suppose you have a "for each" loop that processes a list.
103+
Logic Apps meters an action in that loop by multiplying the number of list items
104+
with the number of actions in the loop, and adds the action that starts the loop.
102105
The calculation for a 10-item list is (10 * 1) + 1, which results in 11 action executions.
103106

104107
## Integration Account usage
@@ -111,8 +114,8 @@ where you can explore, develop, and test the
111114
features in Logic Apps at no additional cost. You can have
112115
one integration account per region. Each integration account
113116
can store up to specific [numbers of artifacts](../logic-apps/logic-apps-limits-and-config.md),
114-
such as trading partners, agreements, maps, schemas,
115-
assemblies, certificates, and batch configurations.
117+
which include trading partners, agreements, maps, schemas,
118+
assemblies, certificates, batch configurations, and so on.
116119

117120
Logic Apps also offers basic and standard integration accounts with supported Logic Apps SLA.
118121
You can use basic integration accounts when you just want message handling or act as a small

0 commit comments

Comments
 (0)