Fix broken link

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

Author: Natalie Arellano

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

@@ -14,16 +14,18 @@ See the [spec release](https://github.com/buildpacks/spec/releases/tag/platform%
 
 In Platform 0.11, the lifecycle ships with standardized SBOM files describing the `lifecycle` and `launcher` binaries
 (these are included in the tarball on the GitHub release page and within the image at `index.docker.io/buildpacksio/lifecycle:<version>`).
-SBOM files describing the `launcher` are included in the application image at `<layers>/sbom/launch/buildpacksio_lifecycle/launcher/sbom.<ext>`,
+
+After a build, SBOM files describing the `launcher` are included in the application image at `<layers>/sbom/launch/buildpacksio_lifecycle/launcher/sbom.<ext>`,
 where `<ext>` is each of: `cdx.json`, `spdx.json`, and `syft.json`.
 Additionally, SBOM files describing the `lifecycle` are copied to `<layers>/sbom/build/buildpacksio_lifecycle/sbom.<ext>`,
 where they may be saved off by the platform prior to the build container exiting.
 
 This mirrors what is already being done as of Platform 0.8 for buildpack-provided standardized SBOM files,
 which are exported to `<layers>/sbom/launch/<buildpack-id>/<layer>/sbom.<ext>` (for runtime dependencies)
 and copied to `<layers>/sbom/launch/<buildpack-id>/sbom.<ext>` (for build-time dependencies).
-Platforms that are already handling these files should not need to take additional action -
-the resulting SBOMs will simply be more complete.
+
+To use this feature, no additional action is required from platforms that are already handling buildpack-provided SBOM files.
+The SBOMs for the image will simply be more complete.
 
 ### The rebaser accepts a -previous-image flag to allow rebasing by digest reference
 

content/docs/reference/spec/migration/platform-api-0.11-0.12.md

@@ -57,19 +57,24 @@ If `-force` is not provided,
 
 In Platform 0.12, extensions can be used to extend not only build-time base images, but runtime base images as well.
 
+#### During build
+
 To use the feature, platforms should:
 * Invoke `analyzer` as usual for Platform 0.12
 * Invoke `detector` with the `-run` flag, to specify the location of a `run.toml` file containing run image information
   * When extensions switch the run image, this is used to log a warning if the new run image is not a known run image
 * Invoke `restorer` with the `-dameon` flag (newly added in this Platform API version) if the export target is a daemon
   * When extensions switch the run image, the `restorer` must re-read target data from the new run image in order to provide this information to buildpacks; if `-daemon` is provided the `restorer` will look for the run image in a daemon instead of a registry
   * When extensions extend the run image, the `-daemon` flag has no effect as the `restorer` must be able to pull the run image manifest from a registry
-* Invoke `extender` as usual to extend the builder image (see [migration guide](TODO) for Platform 0.10)
+* Invoke `extender` as usual to extend the builder image (see [migration guide](/docs/reference/spec/migration/platform-api-0.9-0.10/index.html) for Platform 0.10)
 * Inspect the contents of `analyzed.toml` - if `run-image.extend` is `true` we must run the `extender` on the run image
 * Using the **run image** as the basis for the container, invoke `extender` with flags `-kind run` and `-extended <extended dir>`
   * `<extended dir>` is the directory where layers from applying each `run.Dockerfile` to the run image will be saved for use by the `exporter`; it defaults to `<layers>/extended`
+  * Run image extension may be done in parallel with builder image extension
 * Invoke `exporter` with the `-extended` flag
 
+#### After build
+
 Note that unlike buildpack-provided layers, layers from extensions may NOT be safe to rebase.
 The `io.buildpacks.rebasable` label on the exported application image will be `false` if rebase is unsafe.
 The `-force` flag must be provided to the `rebaser` in order to rebase images with unsafe extension layers,