Merge branch 'main' into runext/demo

Author: Natalie Arellano

content/docs/extension-guide/create-extension/building-blocks-extension.md

@@ -27,7 +27,7 @@ You should see something akin to the following:
 
 * The `extension.toml` describes the extension, containing information such as its name, ID, and version, as well as the
   buildpack API that it implements. Though extensions are not buildpacks, they are expected to conform to the buildpack
-  API except where noted. Consult the [spec](https://github.com/buildpacks/spec/blob/buildpack/main/image_extension.md)
+  API except where noted. Consult the [spec](https://github.com/buildpacks/spec/blob/main/image_extension.md)
   for further details.
 * `./bin/detect` is invoked during the `detect` phase. It analyzes application source code to determine if the extension
   is needed and contributes [build plan](/docs/reference/spec/buildpack-api/#build-plan) entries (much like a
@@ -36,12 +36,12 @@ You should see something akin to the following:
 * `./bin/generate` is invoked during the `generate` phase (a new lifecycle phase that happens after `detect`). It
   outputs either or both of `build.Dockerfile` or `run.Dockerfile` for extending the builder or run image, respectively.
   * Only a limited set of Dockerfile instructions is supported - consult
-    the [spec](https://github.com/buildpacks/spec/blob/buildpack/main/image_extension.md)
+    the [spec](https://github.com/buildpacks/spec/blob/main/image_extension.md)
     for further details.
   * In the [initial implementation](/docs/features/dockerfiles#phased-approach), `run.Dockerfile` instructions are
     limited to a single `FROM` instruction (effectively, it is only possible to switch the run-time base image to a
     pre-created image i.e., no dynamic image modification is allowed). Consult
-    the [spec](https://github.com/buildpacks/spec/blob/buildpack/main/image_extension.md)
+    the [spec](https://github.com/buildpacks/spec/blob/main/image_extension.md)
     for further details.
 
 We'll take a closer look at the executables for the `vim` extension in the next step.

content/docs/operator-guide/create-a-stack.md

@@ -16,7 +16,7 @@ Before we get started, make sure you've got the following installed:
 
 ## Creating a custom stack
 
-In this tutorial we will create a sample stack based on `Ubuntu Bionic`. To create a custom stack, we need to create customized build and run images. Let's see how we can do so!
+In this tutorial 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. Let's see how we can do so!
 
 
 ### Create a common base image