Clean up app-dev how-to

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

Author: Natalie Arellano

content/docs/for-app-developers/how-to/build-inputs/_index.md

@@ -1,6 +1,5 @@
 +++
 title="Configure build inputs"
 weight=1
-
 include_summaries=true
 +++

content/docs/for-app-developers/how-to/build-inputs/build-time-environment.md

@@ -1,14 +1,13 @@
 +++
-title="Configure build-time environment variables"
+title="Customize buildpack behavior with build-time environment variables"
 weight=2
-summary="Customize buildpack behavior through the build-time environment."
 +++
-<!--+- `
-# Environment variables
-`+-->
+
 Environment variables are a common way to configure various buildpacks at build-time.
 
-Below are a few ways you can do so. All of them will use our [samples][samples] repo for simplicity.
+<!--more-->
+
+Below are a few ways you can do so. All of them will use our [samples] repo for simplicity.
 
 ### Using CLI arguments (`--env`)
 

content/docs/for-app-developers/how-to/build-inputs/buildpacks.md

@@ -4,10 +4,6 @@ weight=1
 summary="No builder author can be truly omniscient, and whoever created yours surely was no exception!"
 +++
 
-<!--+- `
-# Specify buildpacks
-`+-->
-
 You may specify exactly what buildpacks are used during the build process by referencing them with a URI in any of the following formats.
 
 | Type                  | Format                                       |
@@ -21,7 +17,8 @@ You may specify exactly what buildpacks are used during the build process by ref
 
 ##### Fallback Behavior
 
-When a string does not include a scheme prefix (ex. `docker://`) and also does not match a path on the filesystem, a platform may attempt to resolve it to a URI in the following order:
+When a string does not include a scheme prefix (ex. `docker://`) and also does not match a path on the filesystem,
+a platform may attempt to resolve it to a URI in the following order:
 - If it matches a buildpack ID in the builder, it will be treated as a `urn:cnb:builder` URI
 - If it looks like a Docker ref, it will be treated as a `docker://` URI
 - If it looks like a Buildpack Registry ID, it will be treated as a `urn:cnb:registry` URI
@@ -111,4 +108,4 @@ A buildpack located in a CNB Registry
 <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/project-toml/
-[samples]: https://github.com/buildpacks/samples
+[samples]: https://github.com/buildpacks/samples

content/docs/for-app-developers/how-to/build-inputs/cache-images.md

@@ -3,11 +3,8 @@ title="Use a cache image"
 weight=6
 summary="Share layers between builds with a cache image."
 +++
-<!--+- `
-# Cache Images
-`+-->
 
-Cache Images are a way to preserve build optimizing layers across different host machines. 
+Cache images are a way to preserve build-optimizing layers across different host machines. 
 These images can improve performance when using `pack` in ephemeral environments such as CI/CD pipelines.
 
 ## Using Cache Images (`--cache-image`)

content/docs/for-app-developers/how-to/build-inputs/volume-mounts.md

@@ -3,14 +3,6 @@ title="Mount volumes at build-time"
 weight=3
 summary="Supply and persist data from build containers with arbitrary volume mounts."
 +++
-<!--+if false+-->
-{{< param "summary" >}}
-<!--+end+-->
-<!--+- `
-# Mounting Volumes
-
-Volumes are a mechanism for both supplying and persisting data generated by build containers.
-`+-->
 
 ## Mounting Volumes (`--volume`)
 

content/docs/for-app-developers/how-to/build-outputs/_index.md

@@ -1,6 +1,5 @@
 +++
 title="Understand build outputs"
 weight=2
-
 include_summaries=true
 +++

content/docs/for-app-developers/how-to/build-outputs/download-sbom.md

@@ -1,30 +1,30 @@
 +++
 title="Download a Software Bill-of-Materials (SBOM)"
 summary="An SBOM can give you a layer-by-layer view of what's inside your application image."
-weight=2
+weight=3
 +++
 
 ## Summary
 
