Merge pull request #300182 from craigshoemaker/aca/structure-updates

[Container Apps] Updates: Refine structure language

Author: prmerger-automator[bot]

articles/azure-functions/functions-container-apps-hosting.md

@@ -19,7 +19,7 @@ For a general overview of container hosting options for Azure Functions, see [Li
 
 ## Hosting and workload profiles
 
-There are two primary hosting plans for Container Apps, a serverless [Consumption plan](../container-apps/plans.md#consumption) and a [Dedicated plan](../container-apps/plans.md#dedicated), which uses workload profiles to better control your deployment resources. A workload profile determines the amount of compute and memory resources available to container apps deployed in an environment. These profiles are configured to fit the different needs of your applications. 
+There are two primary plans for Container Apps: a serverless [Consumption plan](../container-apps/plans.md#consumption) and a [Dedicated plan](../container-apps/plans.md#dedicated). Both can be used in Workload profiles environment types, with workload profiles determining the compute and memory resources available to your apps. A workload profile determines the amount of compute and memory resources available to container apps deployed in an environment. These profiles are configured to fit the different needs of your applications. 
 
 The Consumption workload profile is the default profile added to every Workload profiles environment type. You can add Dedicated workload profiles to your environment as you create an environment or after it's created. To learn more about workload profiles, see [Workload profiles in Azure Container Apps](../container-apps/workload-profiles-overview.md).
 

articles/container-apps/billing.md

@@ -14,7 +14,7 @@ ms.author: cshoe
 
 # Billing in Azure Container Apps
 
-Billing in Azure Container Apps is based on your [plan type](plans.md).
+Billing in Azure Container Apps is based on your [plan type](plans.md) (Consumption or Dedicated), which is determined by your environment type you select.
 
 | Plan type | Description |
 |--|--|

articles/container-apps/structure.md

@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: conceptual
-ms.date: 02/05/2025
+ms.date: 05/21/2025
 ms.author: cshoe
 ---
 
@@ -39,7 +39,7 @@ To better understand these relationships, start by considering the differences b
 
 ## Workload profiles
 
-Each *Workload profiles (v2)* environment automatically comes with a consumption profile. The consumption profile allows you to run applications where you only want to pay for usage. Ultimately, you decide whether or not to use the consumption profile since you only incur costs as when apps are running in the consumption workload profile.
+Each *Workload profiles (v2)* environment automatically comes with a consumption profile. The consumption profile allows you to run applications where you only want to pay for usage. Ultimately, you decide whether or not to use the consumption profile since you only incur costs when apps are running in the consumption workload profile.
 
 By default, every *v2* environment only comes with a consumption workload profile. Depending on the needs of your app, you can choose to add any other specialized workload profiles that are best tailored for your application's needs.