Merge pull request #230481 from craigshoemaker/aca/disclaimers

[Container Apps] Add platform expectation details

Author: prmerger-automator[bot]

articles/container-apps/application-lifecycle-management.md

@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: container-apps
 ms.topic: conceptual
-ms.date: 10/25/2022
+ms.date: 3/13/2023
 ms.author: cshoe
 ms.custom: ignite-fall-2021, event-tier1-build-2022
 ---
@@ -16,7 +16,7 @@ The Azure Container Apps application lifecycle revolves around [revisions](revis
 
 When you deploy a container app, the first revision is automatically created. [More revisions are created](revisions.md) as [containers](containers.md) change, or any adjustments are made to the `template` section of the configuration.
 
-A container app flows through four phases: deployment, update, deactivation, and shutdown.
+A container app flows through four phases: deployment, update, deactivation, and shut down.
 
 ## Deployment
 
@@ -32,12 +32,12 @@ As a container app is updated with a [revision scope-change](revisions.md#revisi
 
 ### Zero downtime deployment
 
-In single revision mode, Container Apps automatically ensures your app does not experience downtime when creating a new revision. The existing active revision is not deactivated until the new revision is ready. If ingress is enabled, the existing revision will continue to receive 100% of the traffic until the new revision is ready.
+In single revision mode, Container Apps automatically ensures your app doesn't experience downtime when creating a new revision. The existing active revision isn't deactivated until the new revision is ready. If ingress is enabled, the existing revision continues to receive 100% of the traffic until the new revision is ready.
 
 > [!NOTE]
 > A new revision is considered ready when one of its replicas starts and becomes ready. A replica is ready when all of its containers start and pass their [startup and readiness probes](./health-probes.md).
 
-In multiple revision mode, you control when revisions are activated or deactivated and which revisions receive ingress traffic. If a [traffic splitting rule](./revisions-manage.md#traffic-splitting) is configured with `latestRevision` set to `true`, traffic does not switch to the latest revision until it is ready.
+In multiple revision mode, you control when revisions are activated or deactivated and which revisions receive ingress traffic. If a [traffic splitting rule](./revisions-manage.md#traffic-splitting) is configured with `latestRevision` set to `true`, traffic doesn't switch to the latest revision until it's ready.
 
 ## Deactivate
 
@@ -55,7 +55,9 @@ The containers are shut down in the following situations:
 
 When a shutdown is initiated, the container host sends a [SIGTERM message](https://wikipedia.org/wiki/Signal_(IPC)) to your container. The code implemented in the container can respond to this operating system-level message to handle termination.
 
-If your application does not respond within 30 seconds to the `SIGTERM` message, then [SIGKILL](https://wikipedia.org/wiki/Signal_(IPC)) terminates your container.
+If your application doesn't respond within 30 seconds to the `SIGTERM` message, then [SIGKILL](https://wikipedia.org/wiki/Signal_(IPC)) terminates your container.
+
+Additionally, make sure your application can gracefully handle shutdowns. Containers restart regularly, so don't expect state to persist inside a container. Instead, use external caches for expensive in-memory cache requirements.
 
 ## Next steps
 

articles/container-apps/environment.md

@@ -5,14 +5,16 @@ services: container-apps
 author: craigshoemaker
 ms.service: container-apps
 ms.topic:  conceptual
-ms.date: 10/18/2022
+ms.date: 03/13/2023
 ms.author: cshoe
 ms.custom: ignite-fall-2021, event-tier1-build-2022
 ---
 
 # Azure Container Apps environments
 
-Individual container apps are deployed to a single Container Apps environment, which acts as a secure boundary around groups of container apps. Container Apps in the same environment are deployed in the same virtual network and write logs to the same Log Analytics workspace. You may provide an [existing virtual network](vnet-custom.md) when you create an environment.
+A Container Apps environment is a secure boundary around groups of container apps that share the same virtual network and write logs to the same logging destination.
+
+Container Apps environments are fully managed where Azure handles OS upgrades, scale operations, failover procedures, and resource balancing.
 
 :::image type="content" source="media/environments/azure-container-apps-environments.png" alt-text="Azure Container Apps environments.":::
 
@@ -29,13 +31,15 @@ Reasons to deploy container apps to different environments include situations wh
 - Two applications never share the same compute resources
 - Two Dapr applications can't communicate via the Dapr service invocation API
 
+Also, you may provide an [existing virtual network](vnet-custom.md) when you create an environment.
+
 ## Logs
 
 Settings relevant to the Azure Container Apps environment API resource.
 
 | Property | Description |
 |---|---|
-| `properties.appLogsConfiguration` | Used for configuring Log Analytics workspace where logs for all apps in the environment will be published |
+| `properties.appLogsConfiguration` | Used for configuring the Log Analytics workspace where logs for all apps in the environment are published. |
 | `properties.containerAppsConfiguration.daprAIInstrumentationKey` | App Insights instrumentation key provided to Dapr for tracing |
 
 ## Billing

articles/container-apps/overview.md

@@ -5,14 +5,14 @@ services: container-apps
 author: craigshoemaker
 ms.service: container-apps
 ms.topic: overview
-ms.date: 06/23/2022
+ms.date: 03/13/2023
 ms.author: cshoe
 ms.custom: ignite-fall-2021, event-tier1-build-2022, ignite-2022
 ---
 
 # Azure Container Apps overview
 
-Azure Container Apps enables you to run microservices and containerized applications on a serverless platform. Common uses of Azure Container Apps include:
+Azure Container Apps is a fully managed environment that enables you to run microservices and containerized applications on a serverless platform. Common uses of Azure Container Apps include:
 
 - Deploying API endpoints
 - Hosting background processing applications