From e7c4cc622ed6545d36e501277f7dac9b37f29ccb Mon Sep 17 00:00:00 2001 From: Megan Marsh Date: Tue, 30 Apr 2019 11:56:56 +0200 Subject: [PATCH] Update website/source/docs/extending/custom-post-processors.html.md Co-Authored-By: azr --- website/source/docs/extending/custom-post-processors.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/extending/custom-post-processors.html.md b/website/source/docs/extending/custom-post-processors.html.md index c4bc34544..e940047b3 100644 --- a/website/source/docs/extending/custom-post-processors.html.md +++ b/website/source/docs/extending/custom-post-processors.html.md @@ -69,7 +69,7 @@ validates, but will never actually run the build. The `PostProcess` method is where the real work goes. PostProcess is responsible for taking one `packer.Artifact` implementation, and transforming it into another. -A `PostProcess` call can be cancelled at any moment, cancellation is triggered +A `PostProcess` call can be cancelled at any moment. Cancellation is triggered when the done chan of the context struct (`<-ctx.Done()`) unblocks . When we say "transform," we don't mean actually modifying the existing