From baa83c4920f1ef25504efafbc1a612304a38373e Mon Sep 17 00:00:00 2001 From: Terence Lee Date: Wed, 12 Apr 2023 13:37:57 -0700 Subject: [PATCH] Update text/0000-execution-environments.md Co-authored-by: Josh W Lewis Signed-off-by: Terence Lee --- text/0000-execution-environments.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/0000-execution-environments.md b/text/0000-execution-environments.md index 9df603208..e500c4377 100644 --- a/text/0000-execution-environments.md +++ b/text/0000-execution-environments.md @@ -22,7 +22,7 @@ Add support for different execution environments for buildpacks, with testing as # Motivation [motivation]: #motivation -The main way Buildpacks are being used is building production images, but this is only one piece of the CI/CD pipeline. Without a solid buildpack test environment story, users will be required alternatives for building their environment. A testing environment, while different, shares many of the same broad strokes ultimately producing an execution environment. This is something Buildpacks are well suited to solve. +The main way Buildpacks are being used is building production images, but this is only one piece of the software development process. Without a solid buildpack test environment story, users will be required alternatives for building their environment. A testing environment, while different, shares many of the same broad strokes ultimately producing an execution environment. This is something Buildpacks are well suited to solve. # What it is [what-it-is]: #what-it-is