Merge pull request #266319 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: v-alje

articles/role-based-access-control/scope-overview.md

@@ -44,7 +44,7 @@ The scope consists of a series of identifiers separated by the slash (/) charact
 ```
 
 - `{subscriptionId}` is the ID of the subscription to use (a GUID).
-- `{resourcesGroupName}` is the name of the containing resource group.
+- `{resourceGroupName}` is the name of the containing resource group.
 - `{providerName}` is the name of the [resource provider](../azure-resource-manager/management/azure-services-resource-providers.md) that handles the resource, then `{resourceType}` and `{resourceSubType*}` identify further levels within that resource provider.
 - `{resourceName}` is the last part of the string that identifies a specific resource.
 

articles/sap/workloads/high-availability-guide-suse-pacemaker.md

@@ -470,21 +470,13 @@ If you want to deploy resources by using the Azure CLI or the Azure portal, you
 
 ### Set up an Azure shared disk SBD device
 
-1. **[A]** Install iSCSI package.
-
-   ```bash
-   sudo zypper install open-iscsi
-   ```
-
-2. **[A]** Enable the iSCSI and SBD services.
+1. **[A]** Enable the SBD services.
 
    ```bash
-   sudo systemctl enable iscsid
-   sudo systemctl enable iscsi
    sudo systemctl enable sbd
    ```
 
-3. **[A]** Make sure that the attached disk is available.
+2. **[A]** Make sure that the attached disk is available.
 
    ```bash
    # lsblk
@@ -507,7 +499,7 @@ If you want to deploy resources by using the Azure CLI or the Azure portal, you
    [5:0:0:0]    disk    Msft     Virtual Disk     1.0   /dev/sdc
    ```
 
-4. **[A]** Retrieve the IDs of the attached disks.
+3. **[A]** Retrieve the IDs of the attached disks.
 
    ```bash
    # ls -l /dev/disk/by-id/scsi-* | grep sdc
@@ -517,15 +509,15 @@ If you want to deploy resources by using the Azure CLI or the Azure portal, you
 
    The commands list device IDs for the SBD device. We recommend using the ID that starts with scsi-3. In the preceding example, the ID is **/dev/disk/by-id/scsi-3600224804208a67da8073b2a9728af19**.
 
-5. **[1]** Create the SBD device.
+4. **[1]** Create the SBD device.
 
    Use the device ID from step 2 to create the new SBD devices on the first cluster node.
 
    ```bash
    # sudo sbd -d /dev/disk/by-id/scsi-3600224804208a67da8073b2a9728af19 -1 60 -4 120 create
    ```
 
-6. **[A]** Adapt the SBD configuration.
+5. **[A]** Adapt the SBD configuration.
 
    a. Open the SBD config file.
 
@@ -548,13 +540,13 @@ If you want to deploy resources by using the Azure CLI or the Azure portal, you
     > [!NOTE]
     > If the SBD_DELAY_START property value is set to "no", change the value to "yes". You must also check the SBD service file to ensure that the value of TimeoutStartSec is greater than the value of SBD_DELAY_START. For more information, see [SBD file configuraton](https://documentation.suse.com/sle-ha/15-SP5/html/SLE-HA-all/cha-ha-storage-protect.html#pro-ha-storage-protect-sbd-config)
 
-7. Create the `softdog` configuration file.
+6. Create the `softdog` configuration file.
 
    ```bash
    echo softdog | sudo tee /etc/modules-load.d/softdog.conf
    ```
 
-8. Load the module.
+7. Load the module.
 
    ```bash
    sudo modprobe -v softdog