Wrap README.md and COPYRIGHT files consistently.

Author: sunfishcode

COPYRIGHT

@@ -1,19 +1,20 @@
 Short version for non-lawyers:
 
-`cap-std` is triple-licensed under Apache 2.0 with the LLVM Exception, Apache 2.0,
-and MIT terms.
+`cap-std` is triple-licensed under Apache 2.0 with the LLVM Exception,
+Apache 2.0, and MIT terms.
 
 
 Longer version:
 
-Copyrights in the `cap-std` project are retained by their contributors. No
-copyright assignment is required to contribute to the `cap-std` project.
+Copyrights in the `cap-std` project are retained by their contributors.
+No copyright assignment is required to contribute to the `cap-std`
+project.
 
 Some files include code derived from Rust's `libstd`; see the comments in
 the code for details.
 
-Except as otherwise noted (below and/or in individual files), `cap-std` is
-licensed under:
+Except as otherwise noted (below and/or in individual files), `cap-std`
+is licensed under:
 
  - the Apache License, Version 2.0, with the LLVM Exception
    <LICENSE-Apache-2.0_WITH_LLVM-exception> or

README.md

@@ -11,8 +11,8 @@
   </p>
 </div>
 
-`cap-std` crate provides a capability-based version of [`std`]. It provides all the
-interfaces you are used to, but in a capability-based version.
+`cap-std` crate provides a capability-based version of [`std`]. It provides all
+the interfaces you are used to, but in a capability-based version.
 
 [`std`]: https://doc.rust-lang.org/std/
 
@@ -57,8 +57,8 @@ Attempts to access paths not contained within the directory:
 
 return `PermissionDenied` errors.
 
-This allows application logic to configure its own access, without changing
-the behavior of the whole host process, setting up a separate host process, or
+This allows application logic to configure its own access, without changing the
+behavior of the whole host process, setting up a separate host process, or
 requiring external configuration.
 
 ## How do I obtain a `Dir`?

cap-async-std/COPYRIGHT

@@ -6,14 +6,15 @@ Apache 2.0, and MIT terms.
 
 Longer version:
 
-Copyrights in the `cap-async-std` project are retained by their contributors. No
-copyright assignment is required to contribute to the `cap-async-std` project.
+Copyrights in the `cap-async-std` project are retained by their contributors.
+No copyright assignment is required to contribute to the `cap-async-std`
+project.
 
 Some files include code derived from Rust's `libstd`; see the comments in
 the code for details.
 
-Except as otherwise noted (below and/or in individual files), `cap-async-std` is
-licensed under:
+Except as otherwise noted (below and/or in individual files), `cap-async-std`
+is licensed under:
 
  - the Apache License, Version 2.0, with the LLVM Exception
    <LICENSE-Apache-2.0_WITH_LLVM-exception> or

cap-async-std/README.md

@@ -11,22 +11,24 @@
   </p>
 </div>
 
-This crate provides a capability-based version of [`async-std`]. It provides all the
-interfaces you are used to, but in a capability-based version.
+This crate provides a capability-based version of [`async-std`]. It provides all
+the interfaces you are used to, but in a capability-based version.
 
-See the [`cap-std` README.md] for more information about capability-based security.
+See the [`cap-std` README.md] for more information about capability-based
+security.
 
 [`async-std`]: https://crates.io/crates/async-std
 [`cap-std`]: https://crates.io/crates/cap-std
 [`cap-std` README.md]: https://github.com/sunfishcode/cap-std/blob/main/README.md
 
 At the moment, `cap-async-std` is a very rudimentary translation of `cap-std` to
-`async-std`. Like `cap-std`, it uses [`cap-primitives`] to perform the underlying
-operations. It hasn't yet been optimized to make effective use of `async`.
+`async-std`. Like `cap-std`, it uses [`cap-primitives`] to perform the
+underlying operations. It hasn't yet been optimized to make effective use of
+`async`.
 
-The filesystem module, `fs`, is known to compile on Linux, macOS, and FreeBSD, and
-probably can be easily ported to other modern Unix-family platforms. Ports to
-Windows and WASI platforms are in development, though not yet usable.
+The filesystem module, `fs`, is known to compile on Linux, macOS, and FreeBSD,
+and probably can be easily ported to other modern Unix-family platforms. Ports
+to Windows and WASI platforms are in development, though not yet usable.
 
 The networking module, `net`, is not yet usable.
 

cap-directories/README.md

@@ -11,8 +11,9 @@
   </p>
 </div>
 
-The `cap-directories` crate provides utilities for accessing standard directories
-via the [`directories`] crate, but which provide [`Dir`]s instead of `Path`s.
+The `cap-directories` crate provides utilities for accessing standard
+directories via the [`directories`] crate, but which provide [`Dir`]s instead of
+`Path`s.
 
 [`directories`]: https://crates.io/crates/directories
 [`Dir`]: https://docs.rs/cap-std/latest/cap_std/fs/struct.Dir.html

cap-primitives/README.md

@@ -11,8 +11,8 @@
   </p>
 </div>
 
-The `cap-primitives` crate provides primitive sandboxing operations that [`cap-std`]
-and [`cap-async-std`] are built on.
+The `cap-primitives` crate provides primitive sandboxing operations that
+[`cap-std`] and [`cap-async-std`] are built on.
 
 [`cap-std`]: https://crates.io/crates/cap-std
 [`cap-async-std`]: https://crates.io/crates/cap-async-std

fuzz/README.md

@@ -3,15 +3,16 @@
 This crate defines various `libFuzzer` targets for `cap-std` which can be run
 via `cargo-fuzz` plugin.
 
-Currently, there is only a simple fuzzer for the `cap-primitives` crate which constructs
-random paths and attempts random filesystem operations on them. If `cap-primitives`'
-sandbox is working as intended, these operations either stay within a temporary directory
-or fail. Many of the operations in `cap-primitives` have backup checks in
-`not(feature = "no_racy_asserts")` builds, to diagnose sandbox escapes.
+Currently, there is only a simple fuzzer for the `cap-primitives` crate which
+constructs random paths and attempts random filesystem operations on them. If
+`cap-primitives`' sandbox is working as intended, these operations either stay
+within a temporary directory or fail. Many of the operations in `cap-primitives`
+have backup checks in `not(feature = "no_racy_asserts")` builds, to diagnose
+sandbox escapes.
 
 Caution is recommended when running this fuzzer, since it is a filesystem
-fuzzer, and if it should find a way to escape the sandbox and avoid the
-backup checks, it could cause data loss.
+fuzzer, and if it should find a way to escape the sandbox and avoid the backup
+checks, it could cause data loss.
 
 ## Example: fuzzing `cap-primitives`