Merge pull request #301426 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: Taojunshen

articles/application-gateway/ingress-controller-annotations.md

@@ -37,7 +37,8 @@ For AGIC to observe an ingress resource, the resource *must be annotated* with `
 | [appgw.ingress.kubernetes.io/use-private-ip](#use-private-ip) | `bool` | `false` ||
 | [appgw.ingress.kubernetes.io/override-frontend-port](#override-frontend-port) | `bool` | `false` ||
 | [appgw.ingress.kubernetes.io/cookie-based-affinity](#cookie-based-affinity) | `bool` | `false` ||
-| [appgw.ingress.kubernetes.io/request-timeout](#request-timeout) | `int32` (seconds) | `30` ||
+| [appgw.ingress.kubernetes.io/request-timeout]
+(#request-timeout) | `int32` (seconds) | `30` ||
 | [appgw.ingress.kubernetes.io/use-private-ip](#use-private-ip) | `bool` | `false` ||
 | [appgw.ingress.kubernetes.io/backend-protocol](#backend-protocol) | `string` | `http` | `http`, `https` |
 | [appgw.ingress.kubernetes.io/hostname-extension](#hostname-extension) | `string` | `nil` ||
@@ -121,7 +122,7 @@ spec:
 
 ## Custom Health Probe
 
-You can [configure Application Gateway](./application-gateway-probe-overview.md) to send custom health probes to the backend address pool. When the following annotations are present, the Kubernetes ingress controller [creates a custom probe](./application-gateway-create-probe-portal.md) to monitor the backend application. The controller then applies the changes to Application Gateway.
+You can [configure Application Gateway](./application-gateway-probe-overview.md) to send custom health probe to the backend address pool. When the following annotations are present, the Kubernetes ingress controller [creates a custom probe](./application-gateway-create-probe-portal.md) to monitor the backend application. The controller then applies the changes to Application Gateway.
 
 - `health-probe-hostname`: This annotation allows a custom hostname on the health probe.
 - `health-probe-port`: This annotation configures a custom port for the health probe.

articles/azure-functions/functions-deployment-technologies.md

@@ -210,7 +210,7 @@ You can use FTP/S to directly transfer files to Azure Functions, although this d
 
 >__When to use it:__ To reduce the chance of errors, you should avoid using deployment methods that require the additional step of [manually syncing triggers](#trigger-syncing). Use [zip deployment](run-functions-from-deployment-package.md) when possible.
 
->__Where app content is stored:__ App content is stored on the file system. FTP/FTPS deployments fail when your app's file system is backed by Azure Files in the default host storage account. FTP/FTPS fails with Azure Files as mounted storage bacause of [FTP limitations](../app-service/configure-connect-to-azure-storage.md#limitations).
+>__Where app content is stored:__ App content is stored on the file system. FTP/FTPS deployments fail when your app's file system is backed by Azure Files in the default host storage account. FTP/FTPS fails with Azure Files as mounted storage because of [FTP limitations](../app-service/configure-connect-to-azure-storage.md#limitations).
 
 ### Portal editing
 

articles/azure-signalr/signalr-concept-azure-functions.md

@@ -40,7 +40,7 @@ Some common scenarios for real-time serverless messaging that you can implement
 
 The SignalR Service bindings for Azure Functions allow an Azure Function app to publish messages to clients connected to SignalR Service. Clients can connect to the service using a SignalR client SDK that is available in .NET, JavaScript, and Java, with more languages coming soon.
 
-<!-- Are there more lanaguages now? -->
+<!-- Are there more languages now? -->
 
 ### An example scenario
 

articles/data-factory/connector-troubleshoot-guide.md

@@ -54,7 +54,7 @@ The following errors are general to the copy activity and could occur with any c
 
 - **Cause**: This typically indicates an authentication failure during data transfer operations. This can occur when the remote party closes the transport stream.
 
-- **Reccomendation**:
+- **Recommendation**:
   - Verify the source connection and test it to ensure it is functioning correctly.
   - Check the authentication method used for the connection.
   - Review firewall configuration settings for Azure Cosmos DB to ensure they allow the necessary traffic.

articles/data-factory/data-flow-troubleshoot-connector-format.md

@@ -596,7 +596,7 @@ The escape character either escapes the column delimiter or the escape the chara
 4. The quote character and the escape character both be empty and the column value contains column delimiters.<br/>
 `Column delimiter: \t`<br/>
 `column value: 111\t222\t33\t3`<br/>
-`It will be ambigious if it contains 3 columns 111,222,33\t3 or 4 columns 111,222,33,3.`<br/>
+`It will be ambiguous if it contains 3 columns 111,222,33\t3 or 4 columns 111,222,33,3.`<br/>
 
 #### Recommendation
 The first symptom and the second symptom can't be solved currently. For the third and fourth symptoms, you can apply the following methods:

articles/operator-nexus/list-of-metrics-collected.md

@@ -321,7 +321,7 @@ Baremetal server metrics are collected and delivered to Azure Monitor per minute
 |NodeNetworkReceiveMulticastTotal|Network|Node Network Received Multicast Total|Bytes|Total amount of multicast traffic received by the node network interfaces. In the absence of data, this metric will retain the most recent value emitted|Device, Host|
 |NodeNetworkReceivePackets|Network|Node Network Received Packets|Count|Total number of packets received by the node network interfaces. In the absence of data, this metric will retain the most recent value emitted|Device, Host|
 |NodeNetworkSpeedBytes|Network|Node Network Speed Bytes|Bytes|Current network speed, in bytes per second, for the node network interfaces. In the absence of data, this metric will default to 0|Device, Host|
-|NodeNetworkTransmitPackets|Network|Node Network Transmited Packets|Count|Total number of packets transmitted by the node network interfaces. In the absence of data, this metric will retain the most recent value emitted|Device, Host|
+|NodeNetworkTransmitPackets|Network|Node Network Transmitted Packets|Count|Total number of packets transmitted by the node network interfaces. In the absence of data, this metric will retain the most recent value emitted|Device, Host|
 |NodeNetworkStatus|Network|Node Network Up|Count|Indicates the operational status of the nodes network interfaces. Value is 1 if operational state is 'up', 0 otherwise. In the absence of data, this metric will retain the most recent value emitted|Device, Host|
 |NodeNtpLeap|System|Node NTP Leap|Count|The raw leap flag value of the local NTP daemon. This indicates the status of leap seconds. Value is 0 if no adjustment is needed, 1 to add a leap second, 2 to delete a leap second, and 3 if the clock is unsynchronized. In the absence of data, this metric will retain the most recent value emitted|Host|
 |NodeNtpRootDelaySeconds|System|Node NTP Root Delay Seconds|Seconds|Indicates the delay to synchronize with the root server. In the absence of data, this metric will retain the most recent value emitted|Host|

articles/oracle/oracle-db/oracle-database-regions.md

@@ -53,7 +53,7 @@ The list below mentions the Azure and corresponding OCI regions with the regiona
 | Azure region   | OCI region     | Oracle Exadata Database@Azure  | Oracle Autonomous Database@Azure | Oracle Database Autonomous Recovery Service@Azure| Exadata Database Service on Exascale Infrastructure@Azure | BaseDB | Regional Availability|
 | -------------- | -------------------|------------------------|------------------ | ---- |-----|-----|----|
 | East US        | US East (Ashburn)          | ✓   | ✓ | ✓ | | Preview available | Dual  |
-| Canada Central | Canada Southeast (Toronto) | ✓ |  ✓ | | | | Single  |
+| Canada Central | Canada Southeast (Toronto) | ✓ |  ✓ | | | | Dual  |
 | West US | US West (San Jose)  | ✓  | ✓  | ✓| | Preview available | Single |
 | Central US | US Midwest (Chicago)  | ✓  |   ✓  | ✓ | | | Dual |
 | East US 2 | US East (Ashburn) | ✓  |   | | | | Dual |

articles/storage/blobs/storage-blob-javascript-get-started.md

@@ -29,7 +29,6 @@ If you're looking to start with a complete example, see the client library quick
 - [Node.js LTS](https://nodejs.org/)
 - [TypeScript](https://www.typescriptlang.org/download), if applicable
 - For client (browser) applications, you need [bundling tools](https://github.com/Azure/azure-sdk-for-js/blob/main/documentation/Bundling.md).
-- 
 
 ## Set up your project
 
@@ -174,4 +173,4 @@ The following guides show you how to access data and perform specific actions us
 | [Manage properties and metadata (containers)](storage-blob-container-properties-metadata-javascript.md) | Get and set properties and metadata for containers. |
 | [Performance tuning for data transfers](storage-blobs-tune-upload-download-javascript.md) | Optimize performance for data transfer operations. |
 | [Set or change a blob's access tier](storage-blob-use-access-tier-javascript.md) | Set or change the access tier for a block blob. |
-| [Upload blobs](storage-blob-upload-javascript.md) | Learn how to upload blobs by using strings, streams, file paths, and other methods. |
+| [Upload blobs](storage-blob-upload-javascript.md) | Learn how to upload blobs by using strings, streams, file paths, and other methods. |

articles/virtual-network/how-to-virtual-machine-mtu.md

@@ -64,7 +64,7 @@ The following resources are used as examples in this article. Replace these valu
 
 ## Precautions
 
-- Virtual machines in Azure can support a larger MTU than the 1,500-byte default only for traffic that stays within the virtual network. A larger MTU isn't supported for scenarios outside of intra-virtual network VM-to-VM traffic. Traffic traversing through gateways, peering’s, or to the internet might not be supported. Configuration of a larger MTU can result in fragmentation and reduction in performance. For traffic utilizing these scenarios, utilize the default 1,500 byte MTU for testing to ensure that a larger MTU is supported across the entire network path. 
+- Virtual machines in Azure can support a larger MTU than the 1,500-byte default only for traffic that stays within the virtual network and directly peered virtual networks within the same region. Traffic traversing through gateways, global peerings, or to the internet is not supported. Configuration of a larger MTU can result in fragmentation and reduction in performance. For traffic utilizing these scenarios, utilize the default 1,500 byte MTU for testing to ensure that a larger MTU is supported across the entire network path. 
 
 - Optimal MTU is operating system, network, and application specific. The maximal supported MTU might not be optimal for your use case.
 

articles/virtual-network/ip-services/virtual-network-private-ip-address-blocks-portal.md

@@ -100,7 +100,7 @@ You can add a static private IP address prefix to a virtual machine by completin
    | **Private IP address settings** |   |
    | Private IP Address Type | IP address prefix |
    | Allocation | Select **Static**. |
-   | IP address | Enter an unused CIDR of size /28 from the subnet for your virtual machine.</br> For the 10.0.0.0/14 subnet in the example, an IP would be **10.0.0.0/80**. |
+   | IP address | Enter an unused CIDR of size /28 from the subnet for your virtual machine.</br> For the 10.0.0.0/14 subnet in the example, an IP would be **10.0.0.0/28**. |
 
 9. Select **OK**.