Merge pull request #291685 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: PhilKang0704

articles/bastion/connect-vm-native-client-linux.md

@@ -78,7 +78,7 @@ You can connect to a VM private IP address instead of the resource ID. Be aware
 Using the `az network bastion` command, replace `--target-resource-id` with `--target-ip-address` and the specified IP address to connect to your VM. The following example uses --ssh-key for the authentication method.
 
 ```azurecli
-az network bastion ssh --name "<BastionName>" --resource-group "<ResourceGroupName>" --target-ip-addres "<VMIPAddress>" --auth-type "ssh-key" --username "<Username>" --ssh-key "<Filepath>"
+az network bastion ssh --name "<BastionName>" --resource-group "<ResourceGroupName>" --target-ip-address "<VMIPAddress>" --auth-type "ssh-key" --username "<Username>" --ssh-key "<Filepath>"
 ```
 
 ## <a name="tunnel"></a>Connect to a VM - tunnel command

articles/bastion/diagnostic-logs.md

@@ -52,7 +52,7 @@ To access your diagnostics logs, you can directly use the storage account that y
    ```json
    { 
    "time":"2019-10-03T16:03:34.776Z",
-   "resourceId":"/SUBSCRIPTIONS/<subscripionID>/RESOURCEGROUPS/MYBASTION/PROVIDERS/MICROSOFT.NETWORK/BASTIONHOSTS/MYBASTION-BASTION",
+   "resourceId":"/SUBSCRIPTIONS/<subscriptionID>/RESOURCEGROUPS/MYBASTION/PROVIDERS/MICROSOFT.NETWORK/BASTIONHOSTS/MYBASTION-BASTION",
    "operationName":"Microsoft.Network/BastionHost/connect",
    "category":"BastionAuditLogs",
    "level":"Informational",
@@ -63,8 +63,8 @@ To access your diagnostics logs, you can directly use the storage account that y
       "clientIpAddress":"131.107.159.86",
       "clientPort":24039,
       "protocol":"ssh",
-      "targetResourceId":"/SUBSCRIPTIONS/<subscripionID>/RESOURCEGROUPS/MYBASTION/PROVIDERS/MICROSOFT.COMPUTE/VIRTUALMACHINES/LINUX-KEY",
-      "subscriptionId":"<subscripionID>",
+      "targetResourceId":"/SUBSCRIPTIONS/<subscriptionID>/RESOURCEGROUPS/MYBASTION/PROVIDERS/MICROSOFT.COMPUTE/VIRTUALMACHINES/LINUX-KEY",
+      "subscriptionId":"<subscriptionID>",
       "message":"Successfully Connected.",
       "resourceType":"VM",
       "targetVMIPAddress":"172.16.1.5",
@@ -73,7 +73,7 @@ To access your diagnostics logs, you can directly use the storage account that y
    },
    "FluentdIngestTimestamp":"2019-10-03T16:03:34.0000000Z",
    "Region":"eastus",
-   "CustomerSubscriptionId":"<subscripionID>"
+   "CustomerSubscriptionId":"<subscriptionID>"
    }
    ```
 
@@ -82,7 +82,7 @@ To access your diagnostics logs, you can directly use the storage account that y
    ```json
    { 
    "time":"2019-10-03T16:03:34.776Z",
-   "resourceId":"/SUBSCRIPTIONS/<subscripionID>/RESOURCEGROUPS/MYBASTION/PROVIDERS/MICROSOFT.NETWORK/BASTIONHOSTS/MYBASTION-BASTION",
+   "resourceId":"/SUBSCRIPTIONS/<subscriptionID>/RESOURCEGROUPS/MYBASTION/PROVIDERS/MICROSOFT.NETWORK/BASTIONHOSTS/MYBASTION-BASTION",
    "operationName":"Microsoft.Network/BastionHost/connect",
    "category":"BastionAuditLogs",
    "level":"Informational",
@@ -93,8 +93,8 @@ To access your diagnostics logs, you can directly use the storage account that y
       "clientIpAddress":"131.107.159.86",
       "clientPort":24039,
       "protocol":"ssh",
-      "targetResourceId":"/SUBSCRIPTIONS/<subscripionID>/RESOURCEGROUPS/MYBASTION/PROVIDERS/MICROSOFT.COMPUTE/VIRTUALMACHINES/LINUX-KEY",
-      "subscriptionId":"<subscripionID>",
+      "targetResourceId":"/SUBSCRIPTIONS/<subscriptionID>/RESOURCEGROUPS/MYBASTION/PROVIDERS/MICROSOFT.COMPUTE/VIRTUALMACHINES/LINUX-KEY",
+      "subscriptionId":"<subscriptionID>",
       "message":"Login Failed",
       "resourceType":"VM",
       "targetVMIPAddress":"172.16.1.5",
@@ -103,7 +103,7 @@ To access your diagnostics logs, you can directly use the storage account that y
    },
    "FluentdIngestTimestamp":"2019-10-03T16:03:34.0000000Z",
    "Region":"eastus",
-   "CustomerSubscriptionId":"<subscripionID>"
+   "CustomerSubscriptionId":"<subscriptionID>"
    }
    ```
 

