Merge pull request #292726 from jonburchel/2025-01-07-public-pr-125307

2025 01 07 public pr 125307

Author: JamesJBarnett

articles/confidential-computing/confidential-enclave-nodes-aks-get-started.md

@@ -202,8 +202,8 @@ spec:
               - key: agentpool
                 operator: In
                 values:
-                - acc # this is the name of your confidential computing nodel pool
-                - acc_second # this is the name of your confidential computing nodel pool
+                - acc # this is the name of your confidential computing node pool
+                - acc_second # this is the name of your confidential computing node pool
       containers:
       - name: oe-helloworld
         image: mcr.microsoft.com/acc/samples/oe-helloworld:latest

articles/connectors/built-in.md

@@ -106,8 +106,8 @@ You can use the following built-in connectors to perform general tasks, for exam
     :::column:::
         [![Request trigger icon][http-request-icon]][http-request-doc]
         <br><br>[**Request**][http-request-doc]
-        <br><br>[**When a HTTP request is received**][http-request-doc]: Wait for a request from another workflow, app, or service. This trigger makes your workflow callable without having to be checked or polled on a schedule.
-        <br><br>[**Response**][http-request-doc]: Respond to a request received by the **When a HTTP request is received** trigger in the same workflow.
+        <br><br>[**When an HTTP request is received**][http-request-doc]: Wait for a request from another workflow, app, or service. This trigger makes your workflow callable without having to be checked or polled on a schedule.
+        <br><br>[**Response**][http-request-doc]: Respond to a request received by the **When an HTTP request is received** trigger in the same workflow.
     :::column-end:::
     :::column:::
         [![Batch icon][batch-icon]][batch-doc]
@@ -209,7 +209,7 @@ You can use the following built-in connectors to access specific services and sy
     :::column:::
         [![Azure Logic Apps icon][azure-logic-apps-icon]][nested-logic-app-doc]
         <br><br>[**Azure Logic Apps**][nested-logic-app-doc]<br>(*Consumption workflow*) <br><br>-or-<br><br>**Workflow Operations**<br>(*Standard workflow*)
-        <br><br>Call other workflows that start with the Request trigger named **When a HTTP request is received**.
+        <br><br>Call other workflows that start with the Request trigger named **When an HTTP request is received**.
     :::column-end:::
     :::column:::
         [![Azure OpenAI icon][azure-openai-icon]][azure-openai-doc]
@@ -466,7 +466,7 @@ For more information, review the following documentation:
     :::column:::
         [![SWIFT icon][swift-icon]][swift-doc]
         <br><br>[**SWIFT**][swift-doc]<br>(*Standard workflow only*)
-        <br><br>Encode and decode Society for Worldwide Interbank Financial Telecommuncation (SIWFT) transactions in flat-file XML message format.
+        <br><br>Encode and decode Society for Worldwide Interbank Financial Telecommunication (SWIFT) transactions in flat-file XML message format.
     :::column-end:::
     :::column:::
         [![X12 icon][x12-icon]][x12-doc]
@@ -478,7 +478,7 @@ For more information, review the following documentation:
         <br><br>[**XML Operations**][xml-operations-doc]
         <br><br>Perform operations with XML.
         <br><br>**Compose XML with schema**: Create XML from JSON using a schema for a Standard workflow.
-        <br><br>**Parse XML with schema**: Parse XML using a schema for a Standard workflow..
+        <br><br>**Parse XML with schema**: Parse XML using a schema for a Standard workflow.
         <br><br>**Transform XML**: Convert XML using a map.
         <br><br>**Validate XML**: Validate inbound or outbound XML using a schema.
     :::column-end:::

articles/container-apps/authentication.md

