Merge pull request #121093 from Rageking8/fix-necessary-typos

Fix necessary typos

Author: ShannonLeavitt

articles/azure-vmware/vulnerability-management.md

@@ -7,7 +7,6 @@ ms.date: 3/22/2024
 ms.custom: engagement-fy24
 ---
 
-
 # How Azure VMware Solution Addresses Vulnerabilities in the Infrastructure
 
 At a high level, Azure VMware Solution is a Microsoft Azure service and therefore must follow all the same policies and requirements that Azure follows. Azure policies and procedures dictate that Azure VMware Solution must follow the [SDL](https://www.microsoft.com/securityengineering/sdl) and must meet several regulatory requirements as promised by Microsoft Azure. 
@@ -22,16 +21,17 @@ Azure VMware Solution takes a defense in depth approach to vulnerability and ris
 - Details within the signal are adjudicated and assigned a CVSS score and risk rating according to compensating controls within the service.
 - The risk rating is used against internal bug bars, internal policies and regulations to establish a timeline for implementing a fix.
 - Internal engineering teams partner with appropriate parties to qualify and roll out any fixes, patches and other configuration updates necessary.
-- Communications are drafted when necassary and published according to the risk rating assigned.
->[!tip]
->Communications are surfaced through [Azure Service Health Portal](/azure/service-health/service-health-portal-update), [Known Issues](/azure/azure-vmware/azure-vmware-solution-known-issues) or Email. 
+- Communications are drafted when necessary and published according to the risk rating assigned.
+
+> [!TIP]
+> Communications are surfaced through [Azure Service Health Portal](/azure/service-health/service-health-portal-update), [Known Issues](/azure/azure-vmware/azure-vmware-solution-known-issues) or Email. 
 
 ### Subset of regulations governing vulnerability and risk management
 
 Azure VMware Solution is in scope for the following certifications and regulatory requirements. The regulations listed aren't a complete list of certifications Azure VMware Solution holds, rather it's a list with specific requirements around vulnerability management. These regulations don't rely on other regulations for the same purpose. IE, certain regional certifications may point to ISO requirements for vulnerability management.
 
->[!NOTE]
->To access the following audit reports hosted in the Service Trust Portal, you must be an active Microsoft customer.
+> [!NOTE]
+> To access the following audit reports hosted in the Service Trust Portal, you must be an active Microsoft customer.
 
 - [ISO](https://servicetrust.microsoft.com/DocumentPage/38a05a38-6181-432e-a5ec-aa86008c56c9)
 - [PCI](https://servicetrust.microsoft.com/viewpage/PCI) \- See the packages for DSS and 3DS for Audit Information.

articles/frontdoor/standard-premium/how-to-add-custom-domain.md

@@ -100,7 +100,7 @@ After you validate your custom domain, you can associate it to your Azure Front
 
     > [!NOTE]
     > * If HTTPS is enabled, certificate provisioning and propagation may take a few minutes because propagation is being done to all edge locations.
-    > * If your domain CNAME is indirectly pointed to a Front Door endpoint, for example, using Azure Traffic Manager for multi-CDN failover, the **DNS state** column shows as **CNAME/Alias record currently not detected**. Azure Front Door can't guarantee 100% detection of the CNAME record in this case. If you've configured an Azure Front Door endpoint to Azure Traffic Manager and still see this message, it doesn’t mean you didn't set up correctly, therefore further no action is neccessary from your side.
+    > * If your domain CNAME is indirectly pointed to a Front Door endpoint, for example, using Azure Traffic Manager for multi-CDN failover, the **DNS state** column shows as **CNAME/Alias record currently not detected**. Azure Front Door can't guarantee 100% detection of the CNAME record in this case. If you've configured an Azure Front Door endpoint to Azure Traffic Manager and still see this message, it doesn’t mean you didn't set up correctly, therefore further no action is necessary from your side.
 
 ## Verify the custom domain