Merge pull request #9917 from ryanberg-aquent/CI-7894-p1-warning-updates

AB#7894 - Azure build warnings - P1 changes

Author: ryanberg-aquent

support/azure/virtual-desktop/welcome-virtual-desktop.yml

@@ -7,7 +7,7 @@ metadata:
   title: Troubleshoot common issues with Azure Virtual Desktop
   description: Documentation for troubleshooting common issues with Azure Virtual Desktop. # Required; article description that is displayed in search results. < 160 chars.
   ms.topic: landing-page # Required
-  
+  ms.author: jarrettr
   ms.reviewer: kaushika #Required; microsoft alias of author; optional team alias.
   ms.date: 01/17/2025
 

support/azure/virtual-machines/linux/troubleshoot-pacemaker-services-suse.md

@@ -453,7 +453,7 @@ Pacemaker can't start the SAP HANA resource if `SYN failures` exist between the
       site id: 2
       site name: node-2
       active primary site: 1
-      primary masters: node-1
+      primary master: node-1
       ```
 
 5. You can also verify the SAP HANA system replication by running the following command:

support/azure/virtual-machines/linux/troubleshoot-rhel-pacemaker-cluster-services-resources-startup-issues.md

@@ -483,7 +483,7 @@ When you run the `sudo pcs status --full` command, the `node attributes` status
       * hana_XXX_version			          : 2.00.079.00
       * hana_XXX_vhost				          : node-1
       * lpa_XXX_lpt				              : 1733552029
-      * master-SAPHana_XXX_00		        : 150
+      * mastery-SAPHana_XXX_00		        : 150
   ```
 
 This Migration summary indicates that the SAP HANA resource (SAPHana_XXX_00) failed to start on both nodes (node-0 and node-1). The fail count is set to 1000000 (infinity). 

support/azure/virtual-machines/windows/serial-console-power-options.md

@@ -26,7 +26,7 @@ Serial Console feature | Description | Use case
 Restart VM | A graceful restart of your VM or virtual machine scale set instance. This operation is the same as calling the restart feature that's available in the Overview page. | In most cases, this option should be your primary tool when you try to restart your VM. When you use this option, your Serial Console connection experiences a brief interruption, and then automatically resumes when the VM restarts.
 Reset VM | A forceful power cycle of your VM or virtual machine scale that's set by the Azure platform. | This option is used to immediately restart your OS regardless of its current state. Because this operation isn't graceful, there's a risk of data loss or corruption. There's no interruption in the Serial Console connection. This condition is useful for sending commands early during startup (for example, getting to GRUB on a Linux VM or to Safe Mode in a Windows VM).
 SysRq - Reboot (b) | A system request to force a guest restart. | This feature is applicable to only Linux systems, and requires [SysRq to be enabled](../linux/serial-console-nmi-sysrq.md#system-request-sysrq) in the OS. If the system is correctly configured for SysRq, this command causes the OS to restart.
-NMI (Non-maskable Interrupt) | An interrupt command that's delivered to the OS. | This operation is available for both [Windows](./serial-console-windows.md#use-the-serial-console-for-nmi-calls) and [Linux](../linux/serial-console-nmi-sysrq.md#nonmaskable-interrupt-nmi) VMs. It requires NMI to be enabled. Sending an NMI typically causes your system to stop responding. You can configure your system to create a dump file and then restart upon receiving the NMI. This condition might be useful in low-level debugging.
+NMI (Non-maskable Interrupt) | An interrupt command that's delivered to the OS. | This operation is available for both [Windows](./serial-console-windows.md#use-the-serial-console-for-nmi-calls) and [Linux](../linux/serial-console-nmi-sysrq.md#non-maskable-interrupt-nmi) VMs. It requires NMI to be enabled. Sending an NMI typically causes your system to stop responding. You can configure your system to create a dump file and then restart upon receiving the NMI. This condition might be useful in low-level debugging.
 
 ## Next steps