@@ -160,7 +160,7 @@ The token format varies slightly according to the provider. See the following ta
 | `microsoftaccount` | `{"access_token":"<ACCESS_TOKEN>"}` or `{"authentication_token": "<TOKEN>"`| `authentication_token` is preferred over `access_token`. The `expires_in` property is optional. <br/> When requesting the token from Live services, always request the `wl.basic` scope. |
 | `google` | `{"id_token":"<ID_TOKEN>"}` | The `authorization_code` property is optional. Providing an `authorization_code` value adds an access token and a refresh token to the token store. When specified, `authorization_code` can also optionally be accompanied by a `redirect_uri` property. |
 | `facebook`| `{"access_token":"<USER_ACCESS_TOKEN>"}` | Use a valid [user access token](https://developers.facebook.com/docs/facebook-login/access-tokens) from Facebook. |
-| `twitter` | `{"access_token":"<ACCESS_TOKEN>", "access_token_secret":"<ACCES_TOKEN_SECRET>"}` | |
+| `twitter` | `{"access_token":"<ACCESS_TOKEN>", "access_token_secret":"<ACCESS_TOKEN_SECRET>"}` | |
 | | | |
 
 If the provider token is validated successfully, the API returns with an `authenticationToken` in the response body, which is your session token. 

articles/container-apps/networking.md

@@ -153,7 +153,7 @@ Different environment types have different subnet requirements:
     | /26 | 52 | 26 | 260 |
     | /27 | 20 | 10 | 100 |
 
-    <sup>1</sup> The available IP addresses is the size of the subnet minus the 12 IP addresses required for Azure Container Apps infrastructure.  
+    <sup>1</sup> The available IP addresses are the size of the subnet minus the 12 IP addresses required for Azure Container Apps infrastructure.  
     <sup>2</sup> This is accounting for apps in single revision mode.  
 
 # [Consumption only environment](#tab/consumption-only-env)
@@ -219,7 +219,7 @@ If you're using the Azure CLI with a Consumption only environment and the [platf
 User Defined Routes (UDR) and controlled egress through NAT Gateway are supported in the workload profiles environment. In the Consumption only environment, these features aren't supported.
 
 > [!NOTE]
-> When using UDR with Azure Firewall in Azure Container Apps, you need to add certain FQDN's and service tags to the allowlist for the firewall. To learn more, see [configuring UDR with Azure Firewall](./networking.md#configuring-udr-with-azure-firewall).
+> When using UDR with Azure Firewall in Azure Container Apps, you need to add certain FQDNs and service tags to the allowlist for the firewall. To learn more, see [configuring UDR with Azure Firewall](./networking.md#configuring-udr-with-azure-firewall).
 
 - You can use UDR with workload profiles environments to restrict outbound traffic from your container app through Azure Firewall or other network appliances.
 
@@ -231,10 +231,10 @@ Azure creates a default route table for your virtual networks upon create. By im
 
 #### Configuring UDR with Azure Firewall
 
-User defined routes is only supported in a workload profiles environment. The following application and network rules must be added to the allowlist for your firewall depending on which resources you're using.
+User defined routes are only supported in a workload profiles environment. The following application and network rules must be added to the allowlist for your firewall depending on which resources you're using.
 
 > [!NOTE]
-> For a guide on how to setup UDR with Container Apps to restrict outbound traffic with Azure Firewall, visit the [how to for Container Apps and Azure Firewall](./user-defined-routes.md).
+> For a guide on how to set up UDR with Container Apps to restrict outbound traffic with Azure Firewall, visit the [how to for Container Apps and Azure Firewall](./user-defined-routes.md).
 
 ##### Application rules
 
@@ -272,7 +272,7 @@ When you configure a NAT Gateway on your subnet, the NAT Gateway provides a stat
 
 ### <a name="public-network-access"></a>Public network access (preview)
 
-The public network access setting determines whether your container apps environment is accesible from the public Internet. Whether you can change this setting after creating your environment depends on the environment's virtual IP configuration. The following table shows valid values for public network access, depending on your environment's virtual IP configuration.
+The public network access setting determines whether your container apps environment is accessible from the public Internet. Whether you can change this setting after creating your environment depends on the environment's virtual IP configuration. The following table shows valid values for public network access, depending on your environment's virtual IP configuration.
 
 | Virtual IP | Supported public network access | Description |
 |--|--|--|
@@ -298,15 +298,15 @@ This feature is supported for both Consumption and Dedicated plans in workload p
 
 #### Considerations
 - Private endpoints on Azure Container Apps only support inbound HTTP traffic. TCP traffic is not supported.
-- To use a private endpoint with a custom domain and an *Apex domain* as the *Hostname record type*, you must configure a private DNS zone with the same name as your public DNS. In the record set, configure your private endpoint's private IP address instead of the container app environment's IP address. When configuring your custom domain with CNAME, the setup is unchanged. For more information, see [Set up custom domain with existing certificate](custom-domains-certificates.md).
+- To use a private endpoint with a custom domain and an *Apex domain* as the *Hostname record type*, you must configure a private DNS zone with the same name as your public DNS. In the record set, configure your private endpoint's private IP address instead of the container app environment's IP address. When you configure your custom domain with CNAME, the setup is unchanged. For more information, see [Set up custom domain with existing certificate](custom-domains-certificates.md).
 - Your private endpoint's VNet can be separate from the VNet integrated with your container app.
 - You can add a private endpoint to both new and existing workload profile environments.
 
 In order to connect to your container apps through a private endpoint, you must configure a private DNS zone.
 
 | Service | subresource | Private DNS zone name |
 |--|--|--|
-| Azure Container Apps (Microsoft.App/ManagedEnvironments) | managedEnvironment | privatelink.{regionName}.azurecontainerapps.io |
+| Azure Container Apps (Microsoft.App/ManagedEnvironments) | managedEnvironment | private link.{regionName}.azurecontainerapps.io |
 
 ### Environment security
 

articles/container-apps/sessions-tutorial-llamaindex.md

@@ -46,7 +46,7 @@ The following lines of code instantiate a *AzureCodeInterpreterToolSpec* and pro
 
 ```python
 code_interpreter_tool = AzureCodeInterpreterToolSpec(
-    pool_managment_endpoint=pool_management_endpoint,
+    pool_management_endpoint=pool_management_endpoint,
 )
 agent = ReActAgent.from_tools(code_interpreter_tool.to_tool_list(), llm=llm, verbose=True)
 ```

articles/cost-management-billing/costs/ingest-azure-usage-at-scale.md

@@ -114,7 +114,7 @@ Here are some of the characteristics of the service-side sync transfer used with
 - The transfer creates checkpoints during its progress and exposes a _TransferCheckpoint_ object. The object represents the latest checkpoint via the _TransferContext_ object. If the _TransferCheckpoint_ is saved before a transfer is cancelled/aborted, the transfer can be resumed from the checkpoint for up to seven days. The transfer can be resumed from any checkpoint, not just the latest.
 - If the transfer client process is killed and restarted without implementing the checkpoint feature:
   - Before any blob transfers complete, the transfer restarts.
-  - After some of the blobs complete, the transfer restarts for only the incompleted blobs.
+  - After some of the blobs complete, the transfer restarts for only the incomplete blobs.
 - Pausing the client execution pauses the transfers.
 - The blob transfer feature abstracts the client from transient failures. For instance, storage account throttling doesn't normally cause a transfer to fail but slows the transfer.
 - Service-side transfers have low client resource usage for CPU and memory, some network bandwidth, and connections.

articles/cost-management-billing/costs/quick-create-budget-bicep.md

@@ -91,7 +91,7 @@ One Azure resource is defined in the Bicep file:
 
     You need to enter the following parameters:
 
-    - **startDate**: Replace **\<start-date\>** with the start date. It must be the first of the month in YYYY-MM-DD format. A future start date shouldn't be more than three months in the future. A past start date should be selected within the timegrain period.
+    - **startDate**: Replace **\<start-date\>** with the start date. It must be the first of the month in YYYY-MM-DD format. A future start date shouldn't be more than three months in the future. A past start date should be selected within the time grain period.
     - **endDate**: Replace **\<end-date\>** with the end date in YYYY-MM-DD format. If not provided, it defaults to ten years from the start date.
     - **contactEmails**: First create a variable that holds your emails and then pass that variable. Replace the sample emails with the email addresses to send the budget notification to when the threshold is exceeded.
 
@@ -137,7 +137,7 @@ One Azure resource is defined in the Bicep file:
 
     You need to enter the following parameters:
 
-    - **startDate**: Replace **\<start-date\>** with the start date. It must be the first of the month in YYYY-MM-DD format. A future start date shouldn't be more than three months in the future. A past start date should be selected within the timegrain period.
+    - **startDate**: Replace **\<start-date\>** with the start date. It must be the first of the month in YYYY-MM-DD format. A future start date shouldn't be more than three months in the future. A past start date should be selected within the time grain period.
     - **endDate**: Replace **\<end-date\>** with the end date in YYYY-MM-DD format. If not provided, it defaults to ten years from the start date.
     - **contactEmails**: First create a variable that holds your emails and then pass that variable. Replace the sample emails with the email addresses to send the budget notification to when the threshold is exceeded.
     - **resourceGroupFilterValues** First create a variable that holds your resource group filter values and then pass that variable. Replace the sample filter values with the set of values for your resource group filter.
@@ -189,7 +189,7 @@ One Azure resource is defined in the Bicep file:
 
     You need to enter the following parameters:
 
-    - **startDate**: Replace **\<start-date\>** with the start date. It must be the first of the month in YYYY-MM-DD format. A future start date shouldn't be more than three months in the future. A past start date should be selected within the timegrain period.
+    - **startDate**: Replace **\<start-date\>** with the start date. It must be the first of the month in YYYY-MM-DD format. A future start date shouldn't be more than three months in the future. A past start date should be selected within the time grain period.
     - **endDate**: Replace **\<end-date\>** with the end date in YYYY-MM-DD format. If not provided, it defaults to ten years from the start date.
     - **contactEmails**: First create a variable that holds your emails and then pass that variable. Replace the sample emails with the email addresses to send the budget notification to when the threshold is exceeded.
     - **contactGroups**: First create a variable that holds your contact groups and then pass that variable. Replace the sample contact groups with the list of action groups to send the budget notification to when the threshold is exceeded. You must pass the resource ID of the action group, which you can get with [az monitor action-group show](/cli/azure/monitor/action-group#az-monitor-action-group-show) or [Get-AzActionGroup](/powershell/module/az.monitor/get-azactiongroup).

articles/cost-management-billing/troubleshoot-billing/troubleshoot-customer-agreement-billing-issues-usage-file-pivot-tables.md

@@ -46,7 +46,7 @@ In this section, you create a pivot table where you can troubleshoot overall gen
 
 1. In the PivotTable Fields area, drag **Meter Category** and **Product** to the **Rows** section. Put **Product** below **Meter Category**.  
     :::image type="content" source="./media/troubleshoot-customer-agreement-billing-issues-usage-file-pivot-tables/rows-section.png" alt-text="Screenshot showing Meter Category and Product in Rows." lightbox="./media/troubleshoot-customer-agreement-billing-issues-usage-file-pivot-tables/rows-section.png" :::
-1. Next, add the **costInBillingCurrenty** column to the **Values** section. You can also use the **Quantity** column instead to get information about consumption units and transactions. For example, GB and Hours. Or, transactions instead of cost in different currencies like USD, EUR, and INR.  
+1. Next, add the **costInBillingCurrency** column to the **Values** section. You can also use the **Quantity** column instead to get information about consumption units and transactions. For example, GB and Hours. Or, transactions instead of cost in different currencies like USD, EUR, and INR.  
     :::image type="content" source="./media/troubleshoot-customer-agreement-billing-issues-usage-file-pivot-tables/add-pivot-table-fields.png" alt-text="Screenshot showing fields added to the pivot table." lightbox="./media/troubleshoot-customer-agreement-billing-issues-usage-file-pivot-tables/add-pivot-table-fields.png" :::
 1. Now you have a dashboard for generalized consumption investigation. You can filter for a specific service using the filtering options in the pivot table.  
     :::image type="content" source="./media/troubleshoot-customer-agreement-billing-issues-usage-file-pivot-tables/pivot-table-filter-option-row-label.png" alt-text="Screenshot showing the pivot table filter option for a row label." lightbox="./media/troubleshoot-customer-agreement-billing-issues-usage-file-pivot-tables/pivot-table-filter-option-row-label.png" :::