Merge pull request #214049 from craigshoemaker/aca/sofias-feedback

[Container Apps] Update based on PM review

Author: Court72

articles/container-apps/TOC.yml

@@ -9,32 +9,29 @@
 - name: Quickstarts
   expanded: true
   items: 
-    - name: Deploy your first container app
-      expanded: true
-      items:
-      - name: With a sample container image
-        expanded: true
-        items:
-        - name: Azure portal
-          href: quickstart-portal.md
-        - name: Command line
-          href: get-started.md
-      - name: With an existing container image
-        expanded: true
-        items:
-        - name: Azure portal
-          href: get-started-existing-container-image-portal.md
-        - name: Command line
-          href: get-started-existing-container-image.md
-      - name: With code on your local machine
-        expanded: true
-        items:
-        - name: Command line
-          href: quickstart-code-to-cloud.md
-        - name: Visual Studio
-          href: deploy-visual-studio.md
-        - name: Visual Studio Code
-          href: deploy-visual-studio-code.md
+  - name: With a sample container image
+    expanded: true
+    items:
+    - name: Azure portal
+      href: quickstart-portal.md
+    - name: Command line
+      href: get-started.md
+  - name: With an existing container image
+    expanded: true
+    items:
+    - name: Azure portal
+      href: get-started-existing-container-image-portal.md
+    - name: Command line
+      href: get-started-existing-container-image.md
+  - name: With code on your local machine
+    expanded: true
+    items:
+    - name: Command line
+      href: quickstart-code-to-cloud.md
+    - name: Visual Studio
+      href: deploy-visual-studio.md
+    - name: Visual Studio Code
+      href: deploy-visual-studio-code.md
 - name: Concepts
   items:
     - name: Environment

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

@@ -155,4 +155,4 @@ If you're not going to continue to use this application, you can delete the Azur
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Environments in Azure Container Apps](environment.md)
+> [Communication between microservices](communicate-between-microservices.md)

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

@@ -252,4 +252,4 @@ Remove-AzResourceGroup -Name $ResourceGroupName -Force
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Environments in Azure Container Apps](environment.md)
+> [Communication between microservices](communicate-between-microservices.md)

articles/container-apps/get-started.md

@@ -172,4 +172,4 @@ Remove-AzResourceGroup -Name $ResourceGroupName -Force
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Environments in Azure Container Apps](environment.md)
+> [Communication between microservices](communicate-between-microservices.md)

articles/container-apps/microservices-dapr.md

@@ -18,13 +18,14 @@ ms.devlang: azurecli
 You learn how to:
 
 > [!div class="checklist"]
-> - Create a Container Apps environment to host your container apps
-> - Create an Azure Blob Storage account
-> - Create a Dapr state store component for the Azure Blob storage
-> - Deploy two container apps: one that produces messages, and one that consumes messages and persists them in the state store
-> - Verify the solution is up and running
+> * Create a Container Apps environment for your container apps
+> * Create an Azure Blob Storage state store for the container app
+> * Deploy two apps that produce and consume messages and persist them in the state store
+> * Verify the interaction between the two microservices.
 
-In this tutorial, you deploy the Dapr [Hello World](https://github.com/dapr/quickstarts/tree/master/tutorials/hello-world) quickstart.
+With Azure Container Apps, you get a [fully managed version of the Dapr APIs](./dapr-overview.md) when building microservices. When you use Dapr in Azure Container Apps, you can enable sidecars to run next to your microservices that provide a rich set of capabilities. Available Dapr APIs include [Service to Service calls](https://docs.dapr.io/developing-applications/building-blocks/service-invocation/), [Pub/Sub](https://docs.dapr.io/developing-applications/building-blocks/pubsub/), [Event Bindings](https://docs.dapr.io/developing-applications/building-blocks/bindings/), [State Stores](https://docs.dapr.io/developing-applications/building-blocks/state-management/), and [Actors](https://docs.dapr.io/developing-applications/building-blocks/actors/).
+
+In this tutorial, you deploy the same applications from the Dapr [Hello World](https://github.com/dapr/quickstarts/tree/master/tutorials/hello-kubernetes) quickstart. 
 
 The application consists of:
 
@@ -219,7 +220,7 @@ There are multiple ways to authenticate to external resources via Dapr. This exa
 
 # [Bash](#tab/bash)
 
-Create a config file named **statestore.yaml** with the properties that you sourced from the previous steps. This file helps enable your Dapr app to access your state store. Since the application is authenticating directly via Managed Identity, there's no need to include the storage account key directly within the component. The following example shows how your **statestore.yaml** file should look when configured for your Azure Blob Storage account:
+Open a text editor and create a config file named *statestore.yaml* with the properties that you sourced from the previous steps. This file helps enable your Dapr app to access your state store. The following example shows how your *statestore.yaml* file should look when configured for your Azure Blob Storage account:
 
 ```yaml
 # statestore.yaml for Azure Blob storage component

articles/container-apps/quickstart-portal.md

@@ -22,9 +22,6 @@ An Azure account with an active subscription is required. If you don't already h
 
 ## Setup
 
-> [!NOTE]
-> An Azure Container Apps environment can be deployed as a zone redundant resource in regions where support is available. This is a deployment-time only configuration option.
-
 <!-- Create -->
 [!INCLUDE [container-apps-create-portal-steps.md](../../includes/container-apps-create-portal-steps.md)]
 
@@ -55,4 +52,4 @@ If you're not going to continue to use this application, you can delete the Azur
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Environments in Azure Container Apps](environment.md)
+> [Communication between microservices](communicate-between-microservices.md)

includes/container-apps-create-portal-steps.md

@@ -36,7 +36,7 @@ Next, create an environment for your container app.
 
     | Setting | Value |
     |--|--|
-    | Region | Select **Canada Central**. |
+    | Region | Select **Central US**. |
 
 1. In the *Create Container Apps environment* field, select the **Create new** link.
 1. In the *Create Container Apps Environment* page on the *Basics* tab, enter the following values:
@@ -53,6 +53,6 @@ Next, create an environment for your container app.
     |--|--|
     | Name | Enter **my-container-apps-logs**. |
 
-    The *Location* field is pre-filled with *Canada Central* for you.
+    The *Location* field is pre-filled with *Central US* for you.
 
 1. Select **OK**.