Merge pull request #4066 from tgross35/format-markdown

Format all markdown files to rewrap text

Author: tgross35

README.md

@@ -11,8 +11,8 @@ This crate exports all underlying platform types, functions, and constants under
 the crate root, so all items are accessible as `libc::foo`. The types and values
 of all the exported APIs match the platform that libc is compiled for.
 
-Windows API bindings are not included in this crate. If you are looking for WinAPI
-bindings, consider using crates like [windows-sys].
+Windows API bindings are not included in this crate. If you are looking for
+WinAPI bindings, consider using crates like [windows-sys].
 
 More detailed information about the design of this library can be found in its
 [associated RFC][rfc].
@@ -43,32 +43,31 @@ libc = "0.2"
 
 ## Features
 
-* `std`: by default `libc` links to the standard library. Disable this
-  feature to remove this dependency and be able to use `libc` in `#![no_std]`
-  crates.
+* `std`: by default `libc` links to the standard library. Disable this feature
+  to remove this dependency and be able to use `libc` in `#![no_std]` crates.
 
 * `extra_traits`: all `struct`s implemented in `libc` are `Copy` and `Clone`.
   This feature derives `Debug`, `Eq`, `Hash`, and `PartialEq`.
 
-* `const-extern-fn`: Changes some `extern fn`s into `const extern fn`s.
-  If you use Rust >= 1.62, this feature is implicitly enabled.
-  Otherwise it requires a nightly rustc.
+* `const-extern-fn`: Changes some `extern fn`s into `const extern fn`s. If you
+  use Rust >= 1.62, this feature is implicitly enabled. Otherwise it requires a
+  nightly rustc.
 
 ## Rust version support
 
-The minimum supported Rust toolchain version is currently **Rust 1.63.0**
-(libc does not currently have any policy regarding changes to the minimum
-supported Rust version; such policy is a work in progress).
+The minimum supported Rust toolchain version is currently **Rust 1.63.0** (libc
+does not currently have any policy regarding changes to the minimum supported
+Rust version; such policy is a work in progress).
 
 ## Platform support
 
-You can see the platform(target)-specific docs on [docs.rs], select a platform you want to see.
+You can see the platform(target)-specific docs on [docs.rs], select a platform
+you want to see.
 
