Fix broken links

Natalie Arellano · Natalie Arellano · commit 06d109d96700 · 2024-02-13T15:25:20.000-05:00
Signed-off-by: Natalie Arellano &lt;narellano@vmware.com&gt;
diff --git a/content/docs/app-journey.md b/content/docs/app-journey.md
@@ -99,7 +99,7 @@ deploying your new image to your favorite cloud!
 
 Windows image builds are now supported!
 
-<a href="/docs/for-app-developers/how-to/configure-build/build-for-windows" class="button bg-blue">Windows build guide</a>
+<a href="/docs/for-app-developers/how-to/configure-build-environment/build-for-windows" class="button bg-blue">Windows build guide</a>
 
 [builder]: /docs/concepts/components/builder/
 [buildpack]: /docs/concepts/components/buildpack/
diff --git a/content/docs/concepts/operations/rebase.md b/content/docs/concepts/operations/rebase.md
@@ -30,4 +30,4 @@ $ pack rebase my-app:my-tag
 > **TIP:** `pack rebase` has a `--publish` flag that can be used to publish the updated app image directly to a registry. 
 > Using `--publish` is optimal when using a registry in comparison to the docker daemon.
 
-[build]: /docs/for-app-developers/tutorials/build-basic-app/
+[build]: /docs/for-app-developers/tutorials/basic-app/
diff --git a/content/docs/for-app-developers/how-to/configure-build-environment/build-for-windows.md b/content/docs/for-app-developers/how-to/configure-build-environment/build-for-windows.md
@@ -129,7 +129,7 @@ curl http://10.0.0.1:8080
 [container-mode]: https://docs.docker.com/desktop/faqs/windowsfaqs/#how-do-i-switch-between-windows-and-linux-containers
 [docker-env-vars]: https://docs.docker.com/engine/reference/commandline/cli/#environment-variables
 [docker-hosts]: #understanding-docker-hosts
-[build-linux]: /docs/for-app-developers/tutorials/build-basic-app
+[build-linux]: /docs/for-app-developers/tutorials/basic-app
 [build]: /docs/concepts/operations/build
 [builder]: /docs/concepts/components/builder
 [buildpack]: /docs/concepts/components/buildpack
diff --git a/content/docs/for-app-developers/how-to/configure-build-environment/export-to-oci-layout.md b/content/docs/for-app-developers/how-to/configure-build-environment/export-to-oci-layout.md
@@ -39,7 +39,7 @@ to save images requires by `pack build` command in OCI layout format.
 
 ### 2. Build the app
 
-Please first follow the steps to [build an app](/docs/for-app-developers/tutorials/build-basic-app), once you have successfully built an application you can export the sample application to disk in OCI layout format. 
+Please first follow the steps to [build an app](/docs/for-app-developers/tutorials/basic-app), once you have successfully built an application you can export the sample application to disk in OCI layout format. 
 
 The OCI layout feature must be enabled using the convention `oci:<path/to/save/image>` in the `<image-name>` parameter when invoking `pack build`.
 
diff --git a/content/docs/for-app-developers/how-to/configure-build-inputs/buildpacks.md b/content/docs/for-app-developers/how-to/configure-build-inputs/buildpacks.md
@@ -110,5 +110,5 @@ A buildpack located in a CNB Registry
 <small><sup>†</sup> Directory buildpacks are not currently supported on Windows.</small><br />
 <small><sup>‡</sup> Version may be omitted if there is only one buildpack in the builder matching the `id`.</small>
 
-[project-toml]: /docs/for-app-developers/how-to/build-inputs/use-project-toml/
+[project-toml]: /docs/for-app-developers/how-to/configure-build-inputs/project-toml/
 [samples]: https://github.com/buildpacks/samples
diff --git a/content/docs/for-app-developers/how-to/configure-build-inputs/inline-buildpacks.md b/content/docs/for-app-developers/how-to/configure-build-inputs/inline-buildpacks.md
@@ -54,6 +54,6 @@ EOF
 ### Further Reading
 For more about project descriptors, look at the [schema][descriptor-schema], as well as the [specification][spec].
 
