Update name of container image vulnerability recommendation; specify powered by Qualys

Author: bmansheim

articles/defender-for-cloud/defender-for-container-registries-usage.md

@@ -11,7 +11,7 @@ author: ElazarK
 
 [!INCLUDE [Banner for top of topics](./includes/banner.md)]
 
-This page explains how to use the built-in vulnerability scanner to scan the container images stored in your Azure Resource Manager-based Azure Container Registry.
+This page explains how to use the built-in vulnerability scanner, powered by Qualys, to scan the container images stored in your Azure Resource Manager-based Azure Container Registry.
 
 When **Defender for Containers** is enabled, any image you push to your registry will be scanned immediately. In addition, any image pulled within the last 30 days is also scanned.
 
@@ -47,7 +47,7 @@ To enable vulnerability scans of images stored in your Azure Resource Manager-ba
 
 ## View and remediate findings
 
-1. To view the findings, open the **Recommendations** page. If issues were found, you'll see the recommendation [Container registry images should have vulnerability findings resolved (powered by Qualys)](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/dbd0cb49-b563-45e7-9724-889e799fa648).
+1. To view the findings, open the **Recommendations** page. If issues were found, you'll see the recommendation [Container registry images should have vulnerability findings resolved](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/dbd0cb49-b563-45e7-9724-889e799fa648).
 
     ![Recommendation to remediate issues .](media/monitor-container-security/acr-finding.png)
 
@@ -89,7 +89,7 @@ To enable vulnerability scans of images stored in your Azure Resource Manager-ba
 
     1. Push the updated image to trigger a scan.
 
-    1. Check the recommendations page for the recommendation [Container registry images should have vulnerability findings resolved (powered by Qualys)](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/dbd0cb49-b563-45e7-9724-889e799fa648).
+    1. Check the recommendations page for the recommendation [Container registry images should have vulnerability findings resolved](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/dbd0cb49-b563-45e7-9724-889e799fa648).
 
         If the recommendation still appears and the image you've handled still appears in the list of vulnerable images, check the remediation steps again.
 
@@ -125,7 +125,7 @@ You can use any of the following criteria:
 
 To create a rule:
 
-1. From the recommendations detail page for [Container registry images should have vulnerability findings resolved (powered by Qualys)](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/dbd0cb49-b563-45e7-9724-889e799fa648), select **Disable rule**.
+1. From the recommendations detail page for [Container registry images should have vulnerability findings resolved](https://portal.azure.com/#blade/Microsoft_Azure_Security/RecommendationsBlade/assessmentKey/dbd0cb49-b563-45e7-9724-889e799fa648), select **Disable rule**.
 1. Select the relevant scope.
 1. Define your criteria.
 1. Select **Apply rule**.