Merge branch 'main' into dependabot/github_actions/actions/download-artifact-4

Author: AidanDelaney

content/docs/for-app-developers/concepts/build.md

@@ -9,7 +9,7 @@ weight=3
 
 ## Building explained
 
-![build diagram](/docs/for-app-developers/concepts/build.svg)
+![build diagram](/images/build.svg)
 
 Each [buildpack] inspects the source code and provides relevant dependencies.
 An image is then generated from the app's source code and these dependencies.

content/docs/for-app-developers/concepts/builder.md

@@ -13,7 +13,7 @@ The [build-time base image] provides the base environment for the `builder`
 (e.g., an Ubuntu Jammy OS image with build tooling) and
 a [runtime base image] provides the base environment for the `app image` during runtime.
 
-![builder](/docs/for-app-developers/concepts/builder.svg)
+![builder](/images/builder.svg)
 
 Under the hood a builder uses the [lifecycle] to run the `detect` phase for all the `buildpacks` it contains, in order,
 and then proceeds to run the `build` phase for all the `buildpacks` that passed detection.

content/docs/for-app-developers/concepts/rebase.md

@@ -16,7 +16,7 @@ weight=4
 
 By using image layer rebasing, this command avoids the need to fully rebuild the app.
 
-![rebase diagram](/docs/for-app-developers/concepts/rebase.svg)
+![rebase diagram](/images/rebase.svg)
 
 At its core, image rebasing is a simple process. By inspecting an app image, `rebase` can determine whether or not a
 newer version of the app's base image exists (either locally or in a registry).