edits from my review

Author: cebundy

articles/container-apps/alerts.md

@@ -6,7 +6,7 @@ author: cebundy
 ms.service: container-apps
 ms.custom: event-tier1-build-2022
 ms.topic: how-to
-ms.date: 07/29/2022
+ms.date: 08/30/2022
 ms.author: v-bcatherine
 ---
 
@@ -19,9 +19,9 @@ Azure Monitor alerts notify you so that you can respond quickly to critical issu
 
 You can create alert rules from metric charts in the metric explorer and from queries in Log Analytics.  You can also define and manage alerts from the **Monitor>Alerts** page.  To learn more about alerts, refer to [Overview of alerts in Microsoft Azure](../azure-monitor/alerts/alerts-overview.md).
 
-The **Alerts** page in the **Monitoring** section on your container app page displays all of your app's alerts.  You can filter the list by alert type, resource, time and severity.  You can also modify and create new alerts from this page.
+The **Alerts** page in the **Monitoring** section on your container app page displays all of your app's alerts.  You can filter the list by alert type, resource, time and severity.  You can also modify and create new alert rules from this page.
 
-### Create metric alert rules
+## Create metric alert rules
 
 When you create alerts rules based on a metric chart in the metrics explorer, alerts are triggered when the metric data matches alert rule conditions. For more information about creating metrics charts, see [Using metrics explorer](metrics.md#using-metrics-explorer)
 
@@ -41,7 +41,7 @@ After creating a metric chart, you can create a new alert rule.
    :::image type="content" source="media/observability/screenshot-alert-details-dialog.png" alt-text="Screen shot of the alert details configuration page.":::
 
 
-#### Add conditions to an alert rule
+### Add conditions to an alert rule
 
 To add more conditions to your alert rule:
 
@@ -61,7 +61,7 @@ Example of selecting a dimension to split an alert.
 
  To learn more about configuring alerts, visit [Create a metric alert for an Azure resource](../azure-monitor/alerts/tutorial-metric-alert.md)
 
-### Create log alert rules
+## Create log alert rules
 
 You can create log alerts from queries in Log Analytics.  When you create an alert rule from a query, the query is run at set intervals triggering alerts when the log data matches the alert rule conditions.  To learn more about creating log alert rules, see [Manage log alerts](../azure-monitor/alerts/alerts-log.md).
 
@@ -84,5 +84,5 @@ To create an alert rule:
 1. Select **Review + create**.
 1. Select **Create**.
 
- [!div class="nextstepaction"]
+> [!div class="nextstepaction"]
 > [View log streams from the Azure portal](log-streaming.md)

articles/container-apps/container-console.md

@@ -6,7 +6,7 @@ author: cebundy
 ms.service: container-apps
 ms.custom: event-tier1-build-2022
 ms.topic: how-to
-ms.date: 08/25/2022
+ms.date: 08/30/2022
 ms.author: v-bcatherine
 ---
 
@@ -17,19 +17,19 @@ Connecting to a container's console is useful when you want to troubleshoot your
 
 ## Azure portal
 
-Select **Console** in the **Monitoring** menu group from your container app page in the Azure portal.
+To connect to a container's console in the Azure portal, follow these steps.
 
-* Select the revision, replica and container you want to connect to.
-
-* You can choose to access your console via bash, sh, or a custom executable.  If you choose a custom executable, it must be available in the container.
+1. Select **Console** in the **Monitoring** menu group from your container app page in the Azure portal.
+1. Select the revision, replica and container you want to connect to.
+1. Choose to access your console via bash, sh, or a custom executable.  If you choose a custom executable, it must be available in the container.
 
 :::image type="content" source="media/observability/console-ss.png" alt-text="Screenshot of Azure Container Apps Console page.":::
 
 ## Azure CLI
 
 Use the `az containerapp exec` command to connect to a container console.  Select **Ctrl-D** to exit the console.
 
-For example, connect to a container console in a container app with a single revision, replica, and container using the following command.  Replace the \<placeholders\> with your container app's values.
+For example, connect to a container console in a container app with a single container using the following command.  Replace the \<placeholders\> with your container app's values.
 
 # [Bash](#tab/bash)
 
@@ -49,7 +49,13 @@ az containerapp exec `
 
 ---
 
-To connect to a container console in a container app with multiple revisions, replicas, and containers include the `--revision`, `--replica`, and `--container` arguments with the `az containerapp exec` command. 
+To connect to a container console in a container app with multiple revisions, replicas, and containers include the  following parameters in the `az containerapp exec` command.
+
+| Argument | Description |
+|----------|-------------|
+| `--revision` | The revision name of the container connect to. |
+| `--replica` | The replica name of the container o connect to. |
+| `--container` | The container name of the container to connect to. |
 
 You can get the revision names with the `az containerapp revision list` command.  Replace the \<placeholders\> with your container app's values.
 
@@ -97,28 +103,28 @@ az containerapp replica list `
 
 ---
 
-Connect to the container console using the names from the `az containerapp revision list` command.
+Connect to the container console with the `az containerapp exec` command. Replace the \<placeholders\> with your container app's values.
 
 # [Bash](#tab/bash)
 
 ```azurecli
 az containerapp exec \
-  --name album-api \
-  --resource-group album-api-rg \
-  --revision album-api--v2 \
-  --replica album-api--v2-5fdd5b4ff5-6mblw \
-  --container album-api-container 
+  --name <ContainerAppName> \
+  --resource-group <ResourceGroup> \
+  --revision <RevisionName> \
+  --replica <ReplicaName> \
+  --container <ContainerName> 
 ```
 
 # [PowerShell](#tab/powershell)
 
 ```azurecli
 az containerapp exec `
-  --name album-api `
-  --resource-group album-api-rg `
-  --revision album-api--v2 `
-  --replica album-api--v2-5fdd5b4ff5-6mblw `
-  --container album-api-container
+  --name <ContainerAppName> `
+  --resource-group <ResourceGroup> `
+  --revision <RevisionName> `
+  --replica <ReplicaName> `
+  --container <ContainerName> 
 ```
 
 ---

articles/container-apps/log-monitoring.md

@@ -6,7 +6,7 @@ author: cebundy
 ms.service: container-apps
 ms.custom: event-tier1-build-2022
 ms.topic: how-to
-ms.date: 07/29/2022
+ms.date: 08/30/2022
 ms.author: v-bcatherine
 ---
 

articles/container-apps/log-streaming.md

@@ -6,7 +6,7 @@ author: cebundy
 ms.service: container-apps
 ms.custom: event-tier1-build-2022
 ms.topic: how-to
-ms.date: 08/29/2022
+ms.date: 08/30/2022
 ms.author: v-bcatherine
 ---
 
@@ -59,7 +59,13 @@ az containerapp logs show `
 
 ---
 
-When your app has multiple active revisions, replicas, and containers, you need to specify the container by including  the `--revision`, `--replica`, and `--container` arguments in the `az containerapp logs show` command.
+To connect to a container console in a container app with multiple revisions, replicas, and containers include the  following parameters in the `az containerapp logs show` command.
+
+| Argument | Description |
+|----------|-------------|
+| `--revision` | The revision name of the container connect to. |
+| `--replica` | The replica name of the container o connect to. |
+| `--container` | The container name of the container to connect to. |
 
 You can get the revision names with the `az containerapp revision list` command.  Replace the \<placeholders\> with your container app's values.
 
@@ -107,7 +113,7 @@ az containerapp replica list `
 
 ---
 
-Run the `az container app show` command using the names from the `az containerapp revision list ` command output.  Replace the \<placeholders\> with your container app's values.
+Stream the container logs with the `az container app show` command. Replace the \<placeholders\> with your container app's values.
 
 
 # [Bash](#tab/bash)

articles/container-apps/metrics.md

@@ -6,13 +6,15 @@ author: cebundy
 ms.service: container-apps
 ms.custom: event-tier1-build-2022
 ms.topic: how-to
-ms.date: 07/29/2022
+ms.date: 08/30/2022
 ms.author: v-bcatherine
 ---
 
 # Monitor Azure Container Apps metrics
 
-Azure Monitor collects metric data from your container app at regular intervals. These metrics help you gain insights into the performance and health of your container app. You can use the metrics explorer in the Azure portal to monitor and analyze the metric data. You can also retrieve metric data through the [Azure CLI](/cli/azure/monitor/metrics) and Azure [PowerShell cmdlets](/powershell/module/az.monitor/get-azmetric).
+Azure Monitor collects metric data from your container app at regular interval to help you gain insights into the performance and health of your container app. 
+
+The metrics explorer in the Azure portal allows you to visualize the data. You can also retrieve raw metric data through the [Azure CLI](/cli/azure/monitor/metrics) and Azure [PowerShell cmdlets](/powershell/module/az.monitor/get-azmetric).
 
 ## Available metrics
 
@@ -32,7 +34,7 @@ The metrics namespace is `microsoft.app/containerapps`.
 
 ## Metrics snapshots
 
-On your container app **Overview** page in the Azure portal, select the **Monitoring** tab to display charts showing your container app's current CPU, memory, and network utilization.
+Select the **Monitoring** tab on your app's **Overview** page to display charts showing your container app's current CPU, memory, and network utilization.
 
 :::image type="content" source="media/observability/metrics-in-overview-page.png" alt-text="Screenshot of the Monitoring section in the container app overview page.":::
 
@@ -42,14 +44,14 @@ From this view, you can pin one or more charts to your dashboard or select a cha
 
 The Azure Monitor metrics explorer lets you create charts from metric data to help you analyze your container app's resource and network usage over time. You can pin charts to a dashboard or in a shared workbook.
 
-1. Open the metrics explorer in the Azure portal by selecting **Metrics** from the sidebar menu on your container app page.  To learn more about metrics explorer, go to [Getting started with metrics explorer](../azure-monitor/essentials/metrics-getting-started.md).
+1. Open the metrics explorer in the Azure portal by selecting **Metrics** from the sidebar menu on your container app's page.  To learn more about metrics explorer, go to [Getting started with metrics explorer](../azure-monitor/essentials/metrics-getting-started.md).
 
 1. Create a chart by selecting **Metric**.  You can modify the chart by changing aggregation, adding more metrics, changing time ranges and intervals, adding filters, and applying splitting.
 :::image type="content" source="media/observability/metrics-main-page.png" alt-text="Screenshot of the metrics explorer from the container app resource page.":::
 
 ### Add filters
 
-Optionally, you can create filters based on revisions and replicas.  To create a filter:
+Optionally, you can create filters to limit the data shown based on revisions and replicas.  To create a filter:
 1. Select **Add filter**.
 1. Select a revision or replica from the **Property** list.
 1. Select values from the **Value** list.
@@ -59,15 +61,18 @@ Optionally, you can create filters based on revisions and replicas.  To create a
 
 When your chart contains a single metric, you can choose to split the metric information by revision or replica with the exceptions:
 
-* The Replica count metric can only split by revision.
-* The requests metric can also be split by status code and status code category. 
+* The *Replica count* metric can only split by revision.
+* The *Requests* metric can also be split by status code and status code category. 
 
-To split by revision:
+To split by revision or replica:
 
 1. Select **Apply splitting** 
-1. Select **Revision** from the **Values** drop-down list. 
+1. Select **Revision** or **Replica**  from the **Values** drop-down list. 
+1. You can set the limit of the number of revisions or replicas to display in the chart.  The default is 10. 
+1. You can set Sort order to **Ascending** or **Descending**.  The default is **Descending**.
+
+:::image type="content" source="media/observability/metrics-splitting.png" alt-text="Screenshot of the metrics explorer showing the chart splitting options.":::
 
-:::image type="content" source="media/observability/metrics-apply-splitting.png" alt-text="Screenshot of the metrics explorer that shows a chart with metrics split by revision.":::
 
 ### Add scopes
 

articles/container-apps/observability.md

@@ -39,20 +39,20 @@ During the development and test phase, real-time access to your containers' appl
 
 ### Deployment
 
-Once you deploy your container app, it's essential to monitor your app. Upon deployment, continuous monitoring helps you quickly identify problems that may occur around error rates, performance, or metrics.
+Once you deploy your container app, continuous monitoring helps you quickly identify problems that may occur around error rates, performance, and resource consumption.
 
 Azure Monitor gives you the ability to track your app with the following features:
 
 - [Azure Monitor metrics](metrics.md): Monitor and analyze key metrics.
-- [Azure Monitor alerts](alerts.md): Send alerts for critical conditions.
+- [Azure Monitor alerts](alerts.md): Recieve alerts for critical conditions.
 - [Azure Monitor Log Analytics](log-monitoring.md): View and analyze application logs.
 
 ### Maintenance
 
 Container Apps manages updates to your container app by creating [revisions](revisions.md).  You can run multiple revisions concurrently in blue green deployments or to perform A/B testing.  These observability features will help you monitor your app across revisions:
 
 - [Azure Monitor metrics](metrics.md): Monitor and compare key metrics for multiple revisions.
-- [Azure Monitor alerts](alerts.md): Send alerts individual alerts per revision.
+- [Azure Monitor alerts](alerts.md): Receive individual alerts per revision.
 - [Azure Monitor Log Analytics](log-monitoring.md): View, analyze and compare log data for multiple revisions.
 
 ## Next steps