Formatting

Signed-off-by: Natalie Arellano <narellano@vmware.com>

Author: Natalie Arellano

text/0000-refactor-sbom.md

@@ -28,7 +28,7 @@ The layer-scoped files are restored on future builds so that buildpacks can use
 
 **image signature** - allows for cryptographically verifying the digest of an OCI image
 
-**[cosign](https://github.com/sigstore/cosign/tree/main#cosign)** - tooling for generating image signatures
+**[cosign](https://github.com/sigstore/cosign/tree/main#cosign)** - tooling for generating image signatures and attestations
 
 **OCI v1.1** - pending new releases to the OCI image and distribution specs, as described [here](https://opencontainers.org/posts/blog/2023-07-07-summary-of-upcoming-changes-in-oci-image-and-distribution-specs-v-1-1/)
 
@@ -79,8 +79,8 @@ We should make it possible to invoke the `signer` separate from other phases.
 Buildpacks should continue to output SBOM files as before. We won't need to bother buildpack authors with this change.
 
 The `exporter` will accept a new optional flag `-omit-sbom` that defaults to `false`.
-If `-omit-sbom=false` the exporter will behave as today, and include the SBOM layer containing the `<layers>/sbom/launch/` directory in the application image.
-If `-omit-sbom=true` the exporter will not create the SBOM layer, but `<layers>/sbom/launch/` will remain on the filesystem and be available to the `signer`.
+* If `-omit-sbom=false` the exporter will behave as today, and include the SBOM layer containing the `<layers>/sbom/launch/` directory in the application image.
+* If `-omit-sbom=true` the exporter will not create the SBOM layer, but `<layers>/sbom/launch/` will remain on the filesystem and be available to the `signer`.
 
 The exporter will additionally generate configuration for the `signer` irrespective of the value of `-omit-sbom`.
 
@@ -95,7 +95,7 @@ The `signer` will accept configuration that will allow it to attach attestations
 
 ```toml
 [image]
-reference = <image digest>
+reference = "<image digest>"
 
 [[attestations]]
 type = "<media type>"
@@ -190,6 +190,7 @@ It should optionally accept configuration for new attestations to describe the n
 
 During `analyze`, the lifecyle should verify attestations for the previous application image, and download the SBOM data as files in `<layers>/sbom/launch/`
 so that the `restorer` can behave just as it does today when recreating `<layers>/<buildpack-id>/<layer>.sbom.<ext>` files for buildpacks.
+
 The lifecycle should fall back to pulling the SBOM layer from the image if no attestations exist (this will be necessary to keep compatibility with daemon images).
 
 # Migration