Update agentless-container-registry-vulnerability-assessment.md

Author: tspivakms

articles/defender-for-cloud/agentless-container-registry-vulnerability-assessment.md

@@ -40,15 +40,15 @@ The triggers for an image scan are:
 
 - **One-time triggering**:
   - each image pushed or imported to a container registry is scanned shortly after being pushed or imported to a registry. In most cases, the scan is completed within a few minutes, but sometimes it may take up to an hour.
-  - [preview] each image pulled from a registry is scanned shortly after being pulled from a registry.In most cases, the scan is completed within a few minutes, but sometimes it may take up to an hour.
+  - [Preview] each image pulled from a registry is triggered to be scanned within 24 hours.
 
   > [!NOTE]
   > While Container vulnerability assessment powered by MDVM is generally available for Defender CSPM, scan-on-push and scan-on-pull is currently in public preview.
 
 - **Continuous rescan triggering** – Continuous rescan is required to ensure images that have been previously scanned for vulnerabilities are rescanned to update their vulnerability reports in case a new vulnerability is published.
   - **Re-scan** is performed once a day for:  
     - images pushed in the last 90 days.
-    - [preview] images pulled in the last 30 days.
+    - [Preview] images pulled in the last 30 days.
     - images currently running on the Kubernetes clusters monitored by Defender for Cloud (either via [agentless discovery and visibility for Kubernetes](how-to-enable-agentless-containers.md) or the [Defender agent](tutorial-enable-containers-azure.md#deploy-the-defender-agent-in-azure)).
 
   > [!NOTE]