Minor edits

Signed-off-by: Natalie Arellano <[email protected]>

Author: Natalie Arellano

content/docs/reference/spec/migration/buildpack-api-0.8-0.9.md

@@ -26,4 +26,6 @@ For older platforms (platform API version 0.9 and below), arguments in `args` wi
 
 ### Image extensions are supported (experimental)
 
-TODO
+Platform 0.10 introduces image extensions as experimental components for customizing build and run-time base images (see [here][TODO] for more information).
+
+For more information, see [authoring an image extension][TODO].

content/docs/reference/spec/migration/platform-api-0.9-0.10.md

@@ -69,6 +69,7 @@ Platform 0.10 introduces image extensions as experimental components for customi
 Note: image extensions are not supported for Windows container images.
 
 * To create a builder with extensions, ensure the `pack` version in use is at least TODO and enable experimental features: `pack config experimental`.
+* Enable experimental features in the lifecycle by setting `CNB_EXPERIMENTAL_MODE=warn` or `CNB_EXPERIMENTAL_MODE=silent` in the lifecycle execution environment for ALL lifecycle phases
 * Invoke `analyzer` as usual
 * Invoke `detector` with a new optional argument: `-generated`, to specify the directory where Dockerfiles generated by image extensions will be output (defaults to `<layers>/generated`) and include image extensions in `order.toml`
   * Dockerfiles for customizing the build image can be found in `<generated>/build/<image extension ID>/Dockerfile`