Merge pull request #294125 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/automation/update-management/overview.md

@@ -174,7 +174,7 @@ sudo yum -q --security check-update
 > [!NOTE]
 > Currently there's no supported method to enable native classification-data availability on CentOS. At this time, we provide limited support to customers who might have enabled this feature on their own.
 
-**Redhat** - To classify updates on Red Hat Enterprise version 6, you must install the YUM security plugin. On Red Hat Enterprise Linux 7, the plugin is already a part of YUM itself and there's no need to install anything. For more information, see the following Red Hat [knowledge article](https://access.redhat.com/solutions/10021).
+**Red Hat** - To classify updates on Red Hat Enterprise version 6, you must install the YUM security plugin. On Red Hat Enterprise Linux 7, the plugin is already a part of YUM itself and there's no need to install anything. For more information, see the following Red Hat [knowledge article](https://access.redhat.com/solutions/10021).
 
 
 ## Integrate Update Management with Configuration Manager

articles/azure-netapp-files/performance-linux-filesystem-cache.md

@@ -30,11 +30,11 @@ These factors are controlled by four tunables. Each tunable can be tuned dynamic
 
 ### `vm.dirty_ratio | vm.dirty_bytes` 
 
-These two tunables define the amount of RAM made usable for data modified but not yet written to stable storage. Whichever tunable is set automatically sets the other tunable to zero; RedHat advises against manually setting either of the two tunables to zero. The option `vm.dirty_ratio` (the default of the two) is set by Redhat to either 20% or 30% of physical memory depending on the OS, which is a significant amount considering the memory footprint of modern systems. Consideration should be given to setting `vm.dirty_bytes` instead of `vm.dirty_ratio` for a more consistent experience regardless of memory size. For example, ongoing work with SAS GRID determined 30 MiB an appropriate setting for best overall mixed workload performance. 
+These two tunables define the amount of RAM made usable for data modified but not yet written to stable storage. Whichever tunable is set automatically sets the other tunable to zero; RedHat advises against manually setting either of the two tunables to zero. The option `vm.dirty_ratio` (the default of the two) is set by Red Hat to either 20% or 30% of physical memory depending on the OS, which is a significant amount considering the memory footprint of modern systems. Consideration should be given to setting `vm.dirty_bytes` instead of `vm.dirty_ratio` for a more consistent experience regardless of memory size. For example, ongoing work with SAS GRID determined 30 MiB an appropriate setting for best overall mixed workload performance. 
 
 ### `vm.dirty_background_ratio | vm.dirty_background_bytes` 
 
-These tunables define the starting point where the Linux write-back mechanism begins flushing dirty blocks to stable storage. Redhat defaults to 10% of physical memory, which, on a large memory system, is a significant amount of data to start flushing. With SAS GRID as an example, historically the recommendation was to set `vm.dirty_background` to 1/5 size of `vm.dirty_ratio` or `vm.dirty_bytes`. Considering how aggressively the `vm.dirty_bytes` setting is set for SAS GRID, no specific value is being set here. 
+These tunables define the starting point where the Linux write-back mechanism begins flushing dirty blocks to stable storage. Red Hat defaults to 10% of physical memory, which, on a large memory system, is a significant amount of data to start flushing. With SAS GRID as an example, historically the recommendation was to set `vm.dirty_background` to 1/5 size of `vm.dirty_ratio` or `vm.dirty_bytes`. Considering how aggressively the `vm.dirty_bytes` setting is set for SAS GRID, no specific value is being set here. 
 
 ### `vm.dirty_expire_centisecs` 
 

articles/azure-netapp-files/performance-linux-mount-options.md

@@ -32,7 +32,7 @@ When you use `nconnect`, keep the following rules in mind:
 
     | Linux release | NFSv3 (minimum release) | NFSv4.1 (minimum release) |
     |-|-|-|
-    | Redhat Enterprise Linux | RHEL8.3 | RHEL8.3 |
+    | Red Hat Enterprise Linux | RHEL8.3 | RHEL8.3 |
     | SUSE | SLES12SP4 or SLES15SP1 | SLES15SP2 |
     | Ubuntu | Ubuntu18.04 |          |
 

articles/communication-services/tutorials/includes/twilio-to-acs-chat-ios-tutorial.md