-A **Software-Bill-of-Materials** (`SBoM`) lists all the software components included in an image.  Cloud Native Buildpacks provides all the transparency you need to have confidence in your image supply chain.  Software-Bill-of-Materials in [CycloneDX](https://cyclonedx.org/), [Syft](https://github.com/anchore/syft) and [Spdx](https://spdx.dev/) formats are supported.
+A **Software-Bill-of-Materials** (`SBOM`) lists all the software components included in an image.  Cloud Native Buildpacks provides all the transparency you need to have confidence in your image supply chain.  Software-Bill-of-Materials in [CycloneDX](https://cyclonedx.org/), [Syft](https://github.com/anchore/syft) and [Spdx](https://spdx.dev/) formats are supported.
 
-1. Buildpacks can populate `SBoM` information about the dependencies they have provided.
+1. Buildpacks can populate `SBOM` information about the dependencies they have provided.
 
 ## Viewing Bill of Materials
 
-You can use the `sbom download` command to inspect your app for its Software-Bill-of-Materials. The following command will download the application layer containing the `SBoM` files to `./layers/sbom/...` on your local filesystem.
+You can use the `sbom download` command to inspect your app for its Software-Bill-of-Materials. The following command will download the application layer containing the `SBOM` files to `./layers/sbom/...` on your local filesystem.
 
 ```bash
 pack sbom download your-image-name
 ```
 
-You can also choose to download the `SBoM` from an image hosted in a remote registry, as opposed to an image hosted in a Docker daemon. You use the `--remote` flag to do so.
+You can also choose to download the `SBOM` from an image hosted in a remote registry, as opposed to an image hosted in a Docker daemon. You use the `--remote` flag to do so.
 
 ```bash
 pack sbom download your-image-name --remote
 ```
 
-The following example demonstrates  running `pack sbom download ...` on an image containing an `SBoM` in  `syft` format.  Running `pack sbom download ...` creates a `layers/sbom` directory and populates that directory with `sbom.syft.json` files.  The combined metadata from all of the `sbom.syft.json` files is the image `SBoM`. Where an image generates CycloneDX `SBoM` metadata, the files are named `sbom.cdx.json`. Similarly, Spdx files are named `sbom.spdx.json`.
+The following example demonstrates  running `pack sbom download ...` on an image containing an `SBOM` in  `syft` format.  Running `pack sbom download ...` creates a `layers/sbom` directory and populates that directory with `sbom.syft.json` files.  The combined metadata from all of the `sbom.syft.json` files is the image `SBOM`. Where an image generates CycloneDX `SBOM` metadata, the files are named `sbom.cdx.json`. Similarly, Spdx files are named `sbom.spdx.json`.
 
 ```bash
 layers

content/docs/for-app-developers/how-to/build-outputs/inspect-app.md

@@ -1,10 +1,13 @@
 +++
 title="Inspect your application image"
-weight=1
+weight=2
 +++
 
-One of the benefits of buildpacks is they can also populate the app image with metadata from the build process,
-allowing you to audit the app image for information like:
+Buildpacks-built images contain metadata that allow you to audit both the image itself and the build process.
+
+<!--more-->
+
+Information includes:
 * The process types that are available and the commands associated with them
 * The run-image the app image was based on
 * The buildpacks were used to create the app image
@@ -30,4 +33,6 @@ Processes:
   web (default)        bash         node-js app.js                                   /workspace
 ```
 
-Apart from the above standard metadata, buildpacks can also populate information about the dependencies they have provided in form of a `Software Bill-of-Materials` or `SBOM`.
+Apart from the above standard metadata, buildpacks can also populate information about the dependencies they have provided in form of a `Software Bill-of-Materials` or [SBOM].
+
+[SBOM]: /docs/for-app-developers/how-to/build-outputs/download-sbom

content/docs/for-app-developers/how-to/build-outputs/specify-launch-process.md

@@ -1,14 +1,10 @@
 +++
-title="Run the app"
-weight=2
+title="Run the application"
+weight=1
 summary="Learn how to specify the launch process for an app."
 +++
 
-<!--+- `
-# Specify launch process
-
-Learn how to specify the launch process for an app.
-`+-->
+Buildpacks-built images can contain multiple process types.
 
 ### Build a multi-process app