Skip to content

Commit a86b24e

Browse files
Merge pull request #288323 from Akhilesh-microsoft/ACA/get_started_existing_container_image_portal
[ACA: get-started-existing-container-image-portal]: Verified the article, reviewed the content, and fixed all editorial issues. Updated the latest content and ms.date w.r.t freshness pass.
2 parents 4336ba2 + 029641a commit a86b24e

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/container-apps/get-started-existing-container-image-portal.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: container-apps
55
author: craigshoemaker
66
ms.service: azure-container-apps
77
ms.topic: quickstart
8-
ms.date: 12/13/2021
8+
ms.date: 10/14/2024
99
ms.author: cshoe
1010
zone_pivot_groups: container-apps-registry-types
1111
---
@@ -45,7 +45,7 @@ In the *Basics* tab, do the following actions.
4545
|---|---|
4646
| Subscription | Select your Azure subscription. |
4747
| Resource group | Select **Create new** and enter **my-container-apps**. |
48-
| Container app name | Enter **my-container-app**. |
48+
| Container app name | Enter **my-container-app**. |
4949

5050
#### Create an environment
5151

@@ -114,17 +114,17 @@ If you enabled ingress, configure the following settings:
114114

115115
Next, the settings in the Container App are verified. If no errors are found, the *Create* button is enabled.
116116

117-
If there are errors, any tab containing errors is marked with a red dot. Navigate to the appropriate tab. Fields containing an error will be highlighted in red. Once all errors are fixed, select **Review and create** again.
117+
If there are errors, any tab containing errors is marked with a red dot. Navigate to the appropriate tab. Fields containing an error is highlighted in red. Once all errors are fixed, select **Review and create** again.
118118

119119
1. Select **Create**.
120120

121-
A page with the message *Deployment is in progress* is displayed. Once the deployment is successfully completed, you'll see the message: *Your deployment is complete*.
121+
A page with the message *Deployment is in progress* is displayed. Once the deployment is successfully completed, you see the message: *Your deployment is complete*.
122122

123123
### Verify deployment
124124

125-
You can verify your deployment is successful by querying the Log Analytics workspace. You may need to wait a 5 to 10 minutes for the analytics to arrive for the first time before you are able to query the logs.
125+
You can verify your deployment is successful by querying the Log Analytics workspace. You might need to wait a 5 to 10 minutes for the analytics to arrive for the first time before you're able to query the logs.
126126

127-
After about 5 to 10 minutes has passed after creating the container app, use the following steps to view logged messages.
127+
After 5 to 10 minutes of creating the container app, follow these steps to view logged messages:
128128

129129
1. Select **Go to resource** to view your new container app.
130130
1. Select **Logs** under the *Monitoring* header.
@@ -146,7 +146,7 @@ If you're not going to continue to use this application, you can delete the Azur
146146
1. Select the **Delete resource group** button at the top of the resource group *Overview*.
147147
1. Enter the resource group name **my-container-apps** in the *Are you sure you want to delete "my-container-apps"* confirmation dialog.
148148
1. Select **Delete**.
149-
The process to delete the resource group may take a few minutes to complete.
149+
The process to delete the resource group might take a few minutes to complete.
150150
151151
> [!TIP]
152152
> Having issues? Let us know on GitHub by opening an issue in the [Azure Container Apps repo](https://github.com/microsoft/azure-container-apps).

0 commit comments

Comments
 (0)