Merge pull request #195240 from anthonychu/patch-7

[Container Apps] Clarify idle charges and revisions

Author: laurabren

articles/container-apps/billing.md

@@ -14,7 +14,6 @@ ms.author: cshoe
 Azure Container Apps billing consists of two types of charges:
 
 - **[Resource consumption](#resource-consumption-charges)**: The amount of resources allocated to your container app on a per-second basis, billed in vCPU-seconds and GiB-seconds.
-
 - **[HTTP requests](#request-charges)**: The number of HTTP requests your container app receives.
 
 The following resources are free during each calendar month, per subscription:
@@ -30,31 +29,31 @@ This article describes how to calculate the cost of running your container app.
 
 ## Resource consumption charges
 
-Azure Container Apps runs replicas of your application based on the [scaling rules and replica count limits](scale-app.md) you configure. You're charged for the amount of resources allocated to each replica while it's running.
-
-There are two meters for resource consumption:
+Azure Container Apps runs replicas of your application based on the [scaling rules and replica count limits](scale-app.md) you configure for each revision. You're charged for the amount of resources allocated to each replica while it's running.
 
-- **vCPU-seconds**: The amount of vCPU cores allocated to your container app on a per-second basis.
+There are 2 meters for resource consumption:
 
+- **vCPU-seconds**: The number of vCPU cores allocated to your container app on a per-second basis.
 - **GiB-seconds**: The amount of memory allocated to your container app on a per-second basis.
 
 The first 180,000 vCPU-seconds and 360,000 GiB-seconds in each subscription per calendar month are free.
 
-The rate you pay for resource consumption depends on the state of your container app and replicas. By default, replicas are charged at an *active* rate. However, in certain conditions, a replica can enter an *idle* state. While in an *idle* state, resources are billed at a reduced rate.
+The rate you pay for resource consumption depends on the state of your container app's revisions and replicas. By default, replicas are charged at an *active* rate. However, in certain conditions, a replica can enter an *idle* state. While in an *idle* state, resources are billed at a reduced rate.
 
 ### No replicas are running
 
-When your container app is scaled down to zero replicas, no resource consumption charges are incurred.
+When a revision is scaled to zero replicas, no resource consumption charges are incurred.
 
 ### Minimum number of replicas are running
 
-Idle usage charges are applied when your replicas are running under a specific set of circumstances. The criteria for idle charges include:
+Idle usage charges may apply when a revision is running under a specific set of circumstances. To be eligible for idle charges, a revision must meet the following criteria.
 
-- When your container app<sup>1</sup> is configured with a [minimum replica count](scale-app.md) of at least one.
-- The app is scaled down to the minimum replica count.
+- It is configured with a [minimum replica count](scale-app.md) greater than zero.
+- It is scaled to the minimum replica count.
 
 Usage charges are calculated individually for each replica. A replica is considered idle when *all* of the following conditions are true:
 
+- The replica is running in a revision that is currently eligible for idle charges.
 - All of the containers in the replica have started and are running.
 - The replica isn't processing any HTTP requests.
 - The replica is using less than 0.01 vCPU cores.
@@ -64,13 +63,10 @@ When a replica is idle, resource consumption charges are calculated at the reduc
 
 ### More than the minimum number of replicas are running
 
-When your container app<sup>1</sup> is scaled above the [minimum replica count](scale-app.md), all running replicas are charged for resource consumption at the active rate.
-
-<sup>1</sup> For container apps in multiple revision mode, charges are based on the current replica count in a revision relative to its configured minimum replica count.
+When a revision is scaled above the [minimum replica count](scale-app.md), all of its running replicas are charged for resource consumption at the active rate.
 
 ## Request charges
 
 In addition to resource consumption, Azure Container Apps also charges based on the number of HTTP requests received by your container app.
 
 The first 2 million requests in each subscription per calendar month are free.
-