Fix arcolinx scores.

cebundy · cebundy · commit 2f512a9c3cea · 2022-08-30T11:51:07.000-07:00
diff --git a/articles/container-apps/container-console.md b/articles/container-apps/container-console.md
@@ -53,8 +53,8 @@ To connect to a container console in a container app with multiple revisions, re
 
 | Argument | Description |
 |----------|-------------|
-| `--revision` | The revision name of the container connect to. |
-| `--replica` | The replica name of the container o connect to. |
+| `--revision` | The revision names of the container to connect to. |
+| `--replica` | The replica name of the container to 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.
diff --git a/articles/container-apps/ingress.md b/articles/container-apps/ingress.md
@@ -12,7 +12,7 @@ ms.custom: ignite-fall-2021, event-tier1-build-2022
 
 # Set up HTTPS ingress in Azure Container Apps
 
-Azure Container Apps allows you to expose your container app to the public web by enabling ingress. When you enable ingress, you do not need to create an Azure Load Balancer, public IP address, or any other Azure resources to enable incoming HTTPS requests.
+Azure Container Apps allows you to expose your container app to the public web by enabling ingress. When you enable ingress, you don't need to create an Azure Load Balancer, public IP address, or any other Azure resources to enable incoming HTTPS requests.
 
 With ingress enabled, your container app features the following characteristics:
 
@@ -26,7 +26,7 @@ With ingress enabled, your container app features the following characteristics:
 
 ## Configuration
 
-Ingress is an application-wide setting. Changes to ingress settings apply to all revisions simultaneously, and do not generate new revisions.
+Ingress is an application-wide setting. Changes to ingress settings apply to all revisions simultaneously, and don't generate new revisions.
 
 The ingress configuration section has the following form:
 
@@ -47,10 +47,10 @@ The following settings are available when configuring ingress:
 
 | Property | Description | Values | Required |
 |---|---|---|---|
-| `external` | When enabled, the environment is assigned a public IP and fully qualified domain name (FQDN) for external ingress and an internal IP and FQDN for internal ingress .  When disabled, only an internal IP/FQDN is created. |`true` for external visibility, `false` for internal visibility (default) | Yes |
+| `external` | When enabled, the environment is assigned a public IP and fully qualified domain name (FQDN) for external ingress and an internal IP and FQDN for internal ingress.  When disabled, only an internal IP/FQDN is created. |`true` for external visibility, `false` for internal visibility (default) | Yes |
 | `targetPort` | The port your container listens to for incoming requests. | Set this value to the port number that your container uses. Your application ingress endpoint is always exposed on port `443`. | Yes |
 | `transport` | You can use either HTTP/1.1 or HTTP/2, or you can set it to automatically detect the transport type. | `http` for HTTP/1, `http2` for HTTP/2, `auto` to automatically detect the transport type (default) | No |
-| `allowInsecure` | Allows insecure traffic to your container app. | `false` (default), `true`<br><br>If set to `true`, HTTP requests to port 80 are not automatically redirected to port 443 using HTTPS, allowing insecure connections. | No |
+| `allowInsecure` | Allows insecure traffic to your container app. | `false` (default), `true`<br><br>If set to `true`, HTTP requests to port 80 aren't automatically redirected to port 443 using HTTPS, allowing insecure connections. | No |
 
 > [!NOTE]
 > To disable ingress for your application, you can omit the `ingress` configuration property entirely.
diff --git a/articles/container-apps/log-monitoring.md b/articles/container-apps/log-monitoring.md
@@ -24,7 +24,7 @@ There are two types of logs for Container Apps.
 
 ## System Logs
 
-The Container Apps service provides system log messages at the container app level.  System logs emits the following messages:
+The Container Apps service provides system log messages at the container app level.  System logs emit the following messages:
 
 | Source | Type | Message |
 |---------|------|---------|
@@ -74,7 +74,7 @@ The most commonly used Container Apps specific columns in ContainerAppConsoleLog
 
 Log Analytics is a tool in the Azure portal that you can use to view and analyze log data. Using Log Analytics, you can write Kusto queries and then sort, filter, and visualize the results in charts to spot trends and identify issues. You can work interactively with the query results or use them with other features such as alerts, dashboards, and workbooks.
 
-### Azure Portal
+### Azure portal
 
 Start Log Analytics from **Logs** in the sidebar menu on your container app page.  You can also start Log Analytics from **Monitor>Logs**.  
 
diff --git a/articles/container-apps/log-streaming.md b/articles/container-apps/log-streaming.md
@@ -37,7 +37,7 @@ Use `Ctrl/Cmd-C` to stop the live stream.
 
 For example, you can list the last 50 container log entries in a container app with a single container using the following command.
 
-This example live streams the a container's log entries.
+This example live streams a container's log entries.
 
 # [Bash](#tab/bash)
 
@@ -63,8 +63,8 @@ To connect to a container console in a container app with multiple revisions, re
 
 | Argument | Description |
 |----------|-------------|
-| `--revision` | The revision name of the container connect to. |
-| `--replica` | The replica name of the container o connect to. |
+| `--revision` | The revision name of the container to connect to. |
+| `--replica` | The replica name of the container to 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.
diff --git a/articles/container-apps/observability.md b/articles/container-apps/observability.md
@@ -44,7 +44,7 @@ Once you deploy your container app, continuous monitoring helps you quickly iden
 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): Recieve alerts for critical conditions.
+- [Azure Monitor alerts](alerts.md): Receive alerts for critical conditions.
 - [Azure Monitor Log Analytics](log-monitoring.md): View and analyze application logs.
 
 ### Maintenance
diff --git a/includes/container-apps-create-cli-steps.md b/includes/container-apps-create-cli-steps.md
@@ -59,7 +59,7 @@ az provider register --namespace Microsoft.App
 
 ---
 
-Register the `Microsoft.OperationalInsights` provider for the [Azure Monitor Log Analytics Workspace](../articles/container-apps/log-monitoring.md) if you have not used it before.
+Register the `Microsoft.OperationalInsights` provider for the [Azure Monitor Log Analytics Workspace](../articles/container-apps/log-monitoring.md) if you haven't used it before.
 
 # [Bash](#tab/bash)
 
