Fix one-sentence-per-line violations

.github/PULL_REQUEST_TEMPLATE/maintainer_nomination.md

@@ -10,7 +10,8 @@ Name of the new maintainer with GitHub username
 
 ## Justification
 
-Highlight any work contributed by the new maintainer. Examples of contributions may be:
+Highlight any work contributed by the new maintainer.
+Examples of contributions may be:
 
 - Community involvement in mailing lists and meetings
 - Involvement in any OCI working groups

considerations.md

@@ -2,12 +2,14 @@
 
 ## Extensibility
 
-Implementations storing or copying content MUST NOT modify or alter the content in a way that would change the digest of the content. Examples of these implementations include:
+Implementations storing or copying content MUST NOT modify or alter the content in a way that would change the digest of the content.
+Examples of these implementations include:
 
 - A [registry implementing the distribution specification][distribution-spec], including local registries, caching proxies
 - An application which copies content to disk or between registries
 
-Implementations processing content SHOULD NOT generate an error if they encounter an unknown property in a known media type. Examples of these implementations include:
+Implementations processing content SHOULD NOT generate an error if they encounter an unknown property in a known media type.
+Examples of these implementations include:
 
 - A [runtime implementing the runtime specification][runtime-spec]
 - An implementation using OCI to retrieve and utilize artifacts, e.g.: a WASM runtime

descriptor.md

@@ -165,8 +165,7 @@ Note that `[A-F]` MUST NOT be used here.
 
 #### BLAKE3
 
-[BLAKE3][blake3] is a high performance, highly parallelizable, collision-resistant hash function which [is more performant][blake3-vs-sha2] than
-[SHA-256][rfc4634-s4.1].
+[BLAKE3][blake3] is a high performance, highly parallelizable, collision-resistant hash function which [is more performant][blake3-vs-sha2] than [SHA-256][rfc4634-s4.1].
 The hash output length MUST be 256 bits.
 Implementations MAY implement BLAKE3 digest verification for use in descriptors.
 

layer.md

@@ -97,8 +97,7 @@ With this approach, the link map and links names of a directory could be compare
 
 #### Platform-specific attributes
 
-Implementations on Windows MUST support these additional attributes, encoded in [PAX vendor
-extensions](https://github.com/libarchive/libarchive/wiki/ManPageTar5#pax-interchange-format) as follows:
+Implementations on Windows MUST support these additional attributes, encoded in [PAX vendor extensions](https://github.com/libarchive/libarchive/wiki/ManPageTar5#pax-interchange-format) as follows:
 
 - [Windows file attributes](https://msdn.microsoft.com/en-us/library/windows/desktop/gg258117(v=vs.85).aspx) (`MSWINDOWS.fileattr`)
 - [Security descriptor](https://msdn.microsoft.com/en-us/library/cc230366.aspx) (`MSWINDOWS.rawsd`): base64-encoded self-relative binary security descriptor

media-types.md

@@ -84,7 +84,8 @@ The following figure shows how the above media types reference each other:
 ![media types](img/media-types.png)
 
 [Descriptors](descriptor.md) are used for all references.
-The image-index being a "fat manifest" references a list of image manifests per target platform. An image manifest references exactly one target configuration and possibly many layers.
+The image-index being a "fat manifest" references a list of image manifests per target platform.
+An image manifest references exactly one target configuration and possibly many layers.
 
 [rfc1952]: https://tools.ietf.org/html/rfc1952
 [rfc8478]: https://tools.ietf.org/html/rfc8478