Formatting fixes

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

Author: Natalie Arellano

content/docs/for-buildpack-authors/concepts/caching-strategies.md

@@ -14,7 +14,7 @@ There are three types of layers that can be contributed to an image
 
 * `build` layers -- the directory will be accessible by subsequent buildpacks,
 * `cache` layers -- the directory will be included in the cache,
-* `launch` layers -- the directory will be included in the run image as a single layer,
+* `launch` layers -- the directory will be included in the final app image as a single layer,
 
 In this section we look at caching each layer type.
 

content/docs/for-buildpack-authors/how-to/write-buildpacks/add-sbom.md

@@ -1,6 +1,6 @@
 +++
 title="Provide a Software Bill-of-Materials"
-weight=2
+weight=5
 +++
 
 Buildpacks can provide a [Software `Bill-of-Materials`](https://en.wikipedia.org/wiki/Software_bill_of_materials) (SBOM)

content/docs/for-buildpack-authors/how-to/write-buildpacks/create-layer.md

@@ -1,37 +1,40 @@
 +++
 title="Create dependency layers"
-weight=99
+weight=3
 +++
 
-Each directory created by the buildpack under the `CNB_LAYERS_DIR` can be used as a layer in the final image or build cache.
+Each directory created by the buildpack under the `CNB_LAYERS_DIR` can be used as a layer in the final app image or build cache.
 
 <!--more-->
 
 That is, each directory can be used for any of the following purposes:
 
-* Launch - the directory will be included in the run image as a single layer
-* Cache - the directory will be included in the cache and restored on future builds
-* Build - the directory will be accessible by subsequent buildpacks
+| Layer Type |                                                                                                             |
+|------------|-------------------------------------------------------------------------------------------------------------|
+| `Launch`   | the directory will be included in the **final app image** as a single layer                                 |
+| `Cache`    | the directory will be included in the **build cache** and restored to the `CNB_LAYERS_DIR` on future builds |
+| `Build`    | the directory will be accessible to **buildpacks that follow** in the build (via the environment)           |
 
-A buildpack defines how a layer will by used by creating a `<layer>.toml`
-with a name matching the directory it describes in the `CNB_LAYERS_DIR`.
+A buildpack can control how a layer will be used by creating a `<layer>.toml` with a name matching the directory it describes in the `CNB_LAYERS_DIR`.
 
-For example, a buildpack might create a `$CNB_LAYERS_DIR/python` directory
-and a `$CNB_LAYERS_DIR/python.toml` with the following contents:
+### Example
+
+A buildpack might create a `$CNB_LAYERS_DIR/python` directory and a `$CNB_LAYERS_DIR/python.toml` with the following contents:
 
 ```
 launch = true
 cache = true
 build = true
 ```
 
-In this example, the `python` directory will be included in the run image,
-cached for future builds, and will be accessible to subsequent buildpacks via the environment.
+In this example:
+* the final app image will contain a layer with `python`, as this is needed to run the app
+* the `$CNB_LAYERS_DIR/python` directory will be pre-created for future builds, avoiding the need to re-download this large dependency
+* buildpacks that follow in the build will be able to use `python`
 
 ### Example
 
-This is a simple example of a buildpack that runs Python's `pip` package manager
-to resolve dependencies:
+This is a simple `./bin/build` script for a buildpack that runs Python's `pip` package manager to resolve dependencies:
 
 ```
 #!/bin/sh

content/docs/for-buildpack-authors/how-to/write-buildpacks/get-started.md

@@ -1,6 +1,6 @@
 +++
 title="Get started"
-weight=0
+weight=1
 +++
 
 To write a buildpack, we follow the [Buildpack Specification](https://github.com/buildpacks/spec/blob/main/buildpack.md),

content/docs/for-buildpack-authors/how-to/write-buildpacks/specify-launch-processes.md

@@ -1,6 +1,6 @@
 +++
 title="Specify process types"
-weight=1
+weight=4
 +++
 
 One of the benefits of buildpacks is that they are multi-process - an image can have multiple entrypoints for each operational mode.

content/docs/for-buildpack-authors/how-to/write-buildpacks/use-build-plan.md

@@ -1,6 +1,6 @@
 +++
 title="Use the build plan"
-weight=99
+weight=2
 +++
 
 The [Build Plan](https://github.com/buildpacks/spec/blob/main/buildpack.md#build-plan-toml) is a document that buildpacks can use to pass information between the `detect` and `build` phases, and between each other.