AWS lambda documentation change
Summary
Minor editorial changes to wording (removed possessive form from Lambda references)
Security assessment
Changes are grammatical improvements without security implications. No security content added or modified.
Diff
diff --git a/lambda/latest/dg/microvms-images.md b/lambda/latest/dg/microvms-images.md index 49cf27a2e..c9a49c5ca 100644 --- a//lambda/latest/dg/microvms-images.md +++ b//lambda/latest/dg/microvms-images.md @@ -118 +118 @@ You can update an existing MicroVM image by calling the `update-microvm-image` A - * **Move to a newer MicroVM base image** – Change the MicroVM base image ARN to upgrade to newer versions of Lambda's MicroVM base image. For more information, refer to MicroVM image patching and MicroVM base images. + * **Move to a newer MicroVM base image** – Change the MicroVM base image ARN to upgrade to newer versions of the Lambda MicroVM base image. For more information, refer to MicroVM image patching and MicroVM base images. @@ -185 +185 @@ Lambda MicroVMs runs your application as a container within the MicroVM operatin -You can either start with Lambda's base container image for Amazon Linux 2023 (`public.ecr.aws/lambda/microvms:al2023-minimal`) and add your `Dockerfile` instructions on top of this, or use your own base container image. When using your own container images, validate the following requirements: +You can either start with the Lambda base container image for Amazon Linux 2023 (`public.ecr.aws/lambda/microvms:al2023-minimal`) and add your `Dockerfile` instructions on top of this, or use your own base container image. When using your own container images, validate the following requirements: