Merge pull request #235515 from AlizaBernstein/patch-upcoming-change-mdvm

patch-Update upcoming-changes-mdvm

Author: prmerger-automator[bot]

articles/defender-for-cloud/upcoming-changes.md

@@ -87,15 +87,15 @@ The existing recommendation "Container registry images should have vulnerability
 |--|--|--|
 | Container registry images should have vulnerability findings resolved (powered by Microsoft Defender Vulnerability Management)| Container image vulnerability assessment scans your registry for commonly known vulnerabilities (CVEs) and provides a detailed vulnerability report for each image. This recommendation provides visibility to vulnerable images currently running in your Kubernetes clusters. Remediating vulnerabilities in container images that are currently running is key to  improving your security posture, significantly reducing the attack surface for your containerized workloads. |dbd0cb49-b563-45e7-9724-889e799fa648 <br> is replaced by  c0b7cfc6-3172-465a-b378-53c7ff2cc0d5
 
-The recommendation "Running container images should have vulnerability findings resolved" (assessment key 41503391-efa5-47ee-9282-4eff6131462c) is temporarily removed and will be replaced soon by a new recommendation powered by MDVM.
+The recommendation "Running container images should have vulnerability findings resolved" (assessment key 41503391-efa5-47ee-9282-4eff6131462c) will be temporarily removed and will be replaced soon by a new recommendation powered by MDVM.
 
 Learn more about [Microsoft Defender Vulnerability Management (MDVM)](https://learn.microsoft.com/microsoft-365/security/defender-vulnerability-management/defender-vulnerability-management).
 
 ### Renaming container recommendations powered by Qualys
 
 **Estimated date for change: May 2023**
 
- The current container recommendations in Defender for Containers are renamed as follows:
+ The current container recommendations in Defender for Containers will be renamed as follows:
 
 |Recommendation | Description | Assessment Key|
 |--|--|--|