Merge pull request #281691 from Akhilesh-microsoft/ACA/Container_app_up

[ACA: Containerapp-up]: Verified the article for links and freshness, reviewed the content, verified all the editorial parameters. Article seems good. Updated ms.date

Author: prmerger-automator[bot]

articles/container-apps/containerapp-up.md

@@ -8,7 +8,7 @@ ms.custom:
   - devx-track-azurecli
   - ignite-2023
 ms.topic: how-to
-ms.date: 11/08/2022
+ms.date: 07/24/2024
 ms.author: cshoe
 ---
 
@@ -138,7 +138,7 @@ Run the following command to deploy a container app from local source code:
 
 When the Dockerfile includes the EXPOSE instruction, the `up` command configures the container app's ingress and target port using the information in the Dockerfile. 
 
-If you've configured ingress through your Dockerfile or your app doesn't require ingress, you can omit the `ingress` option.
+If you configure ingress through your Dockerfile or your app doesn't require ingress, you can omit the `ingress` option.
 
 The output of the command includes the URL for the container app.
 
@@ -184,7 +184,7 @@ az containerapp up \
   --ingress external 
 ```
 
-If you've configured ingress through your Dockerfile or your app doesn't require ingress, you can omit the `ingress` option.
+If you configure ingress through your Dockerfile or your app doesn't require ingress, you can omit the `ingress` option.
 
 Because the `up` command creates a GitHub Actions workflow, rerunning it to deploy changes to your app's image has the unwanted effect of creating multiple workflows. Instead, push changes to your GitHub repository, and the GitHub workflow automatically builds and deploys your app. To change the workflow, edit the workflow file in GitHub.