AWS guardduty documentation change
Summary
Fixed typo in 'doesn''t' to 'doesn't'
Security assessment
The change is a grammatical correction with no security implications.
Diff
diff --git a/guardduty/latest/ug/supported-s3-features-malware-protection-s3.md b/guardduty/latest/ug/supported-s3-features-malware-protection-s3.md index 6ef3de6af..9aade1535 100644 --- a//guardduty/latest/ug/supported-s3-features-malware-protection-s3.md +++ b//guardduty/latest/ug/supported-s3-features-malware-protection-s3.md @@ -32 +32 @@ Client side encryption | No | When your Amazon S3 objects are encrypted by usi -CSE-KMS encrypted objects are received as an encrypted blob where the encryption can't be determined. Therefore, GuardDuty processes them as they are received, and scans the encrypted blob as a regular file. GuardDuty doesn''t return an `UNSUPPORTED` scan status for such objects, unless any of the [Quotas in Malware Protection for S3](./malware-protection-s3-quotas-guardduty.html) exceeds. +CSE-KMS encrypted objects are received as an encrypted blob where the encryption can't be determined. Therefore, GuardDuty processes them as they are received, and scans the encrypted blob as a regular file. GuardDuty doesn't return an `UNSUPPORTED` scan status for such objects, unless any of the [Quotas in Malware Protection for S3](./malware-protection-s3-quotas-guardduty.html) exceeds.