@@ -28,7 +28,7 @@ For more information, see [Use Azure CLI to Create and Manage Access Tokens](../
 
 ### Install the libraries
 
-To start the migration from Twilio Conversations Chat, the first step is to install the Azure Communication Services Chat SDK for iOS to your project. You can configure these parameters using `Cocoapods`.
+To start the migration from Twilio Conversations Chat, the first step is to install the Azure Communication Services Chat SDK for iOS to your project. You can configure these parameters using `CocoaPods`.
 
 1. Create a Podfile for your application. Open the terminal, navigate to the project folder, and run:
 

articles/communication-services/tutorials/includes/twilio-to-acs-video-ios-tutorial.md

@@ -37,7 +37,7 @@ This open source prebuilt set of controls enables you to create aesthetically pl
 
 ## Installation
 
-To start the migration from Twilio Video, the first step is to install the Azure Communication Services Calling SDK for iOS to your project. You can configure these parameters using`Cocoapods`.
+To start the migration from Twilio Video, the first step is to install the Azure Communication Services Calling SDK for iOS to your project. You can configure these parameters using`CocoaPods`.
 
 1. To create a Podfile for your application, open the terminal and navigate to the project folder and run:
 

articles/notification-hubs/ios-sdk-current.md

@@ -58,17 +58,17 @@ configure push credentials in your notification hub. Even if you have no prior e
 
 5. Add the Azure Notification Hubs SDK modules.
 
-   You can integrate the Azure Notification Hubs SDK into your app by using [Cocoapods](https://cocoapods.org/) or by manually adding the binaries to your project.
+   You can integrate the Azure Notification Hubs SDK into your app by using [CocoaPods](https://cocoapods.org/) or by manually adding the binaries to your project.
 
-   - Integration via Cocoapods: Add the following dependencies to your podfile to include Azure Notification Hubs SDK in your app:
+   - Integration via CocoaPods: Add the following dependencies to your podfile to include Azure Notification Hubs SDK in your app:
 
       ```ruby
       pod 'AzureNotificationHubs-iOS'
       ```
 
       - Run pod install to install your newly defined pod and open your .xcworkspace.
 
-         If you see an error such as **Unable to find a specification for AzureNotificationHubs-iOS** while running pod install, run `pod repo update` to get the latest pods from the Cocoapods repository, and then run pod install.
+         If you see an error such as **Unable to find a specification for AzureNotificationHubs-iOS** while running pod install, run `pod repo update` to get the latest pods from the CocoaPods repository, and then run pod install.
 
    - Integration via Carthage: Add the following dependencies to your Cartfile to include the Azure Notification Hubs SDK in your app:
 

articles/openshift/howto-use-lockbox.md

@@ -13,7 +13,7 @@ keywords: azure, openshift, aro, red hat, lockbox
 
 # Authorize support requests for cluster access with Azure Lockbox
 
-In some circumstances, a support agent at Microsoft may need access to your OpenShift cluster resources. The Azure Lockbox feature works with Azure Redhat OpenShift to provide customers a way to review and approve or reject requests from Microsoft support to access their cluster resources. This ability can be important for financial, government, or other regulatory industries where there's extra scrutiny regarding access to resources.
+In some circumstances, a support agent at Microsoft may need access to your OpenShift cluster resources. The Azure Lockbox feature works with Azure Red Hat OpenShift to provide customers a way to review and approve or reject requests from Microsoft support to access their cluster resources. This ability can be important for financial, government, or other regulatory industries where there's extra scrutiny regarding access to resources.
 
 With Azure Lockbox, whenever a support ticket is created, you have the ability to grant consent to Microsoft support agents to access your cluster resources. The actions that the support engineer can take are limited to those [listed below](#aro-lockbox-actions). Azure Lockbox will tell you exactly what action the support agent is trying to execute.
 

articles/sap/center-sap-solutions/faq.yml

@@ -39,7 +39,7 @@ sections:
         answer: | 
                 There's no extra licensing cost for deploying or registering an SAP system and generating a virtual 
                 instance. You pay only for 
-                the compute, storage, networking, Virtual machine OS image license (Redhat/SUSE) and other Azure resources you deploy or enable. 
+                the compute, storage, networking, Virtual machine OS image license (Red Hat/SUSE) and other Azure resources you deploy or enable. 
 
       - question:  Which scenarios does Azure Center for SAP solutions support?
         answer: | 

articles/sap/center-sap-solutions/get-quality-checks-insights.md

@@ -52,7 +52,7 @@ Azure Center for SAP solutions runs more than 100 quality checks on all VIS reso
 - High availability (HA) Load Balancer checks
 - HANA DB file system checks.
 - OS parameter checks for ANF file system.
-- Pacemaker configuration checks for HANA DB and ASCS Instance for SUSE and Redhat 
+- Pacemaker configuration checks for HANA DB and ASCS Instance for SUSE and Red Hat 
 - OS Configuration checks for Application Instances
 
 The table in the **Advisor Recommendations** tab shows all the recommendations for ASCS, Application, and Database instances in the VIS.

articles/site-recovery/site-recovery-whats-new-archive.md

@@ -641,7 +641,7 @@ Features added this month are summarized in the table.
 
 **Feature** | **Details**
 --- | ---
-**Linux support** | Support was added for Redhat Enterprise Linux 7.6, RedHat Workstation 6/7, Oracle Linux 6.10 and Oracle Linux 7.6, and new kernel versions for Ubuntu, Debian, and SUSE.
+**Linux support** | Support was added for Red Hat Enterprise Linux 7.6, RedHat Workstation 6/7, Oracle Linux 6.10 and Oracle Linux 7.6, and new kernel versions for Ubuntu, Debian, and SUSE.
 
 
 ### Update rollup 31