-See
-[`ci/build.sh`](https://github.com/rust-lang/libc/blob/HEAD/ci/build.sh)
-for the platforms on which `libc` is guaranteed to build for each Rust
-toolchain. The test-matrix at [GitHub Actions] and [Cirrus CI] show the
-platforms in which `libc` tests are run.
+See [`ci/build.sh`](https://github.com/rust-lang/libc/blob/HEAD/ci/build.sh) for
+the platforms on which `libc` is guaranteed to build for each Rust toolchain.
+The test-matrix at [GitHub Actions] and [Cirrus CI] show the platforms in which
+`libc` tests are run.
 
 <div class="platform_docs"></div>
 
@@ -86,13 +85,13 @@ at your option.
 
 ## Contributing
 
-We welcome all people who want to contribute. Please see the [contributing
-instructions] for more information.
+We welcome all people who want to contribute. Please see the
+[contributing instructions] for more information.
 
 [contributing instructions]: https://github.com/rust-lang/libc/blob/HEAD/CONTRIBUTING.md
 
-Contributions in any form (issues, pull requests, etc.) to this project
-must adhere to Rust's [Code of Conduct].
+Contributions in any form (issues, pull requests, etc.) to this project must
+adhere to Rust's [Code of Conduct].
 
 [Code of Conduct]: https://www.rust-lang.org/policies/code-of-conduct
 

ci/README.md

@@ -4,8 +4,8 @@ result the CI is pretty complicated and also pretty large! Hopefully this can
 serve as a guide through the sea of scripts in this directory and elsewhere in
 this project.
 
-Note that this documentation is quite outdated. See CI config and scripts
-in the `ci` directory how we run CI now.
+Note that this documentation is quite outdated. See CI config and scripts in the
+`ci` directory how we run CI now.
 
 # Files
 
@@ -20,8 +20,9 @@ First up, let's talk about the files in this directory:
 
 # CI Systems
 
-Currently this repository leverages a combination of GitHub Actions and Cirrus CI
-for running tests. You can find tested triples in [Actions config] or [Cirrus config].
+Currently this repository leverages a combination of GitHub Actions and Cirrus
+CI for running tests. You can find tested triples in [Actions config] or
+[Cirrus config].
 
 The Windows triples are all pretty standard, they just set up their environment
 then run tests, no need for downloading any extra target libs (we just download
@@ -101,8 +102,10 @@ about above), and then shut down.
 
 1. [Download the latest stable amd64-bootonly release ISO](https://www.freebsd.org/where.html).
    E.g. FreeBSD-11.1-RELEASE-amd64-bootonly.iso
-2. Create the disk image: `qemu-img create -f qcow2 FreeBSD-11.1-RELEASE-amd64.qcow2 2G`
-3. Boot the machine: `qemu-system-x86_64 -cdrom FreeBSD-11.1-RELEASE-amd64-bootonly.iso -drive if=virtio,file=FreeBSD-11.1-RELEASE-amd64.qcow2 -net nic,model=virtio -net user`
+2. Create the disk image:
+   `qemu-img create -f qcow2 FreeBSD-11.1-RELEASE-amd64.qcow2 2G`
+3. Boot the machine:
+   `qemu-system-x86_64 -cdrom FreeBSD-11.1-RELEASE-amd64-bootonly.iso -drive if=virtio,file=FreeBSD-11.1-RELEASE-amd64.qcow2 -net nic,model=virtio -net user`
 4. Run the installer, and install FreeBSD:
    1. Install
    1. Continue with default keymap
@@ -159,9 +162,9 @@ about above), and then shut down.
 
    1. Exit the post install shell: `exit`
    1. Back in the installer choose Reboot
-   1. If all went well the machine should reboot and show a login prompt.
-      If you switch to the serial console by choosing View > serial0 in
-      the qemu menu, you should be logged in as root.
+   1. If all went well the machine should reboot and show a login prompt. If you
+      switch to the serial console by choosing View > serial0 in the qemu menu,
+      you should be logged in as root.
    1. Shutdown the machine: `shutdown -p now`
 
 Helpful links
@@ -178,8 +181,8 @@ Helpful links
 4. run installer
 5. `echo 'set tty com0' >> /etc/boot.conf`
 6. `echo 'boot' >> /etc/boot.conf`
-7. Modify /etc/ttys, change the `tty00` at the end from 'unknown off' to
-   'vt220 on secure'
+7. Modify /etc/ttys, change the `tty00` at the end from 'unknown off' to 'vt220
+   on secure'
 8. Modify same line in /etc/ttys to have `"/root/foo.sh"` as the shell
 9. Add this script to `/root/foo.sh`
 

libc-test/semver/README.md

@@ -6,12 +6,13 @@ ensure that APIs aren't removed between libc releases.
 ## File order
 
 Files are including in the following order:
- * Family, e.g. `unix.txt`. NOTE: Windows is skipped here and includes as OS
-   name below.
- * Vendor, e.g. `apple.txt`. This allows us to have a single file with system
-   calls shared between multiple OSs, e.g. `ios.txt`, `macos.txt` share the same
-   kernel.
- * OS, e.g `linux.txt`, `macos.txt`, `windows.txt`.
- * Architecture specific system calls, e.g. `linux-x86_64.txt` or
-   `linux-aarch64.txt`.
- * Target environment, e.g. `windows-mscv.txt` or `windows-gnu.txt`.
+
+* Family, e.g. `unix.txt`. NOTE: Windows is skipped here and includes as OS name
+  below.
+* Vendor, e.g. `apple.txt`. This allows us to have a single file with system
+  calls shared between multiple OSs, e.g. `ios.txt`, `macos.txt` share the same
+  kernel.
+* OS, e.g `linux.txt`, `macos.txt`, `windows.txt`.
+* Architecture specific system calls, e.g. `linux-x86_64.txt` or
+  `linux-aarch64.txt`.
+* Target environment, e.g. `windows-mscv.txt` or `windows-gnu.txt`.