AWS AWSEC2: Simplify AMI creation reboot rationale wording
Summary
Removed 'in order to' for brevity in snapshot consistency explanation.
Security assessment
Linguistic simplification without altering the security-relevant concept of consistent snapshots.
Evidence
- * If **Reboot instance** is selected, when Amazon EC2 creates the new AMI, it reboots the instance so that it can take snapshots of the attached volumes while data is at rest, in order to ensure a consistent state.
Diff
diff --git a/AWSEC2/latest/UserGuide/creating-an-ami-ebs.md b/AWSEC2/latest/UserGuide/creating-an-ami-ebs.md index f4ad9b1f2..dbb656670 100644 --- a//AWSEC2/latest/UserGuide/creating-an-ami-ebs.md +++ b//AWSEC2/latest/UserGuide/creating-an-ami-ebs.md @@ -125 +125 @@ If this option is disabled, your instance isn't an Amazon EBS-backed instance. - * If **Reboot instance** is selected, when Amazon EC2 creates the new AMI, it reboots the instance so that it can take snapshots of the attached volumes while data is at rest, in order to ensure a consistent state. + * If **Reboot instance** is selected, when Amazon EC2 creates the new AMI, it reboots the instance so that it can take snapshots of the attached volumes while data is at rest, to ensure a consistent state.