-[project-toml]: /docs/for-app-developers/how-to/build-inputs/use-project-toml/
+[project-toml]: /docs/for-app-developers/how-to/configure-build-inputs/project-toml/
 [descriptor-schema]: /docs/reference/project-descriptor/
 [spec]: https://github.com/buildpacks/spec/blob/main/extensions/project-descriptor.md
diff --git a/content/docs/for-app-developers/how-to/configure-build-inputs/project-toml.md b/content/docs/for-app-developers/how-to/configure-build-inputs/project-toml.md
@@ -106,8 +106,8 @@ docker run sample-app
 ### Further Reading
 For more about project descriptors, look at the [schema][descriptor-schema], as well as the [specification][spec].
 
-[specify-buildpacks]: /docs/for-app-developers/how-to/build-inputs/specify-buildpacks-from-cli
-[descriptor-envs]: /docs/for-app-developers/how-to/build-inputs/configure-build-time-environment/#using-project-descriptor
+[specify-buildpacks]: /docs/for-app-developers/how-to/configure-build-inputs/buildpacks
+[descriptor-envs]: /docs/for-app-developers/how-to/configure-build-inputs/build-time-environment/#using-project-descriptor
 [descriptor-schema]: /docs/reference/project-descriptor/
 [samples]: https://github.com/buildpacks/samples
 [spec]: https://github.com/buildpacks/spec/blob/main/extensions/project-descriptor.md