articles/batch/batch-pool-compute-intensive-sizes.md

@@ -85,7 +85,7 @@ To configure a specialized VM size for your Batch pool, you have several options
 
 ## Example: NVIDIA GPU drivers on Windows NC VM pool
 
-To run CUDA applications on a pool of Windows NC nodes, you need to install NVDIA GPU drivers. The following sample steps use an application package to install the NVIDIA GPU drivers. You might choose this option if your workload depends on a specific GPU driver version.
+To run CUDA applications on a pool of Windows NC nodes, you need to install NVIDIA GPU drivers. The following sample steps use an application package to install the NVIDIA GPU drivers. You might choose this option if your workload depends on a specific GPU driver version.
 
 1. Download a setup package for the GPU drivers on Windows Server 2016 from the [NVIDIA website](https://www.nvidia.com/Download/index.aspx) - for example, [version 411.82](https://us.download.nvidia.com/Windows/Quadro_Certified/411.82/411.82-tesla-desktop-winserver2016-international.exe). Save the file locally using a short name like *GPUDriverSetup.exe*.
 2. Create a zip file of the package.

articles/batch/pool-endpoint-configuration.md

@@ -116,7 +116,7 @@ namespace AzureBatch
     {
         pool.NetworkConfiguration = new NetworkConfiguration
         {
-            EndpointConfiguration = new PoolEndpointConfiguratio(new InboundNatPool[]
+            EndpointConfiguration = new PoolEndpointConfiguration(new InboundNatPool[]
             {
               new InboundNatPool("RDP", InboundEndpointProtocol.Tcp, 3389, 60000, 60099, new NetworkSecurityGroupRule[]
                 {

articles/batch/quick-create-cli.md

@@ -178,7 +178,7 @@ AZ_BATCH_TASK_WORKING_DIR=/mnt/batch/tasks/workitems/myJob/job-1/myTask1/wd
 AZ_BATCH_NODE_SHARED_DIR=/mnt/batch/tasks/shared
 AZ_BATCH_TASK_USER=_azbatch
 AZ_BATCH_NODE_ROOT_DIR=/mnt/batch/tasks
-AZ_BATCH_JOB_ID=myJobl
+AZ_BATCH_JOB_ID=myJob
 AZ_BATCH_NODE_IS_DEDICATED=true
 AZ_BATCH_NODE_ID=tvm-257509324_2-20180703t215033z
 AZ_BATCH_POOL_ID=myPool

articles/batch/resource-files.md

@@ -120,7 +120,7 @@ ResourceFile inputFile = ResourceFile.FromUrl(yourURLFromAzureStorage,
 ```
 
 > [!Note]
-> Managed identity authentication will only work with files in Azure Storage. The nanaged identity needs the `Storage Blob Data Reader` role assignment for the container the file is in, and it must also be [assigned to the Batch pool](managed-identity-pools.md).
+> Managed identity authentication will only work with files in Azure Storage. The managed identity needs the `Storage Blob Data Reader` role assignment for the container the file is in, and it must also be [assigned to the Batch pool](managed-identity-pools.md).
 
 ## Tips and suggestions
 

articles/batch/tutorial-parallel-dotnet.md

@@ -144,7 +144,7 @@ BatchClient _batchClient = new BatchClient(batchUri, new DefaultAzureCredential(
 
 ### Upload input files
 
-The app passes the `blobServerClient` object to the `CreateContainerIfNotExistc` method to create a storage container for the input files (MP4 format) and a container for the task output.
+The app passes the `blobServerClient` object to the `CreateContainerIfNotExist` method to create a storage container for the input files (MP4 format) and a container for the task output.
 
 ```csharp
 CreateContainerIfNotExist(blobClient, inputContainerName);
@@ -229,7 +229,7 @@ if (collection.Exists(poolId) == false)
             },
             ApplicationPackages =
             {
-                    new Azure.ResourceManager.Batch.Models.BatchApplicationPackageReference(new ResourceIdentifier(appPacakgeResourceID))
+                    new Azure.ResourceManager.Batch.Models.BatchApplicationPackageReference(new ResourceIdentifier(appPackageResourceID))
                     {
                         Version = appPackageVersion,
                     }

articles/business-continuity-center/tutorial-monitor-alerts-metrics.md

@@ -26,7 +26,7 @@ To monitor the alerts, follow these steps:
 
    The count of all alert rules appears that have at least one or more fired alerts in the selected time range.
 
-   :::image type="content" source="./media/tutorial-monitor-alerts-metrics/view-triggered-alerts-in-selected-time-range.png" alt-text="Screemshot shows the triggered alerts in a selected time range." lightbox="./media/tutorial-monitor-alerts-metrics/view-triggered-alerts-in-selected-time-range.png":::
+   :::image type="content" source="./media/tutorial-monitor-alerts-metrics/view-triggered-alerts-in-selected-time-range.png" alt-text="Screenshot shows the triggered alerts in a selected time range." lightbox="./media/tutorial-monitor-alerts-metrics/view-triggered-alerts-in-selected-time-range.png":::
 
 2. On **Alerts**, filter the list by *severity of alert*, *category of alert*, *time range* (up to last 15 days), and other parameters.
 

articles/business-process-tracking/create-business-process.md

@@ -16,7 +16,7 @@ ms.date: 06/07/2024
 > This capability is in preview and is subject to the 
 > [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
-To add business context around the Azure resources in an integration solution, you can visualize business processes flows for the tasks implemented by these resources. In Azure Business Process Tracking, a business process is a series of stages that represent the tasks that flow through a real-world business scenario. This business process also specifies a single business identifer or *transaction ID*, such as a ticket number, order number, case number, and so on, to identify a transaction that exists across all the stages in the business process and to correlate those stages together.
+To add business context around the Azure resources in an integration solution, you can visualize business processes flows for the tasks implemented by these resources. In Azure Business Process Tracking, a business process is a series of stages that represent the tasks that flow through a real-world business scenario. This business process also specifies a single business identifier or *transaction ID*, such as a ticket number, order number, case number, and so on, to identify a transaction that exists across all the stages in the business process and to correlate those stages together.
 
 When you add a stage to your business process, you can also define other business property values to capture as data moves through each stage. You can then later map the transaction ID and other properties to specific operations and data outputs in Standard logic app workflows. For more information, see [What is Azure Business Process Tracking](overview.md)?
 
@@ -89,7 +89,7 @@ After you define a business process, you can then map each stage to actual Azure
    | Property | Required | Value | Description |
    |----------|----------|-------|-------------|
    | **Transaction ID** | Yes | <*transaction-ID*> | This important and unique ID identifies a transaction, such as an order number, ticket number, case number, or another similar business identifier that's available across all stages in your business process. <br><br>This example uses the transaction ID named **TicketNumber** to correlate events across the different systems in the example business process, which include CRM, Work Order Management, and Marketing. <br><br>**Note**: Azure Business Process Tracking automatically includes and records the transaction timestamp so that you don't have to separately add this value. Although you can define only a single transaction ID when you create a business process, you can later define other business properties in each stage that you want to record. |
-   | **Data type** | Yes | <*transacton-ID-data-type*> | The data type for your transaction ID: **String** or **Integer**. <br><br>This example uses the **Integer** data type. |
+   | **Data type** | Yes | <*transaction-ID-data-type*> | The data type for your transaction ID: **String** or **Integer**. <br><br>This example uses the **Integer** data type. |
 
    The following example shows the sample transaction ID:
 

articles/communication-services/concepts/analytics/logs/email-logs.md

@@ -108,7 +108,7 @@ By tracking these logs, you can ensure full visibility into your email delivery
 | `Category` | The log category of the event. The category is the granularity at which you can enable or disable logs on a particular resource. The properties that appear within the properties blob of an event are the same within a particular log category and resource type. |
 | `CorrelationID` | The ID for correlated events. Can be used to identify correlated events between multiple tables. For all Email operational logs, the CorrelationId is mapped to the MessageId, which is returned from a successful SendMail request. |
 | `RecipientId` | The email address for the targeted recipient. It is only present for recipient-level events. If this is a message-level event, the property will be empty. |
-| `DeliveryStatus` | The terminal status of the message. Possible valuse for message-level event are: `Dropped`, `OutForDelivery`, `Queued`. Possible valuse for a recipient-level event are: `Delivered`, `Expanded`, `Failed`, `Quarantined`, `FilteredSpam`, `Suppressed`, `Bounced`. |
+| `DeliveryStatus` | The terminal status of the message. Possible values for message-level event are: `Dropped`, `OutForDelivery`, `Queued`. Possible values for a recipient-level event are: `Delivered`, `Expanded`, `Failed`, `Quarantined`, `FilteredSpam`, `Suppressed`, `Bounced`. |
 | `SmtpStatusCode` | SMTP status code returned from the recipient email server in response to a send mail request.
 | `EnhancedSmtpStatusCode` | Enhanced SMTP status code returned from the recipient email server.
 | `SenderDomain` | The domain portion of the SenderAddress used in sending emails.