Skip to content

Commit 191c3cd

Browse files
committed
apply Craig's review comments.
1 parent ff91679 commit 191c3cd

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/container-apps/revisions.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,11 +32,13 @@ By default, a container app is in *single revision mode*. In this mode, only one
3232

3333
Set the revision mode to *multiple revision mode*, to run multiple revisions of your app simultaneously. While in *multiple revision mode*, new revisions are activated alongside current active revisions.
3434

35-
In *multiple revision mode*, traffic isn't automatically allocated to new revisions for apps with external HTTP ingress. Configure splitting from your container app's **Revision management** page in the Azure portal, using Azure CLI commands, or in an ARM template.
35+
In *multiple revision mode*, traffic isn't automatically allocated to new revisions for apps with external HTTP ingress. Configure traffic splitting from your container app's **Revision management** page in the Azure portal, using Azure CLI commands, or in an ARM template.
3636

3737
## Use cases
3838

39-
Container Apps revisions help you manage the versioning of your container app. You can use revisions to:
39+
Container Apps revisions help you manage the versioning of your container app by creating a new revision each time you make a *revision-scope* change to your app. You can control access to versions of your container app by activating and deactivating revisions and by configuring the external HTTP traffic routed to each active revision.
40+
41+
You can use revisions to:
4042

4143
- Release a new version of your app.
4244
- Quickly revert to an earlier version of your app.

0 commit comments

Comments
 (0)