AWS simspaceweaver documentation change
Summary
Changed 'AWS CloudFormation' to 'CloudFormation' in stack deletion instructions and resource warnings
Security assessment
Purely cosmetic updates to product naming. No security vulnerabilities addressed and no new security documentation added. Existing resource cleanup warnings remain functionally identical.
Diff
diff --git a/simspaceweaver/1.16/userguide/getting-started_quickstart_stop-and-clean.md b/simspaceweaver/1.16/userguide/getting-started_quickstart_stop-and-clean.md index 879caa4ff..35f4ec4e1 100644 --- a//simspaceweaver/1.16/userguide/getting-started_quickstart_stop-and-clean.md +++ b//simspaceweaver/1.16/userguide/getting-started_quickstart_stop-and-clean.md @@ -131 +131 @@ You might get billing charges for any of these resources that you don't delete. - 1. If you are done with your **project** , delete its AWS CloudFormation stack. For more information about working with AWS CloudFormation, see [Deleting a stack on the AWS CloudFormation console](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-console-delete-stack.html) in the _AWS CloudFormation User Guide_. + 1. If you are done with your **project** , delete its CloudFormation stack. For more information about working with AWS CloudFormation, see [Deleting a stack on the AWS CloudFormation console](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-console-delete-stack.html) in the _AWS CloudFormation User Guide_. @@ -137 +137 @@ You might get billing charges for any of these resources that you don't delete. -Simulations that you started from the same project share resources such as the app role. When you delete the AWS CloudFormation stack, you delete the app role. Don't delete your AWS CloudFormation stack if you have other simulations that share the same resources. +Simulations that you started from the same project share resources such as the app role. When you delete the CloudFormation stack, you delete the app role. Don't delete your CloudFormation stack if you have other simulations that share the same resources. @@ -141 +141 @@ Simulations that you started from the same project share resources such as the a -Your AWS CloudFormation stack will probably report `DELETE_FAILED` because it can't delete Amazon S3 buckets that aren't empty. You will delete your Amazon S3 buckets in the following step. +Your CloudFormation stack will probably report `DELETE_FAILED` because it can't delete Amazon S3 buckets that aren't empty. You will delete your Amazon S3 buckets in the following step.