Merge pull request #295280 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/azure-functions/functions-develop-local.md

@@ -44,7 +44,7 @@ Other files in the project depend on your language and specific functions. For m
 The local.settings.json file stores app settings and settings used by local development tools. Settings in the local.settings.json file are used only when you're running your project locally. When you publish your project to Azure, be sure to also add any required settings to the app settings for the function app.
 
 > [!IMPORTANT]  
-> Because the local.settings.json may contain secrets, such as connection strings, you should never store it in a remote repository. Tools that support Functions provide ways to synchronize settings in the local.settings.json file with the [app settings](functions-how-to-use-azure-function-app-settings.md#settings) in the function app to which your project is deployed.
+> Because the local.settings.json may contain secrets, such as connection strings, you should take care if committing to source control. Tools that support Functions provide ways to synchronize settings in the local.settings.json file with the [app settings](functions-how-to-use-azure-function-app-settings.md#settings) in the function app to which your project is deployed.
 
 The local settings file has this structure:
 

articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/stickers/messages-quickstart-sticker-messages-javascript.md

@@ -23,7 +23,7 @@ ms.author: armohamed
 
 ## Object model
 
-The following classes and interfaces handle some of the major features of the Azure Communication Services Messages SDK for Javascript.
+The following classes and interfaces handle some of the major features of the Azure Communication Services Messages SDK for JavaScript.
 
 | Class Name | Description |
 | --- | --- |

articles/communication-services/quickstarts/advanced-messaging/whatsapp/includes/templates/messages-quickstart-template-messages-javascript.md

@@ -22,7 +22,7 @@ ms.author: shamkh
 
 ## Object model
 
-The following classes and interfaces handle some of the major features of the Azure Communication Services Messages SDK for Javascript.
+The following classes and interfaces handle some of the major features of the Azure Communication Services Messages SDK for JavaScript.
 
 | Class Name | Description |
 | --- | --- |

articles/virtual-network/how-to-multiple-prefixes-subnet.md

@@ -20,7 +20,7 @@ Currently, Virtual Machine Scale Sets allows you to specify only one subnet. The
 
 The following limitations apply during the public preview:
 
-- The feature only supports virtual machines and virtual machine scale sets and doesn't support Bare Metal or PodSubnet scenario in AKS. Any delegated subnet can't use this feature.
+- The feature only supports virtual machines and virtual machine scale sets and doesn't support Bare Metal or VNet injection for Containers, especially PodSubnet IPAM mode in AKS clusters. Any delegated subnet can't use this feature.
 
 - This feature doesn't support multiple customer address (CA) configurations. When using multiple prefixes on a subnet, you're only able to use a single customer address (CA) configuration. A single IPv4 (Internet Protocol version 4) and single IPv6 (Internet Protocol Version 6) address per NIC (network interface card) is supported.
 

articles/vpn-gateway/nva-work-remotely-support.md

@@ -20,12 +20,12 @@ All major NVA vendors in Azure Marketplace should have recommendations on the VM
 
 ### Consider the following
 
-- **Capacity and number of concurrent users** -  This number is particularly important for Point-to-Site VPN users as each connected user will create one encrypted (IPSec or SSL VPN) tunnel.  
+- **Capacity and number of concurrent users** -  This number is particularly important for Point-to-Site VPN users as each connected user will create one encrypted (IPsec or SSL VPN) tunnel.  
 - **Aggregate throughput** - What is the aggregate bandwidth you will need to accommodate the number of users you need to which you will need to provide remote access.
 - **The VM size you will need** - You should always use VM sizes recommended by the NVA vendor.  For point-to-site VPN, if you will have a lot concurrent user connections, you should be using larger VM sizes such as [Dv2 and DSv2 series](/azure/virtual-machines/dv2-dsv2-series "Dv2 and Dsv2 Series") VMs. These VMs tend to have more vCPUs and can handle more concurrent VPN sessions.  In addition to having more virtual cores, larger VM sizes in Azure have more aggregate bandwidth capacity than smaller VM sizes.
     > **Important:** Each vendor utilizes resources differently.  If it's not clear what instance sizes you should use to accommodate your estimated user load, you should contact the software vendor directly and ask them for a recommendation.
 - **Number of instances** - If you expect to have a large number of users and connections, there are limits to what scaling up your NVA instance sizes can achieve.  Consider deploying multiple VM instances.
-- **IPSec VPN vs SSL VPN** - In general IPSec VPN implementations perform better than SSL VPN implementations.  
+- **IPsec VPN vs SSL VPN** - In general IPsec VPN implementations perform better than SSL VPN implementations.  
 - **Licensing** - Make sure that the software licenses you have purchased for the NVA solution will cover the sudden growth you may experience during the COVID-19 epidemic.  Many NVA licensing programs limit the number of connections or bandwidth the solution is capable of.
 - **Accelerated Networking** - Consider an NVA solution that has support for Accelerated Networking.  Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, greatly improving its networking performance. This high-performance path bypasses the host from the data path, reducing latency, jitter, and CPU utilization for use with the most demanding network workloads on supported VM types. Accelerated networking is supported on most general purpose and compute-optimized instance sizes with two or more vCPUs.