diff --git a/content/docs/for-app-developers/tutorials/basic-app/build.md b/content/docs/for-app-developers/tutorials/basic-app/build.md
@@ -67,21 +67,21 @@ The app should now be running and accessible via [localhost:8080](http://localho
 Linux ARM image builds are now supported!
 
 <!--+- if false+-->
-<a href="/docs/for-app-developers/how-to/configure-build/build-for-arm" class="button bg-blue">Linux ARM build guide</a>
+<a href="/docs/for-app-developers/how-to/configure-build-environment/build-for-arm" class="button bg-blue">Linux ARM build guide</a>
 <!--+end+-->
 
 <!--+ `
-Check out the [Linux ARM build guide](https://buildpacks.io//docs/for-app-developers/how-to/configure-build/build-for-arm).
+Check out the [Linux ARM build guide](https://buildpacks.io//docs/for-app-developers/how-to/configure-build-environment/build-for-arm).
 ` +-->
 ## What about Windows apps?
 
 Windows image builds are now supported!
 
 <!--+- if false+-->
-<a href="/docs/for-app-developers/how-to/configure-build/build-for-windows" class="button bg-blue">Windows build guide</a>
+<a href="/docs/for-app-developers/how-to/configure-build-environment/build-for-windows" class="button bg-blue">Windows build guide</a>
 <!--+end+-->
 <!--+ `
-Check out the [Windows build guide](https://buildpacks.io/docs/for-app-developers/how-to/configure-build/build-for-windows/).
+Check out the [Windows build guide](https://buildpacks.io/docs/for-app-developers/how-to/configure-build-environment/build-for-windows/).
 ` +-->
 
 [build]: /docs/concepts/operations/build
diff --git a/content/docs/for-buildpack-authors/how-to/migrate/buildpack-api-0.8-0.9.md b/content/docs/for-buildpack-authors/how-to/migrate/buildpack-api-0.8-0.9.md
@@ -31,4 +31,4 @@ For older platforms (Platform API version 0.9 and below), arguments in `command`
 
 Platform 0.10 introduces image extensions as experimental components for customizing build and run-time base images (see [here](/docs/for-platform-operators/concepts/dockerfiles) for more information).
 
-For more information, see our tutorial on [authoring an image extension](/docs/for-buildpack-authors/tutorials/write-basic-extension).
+For more information, see our tutorial on [authoring an image extension](/docs/for-buildpack-authors/tutorials/basic-extension).
diff --git a/content/docs/for-buildpack-authors/how-to/migrate/buildpack-api-0.9-0.10.md b/content/docs/for-buildpack-authors/how-to/migrate/buildpack-api-0.9-0.10.md
@@ -53,4 +53,4 @@ Buildpacks can use this information to modify their behavior depending on the ta
 
 In Platform 0.12, extensions can be used to extend not only build-time base images, but runtime base images as well.
 
-For more information, see [authoring an image extension](/docs/for-buildpack-authors/tutorials/write-basic-extension).
+For more information, see [authoring an image extension](/docs/for-buildpack-authors/tutorials/basic-extension).
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-extension/_index.md b/content/docs/for-buildpack-authors/tutorials/basic-extension/_index.md
@@ -11,4 +11,4 @@ This is a step-by-step tutorial for creating and using image extensions, which a
 
 <!--more-->
 
-<a href="/docs/for-buildpack-authors/tutorials/write-basic-extension/setup-local-environment" class="button bg-pink">Start Tutorial</a>
+<a href="/docs/for-buildpack-authors/tutorials/basic-extension/setup-local-environment" class="button bg-pink">Start Tutorial</a>
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-extension/build-dockerfile.md b/content/docs/for-buildpack-authors/tutorials/basic-extension/build-dockerfile.md
@@ -91,4 +91,4 @@ Let's take a look at how the `samples/curl` extension fixes the error by switchi
 <!--+ if false+-->
 ---
 
-<a href="/docs/for-buildpack-authors/tutorials/write-basic-extension/run-dockerfile-switch" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/basic-extension/run-dockerfile-switch" class="button bg-pink">Next Step</a>
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-extension/building-blocks-extension.md b/content/docs/for-buildpack-authors/tutorials/basic-extension/building-blocks-extension.md
@@ -45,5 +45,5 @@ For guidance around writing extensions and more advanced use cases, see [here](/
 <!--+ if false+-->
 ---
 
-<a href="/docs/for-buildpack-authors/tutorials/write-basic-extension/build-dockerfile" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/basic-extension/build-dockerfile" class="button bg-pink">Next Step</a>
 <!--+ end +-->
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-extension/run-dockerfile-switch.md b/content/docs/for-buildpack-authors/tutorials/basic-extension/run-dockerfile-switch.md
@@ -145,5 +145,5 @@ Luckily, we can also use image extensions to dynamically install runtime depende
 <!--+ if false+-->
 ---
 
-<a href="/docs/for-buildpack-authors/tutorials/write-basic-extension/run-dockerfile-extend" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/basic-extension/run-dockerfile-extend" class="button bg-pink">Next Step</a>
 <!--+ end +-->
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-extension/setup-local-environment.md b/content/docs/for-buildpack-authors/tutorials/basic-extension/setup-local-environment.md
@@ -85,5 +85,5 @@ git clone https://github.com/buildpacks/samples.git
 <!--+ if false +-->
 ---
 
-<a href="/docs/for-buildpack-authors/tutorials/write-basic-extension/why-dockerfiles" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/basic-extension/why-dockerfiles" class="button bg-pink">Next Step</a>
 <!--+ end+-->
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-extension/why-dockerfiles.md b/content/docs/for-buildpack-authors/tutorials/basic-extension/why-dockerfiles.md
@@ -105,5 +105,5 @@ Let's take a look at how the `samples/vim` extension installs `vim` on the build
 <!--+ if false+-->
 ---
 
-<a href="/docs/for-buildpack-authors/tutorials/write-basic-extension/building-blocks-extension" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/basic-extension/building-blocks-extension" class="button bg-pink">Next Step</a>
 <!--+ end +-->
diff --git a/content/docs/for-platform-operators/concepts/dockerfiles.md b/content/docs/for-platform-operators/concepts/dockerfiles.md
@@ -62,7 +62,7 @@ An image extension could be defined with the following directory:
   outputs either or both of `build.Dockerfile` or `run.Dockerfile` for extending the builder or run image.
 
 For more information and to see a build in action,
-see [authoring an image extension](/docs/for-buildpack-authors/tutorials/write-basic-extension).
+see [authoring an image extension](/docs/for-buildpack-authors/tutorials/basic-extension).
 
 ## A platform's perspective
 
diff --git a/content/docs/for-platform-operators/how-to/migrate/deprecated/platform-api-0.3-0.4.md b/content/docs/for-platform-operators/how-to/migrate/deprecated/platform-api-0.3-0.4.md
@@ -11,13 +11,13 @@ See the [spec release](https://github.com/buildpacks/spec/releases/tag/platform%
 
 ### Windows support
 
-Windows image builds are now supported! See the [Windows build guide](/docs/for-app-developers/how-to/configure-build/build-for-windows)
+Windows image builds are now supported! See the [Windows build guide](/docs/for-app-developers/how-to/configure-build-environment/build-for-windows)
 for more details.
 
 ### Multicall launcher
 
 When running the exported application image, it is now possible to provide arguments to pre-defined process types. 
-The new flow is described [here](/docs/for-app-developers/tutorials/build-basic-app/run/#run-a-multi-process-app).
+The new flow is described [here](/docs/for-app-developers/tutorials/basic-app/run/#run-a-multi-process-app).
 As part of these changes, the exporter will not set, and the launcher no longer accepts, the `CNB_PROCESS_TYPE` variable.
 See the associated [RFC](https://github.com/buildpacks/rfcs/blob/main/text/0045-launcher-arguments.md) and [spec PR](https://github.com/buildpacks/spec/pull/118)
 for more details.
diff --git a/content/docs/for-platform-operators/how-to/prepare-build-inputs/stack.md b/content/docs/for-platform-operators/how-to/prepare-build-inputs/stack.md
@@ -8,7 +8,7 @@ weight=4
 **Note**: As of Platform API 0.12 and Buildpack API 0.10, stacks are deprecated in favor of existing constructs in the container image ecosystem such as operating system name, operating system distribution, and architecture.
 
 You can still configure the build and run base images for your CNB build.
-To find out how, see [create a build base image](/docs/for-platform-operators/how-to/prepare-build-inputs/create-build-base/) and [create a run base image](/docs/for-platform-operators/how-to/prepare-build-inputs/create-run-base/).
+To find out how, see [create a build base image](/docs/for-platform-operators/how-to/prepare-build-inputs/build-base/) and [create a run base image](/docs/for-platform-operators/how-to/prepare-build-inputs/run-base/).
 
 A stack is the grouping together of the build and run base images, represented by a unique ID.
 A stack ID identifies the configuration for the build and run base images, and it used to determined compatibility with available buildpacks, and rebasability when updated run images are available.
@@ -26,7 +26,7 @@ Before we get started, make sure you've got the following installed:
 ## Creating a custom stack
 
 We will create a sample stack based on `Ubuntu Jammy Jellyfish`. To create a custom stack, we need to create customized build and run images.
-To find out how, see [create a build base image](/docs/for-platform-operators/how-to/prepare-build-inputs/create-build-base/) and [create a run base image](/docs/for-platform-operators/how-to/prepare-build-inputs/create-run-base/), then come back here.
+To find out how, see [create a build base image](/docs/for-platform-operators/how-to/prepare-build-inputs/build-base/) and [create a run base image](/docs/for-platform-operators/how-to/prepare-build-inputs/run-base/), then come back here.
 
 ## Choose your stack ID
 

Original file line number	Diff line number	Diff line change
@@ -31,4 +31,4 @@ For older platforms (Platform API version 0.9 and below), arguments in `command`
`31`	`31`
`32`	`32`	`Platform 0.10 introduces image extensions as experimental components for customizing build and run-time base images (see [here](/docs/for-platform-operators/concepts/dockerfiles) for more information).`
`33`	`33`
`34`		`-For more information, see our tutorial on [authoring an image extension](/docs/for-buildpack-authors/tutorials/write-basic-extension).`
	`34`	`+For more information, see our tutorial on [authoring an image extension](/docs/for-buildpack-authors/tutorials/basic-extension).`
Original file line number	Diff line number	Diff line change
`@@ -53,4 +53,4 @@ Buildpacks can use this information to modify their behavior depending on the ta`
`53`	`53`
`54`	`54`	`In Platform 0.12, extensions can be used to extend not only build-time base images, but runtime base images as well.`
`55`	`55`
`56`		`-For more information, see [authoring an image extension](/docs/for-buildpack-authors/tutorials/write-basic-extension).`
	`56`	`+For more information, see [authoring an image extension](/docs/for-buildpack-authors/tutorials/basic-extension).`