Skip to content

Commit ed1fa13

Browse files
Merge pull request #261982 from dcurwin/patch-171
fix typos
2 parents 55cd97e + 9554da2 commit ed1fa13

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/defender-for-cloud/agentless-vulnerability-assessment-aws.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ In every account where enablement of this capability is completed, all images st
1818

1919
Container vulnerability assessment powered by Microsoft Defender Vulnerability Management has the following capabilities:
2020

21-
- **Scanning OS packages** - container vulnerability assessment has the ability to scan vulnerabilities in packages installed by the OS package manager in Linux and Windows OS. See the [full list of the supported OS and their versions](support-matrix-defender-for-containers.md#registries-and-images-support-for-aws---vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management).
21+
- **Scanning OS packages** - container vulnerability assessment has the ability to scan vulnerabilities in packages installed by the OS package manager in Linux and Windows operating systems. See the [full list of the supported OS and their versions](support-matrix-defender-for-containers.md#registries-and-images-support-for-aws---vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management).
2222

2323
- **Language specific packages****Linux only** - support for language specific packages and files, and their dependencies installed or copied without the OS package manager. See the [complete list of supported languages](support-matrix-defender-for-containers.md#registries-and-images-support-for-aws---vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management).
2424

@@ -40,7 +40,7 @@ Container vulnerability assessment powered by Microsoft Defender Vulnerability M
4040
The triggers for an image scan are:
4141

4242
- **One-time triggering**:
43-
- Each image pushed to a container registry is triggered to be scanned. In most cases, the scan is completed within a few hours, but sometin rare cases it might take up to 24 hors.
43+
- Each image pushed to a container registry is triggered to be scanned. In most cases, the scan is completed within a few hours, but in rare cases it might take up to 24 hours.
4444
- Each image pulled from a registry is triggered to be scanned within 24 hours.
4545

4646

0 commit comments

Comments
 (0)