Unwrap conditional compilation

This unwraps the text to follow our style guide.

Author: ehuss

src/conditional-compilation.md

@@ -37,8 +37,7 @@ r[cfg.conditional]
 Whether to compile can depend on the target architecture of the compiled crate, arbitrary values passed to the compiler, and other things further described below.
 
 r[cfg.predicate]
-Each form of conditional compilation takes a _configuration predicate_ that
-evaluates to true or false. The predicate is one of the following:
+Each form of conditional compilation takes a _configuration predicate_ that evaluates to true or false. The predicate is one of the following:
 
 r[cfg.predicate.option]
 * A configuration option. The predicate is true if the option is set, and false if it is unset.
@@ -74,8 +73,7 @@ r[cfg.options.set]
 ## Set configuration options
 
 r[cfg.options.general]
-Which configuration options are set is determined statically during the
-compilation of the crate.
+Which configuration options are set is determined statically during the compilation of the crate.
 
 r[cfg.options.target]
 Some options are _compiler-set_ based on data about the compilation.
@@ -84,8 +82,7 @@ r[cfg.options.other]
 Other options are _arbitrarily-set_ based on input passed to the compiler outside of the code.
 
 r[cfg.options.crate]
-It is not possible to set a
-configuration option from within the source code of the crate being compiled.
+It is not possible to set a configuration option from within the source code of the crate being compiled.
 
 > [!NOTE]
 > For `rustc`, arbitrary-set configuration options are set using the [`--cfg`] flag. Configuration values for a specified target can be displayed with `rustc --print cfg --target $TARGET`.
@@ -97,9 +94,7 @@ r[cfg.target_arch]
 ### `target_arch`
 
 r[cfg.target_arch.gen]
-Key-value option set once with the target's CPU architecture. The value is
-similar to the first element of the platform's target triple, but not
-identical.
+Key-value option set once with the target's CPU architecture. The value is similar to the first element of the platform's target triple, but not identical.
 
 r[cfg.target_arch.values]
 Example values:
@@ -116,8 +111,7 @@ r[cfg.target_feature]
 ### `target_feature`
 
 r[cfg.target_feature.general]
-Key-value option set for each platform feature available for the current
-compilation target.
+Key-value option set for each platform feature available for the current compilation target.
 
 r[cfg.target_feature.values]
 Example values:
@@ -130,19 +124,16 @@ Example values:
 * `"sse2"`
 * `"sse4.1"`
 
-See the [`target_feature` attribute] for more details on the available
-features.
+See the [`target_feature` attribute] for more details on the available features.
 
 r[cfg.target_feature.crt_static]
-An additional feature of `crt-static` is available to the
-`target_feature` option to indicate that a [static C runtime] is available.
+An additional feature of `crt-static` is available to the `target_feature` option to indicate that a [static C runtime] is available.
 
 r[cfg.target_os]
 ### `target_os`
 
 r[cfg.target_os.general]
-Key-value option set once with the target's operating system. This value is
-similar to the second and third element of the platform's target triple.
+Key-value option set once with the target's operating system. This value is similar to the second and third element of the platform's target triple.
 
 r[cfg.target_os.values]
 Example values:
@@ -162,9 +153,7 @@ r[cfg.target_family]
 ### `target_family`
 
 r[cfg.target_family.general]
-Key-value option providing a more generic description of a target, such as the family of the
-operating systems or architectures that the target generally falls into. Any number of
-`target_family` key-value pairs can be set.
+Key-value option providing a more generic description of a target, such as the family of the operating systems or architectures that the target generally falls into. Any number of `target_family` key-value pairs can be set.
 
 r[cfg.target_family.values]
 Example values:
@@ -186,13 +175,7 @@ r[cfg.target_env]
 ### `target_env`
 
 r[cfg.target_env.general]
-Key-value option set with further disambiguating information about the target
-platform with information about the ABI or `libc` used. For historical reasons,
-this value is only defined as not the empty-string when actually needed for
-disambiguation. Thus, for example, on many GNU platforms, this value will be
-empty. This value is similar to the fourth element of the platform's target
-triple. One difference is that embedded ABIs such as `gnueabihf` will simply
-define `target_env` as `"gnu"`.
+Key-value option set with further disambiguating information about the target platform with information about the ABI or `libc` used. For historical reasons, this value is only defined as not the empty-string when actually needed for disambiguation. Thus, for example, on many GNU platforms, this value will be empty. This value is similar to the fourth element of the platform's target triple. One difference is that embedded ABIs such as `gnueabihf` will simply define `target_env` as `"gnu"`.
 
 r[cfg.target_env.values]
 Example values:
@@ -209,13 +192,10 @@ r[cfg.target_abi]
 ### `target_abi`
 
 r[cfg.target_abi.general]
-Key-value option set to further disambiguate the target with information about
-the target ABI.
+Key-value option set to further disambiguate the target with information about the target ABI.
 
 r[cfg.target_abi.disambiguation]
-For historical reasons, this value is only defined as not the empty-string when actually
-needed for disambiguation. Thus, for example, on many GNU platforms, this value will be
-empty.
+For historical reasons, this value is only defined as not the empty-string when actually needed for disambiguation. Thus, for example, on many GNU platforms, this value will be empty.
 
 r[cfg.target_abi.values]
 Example values:
@@ -228,8 +208,7 @@ Example values:
 r[cfg.target_endian]
 ### `target_endian`
 
-Key-value option set once with either a value of "little" or "big" depending
-on the endianness of the target's CPU.
+Key-value option set once with either a value of "little" or "big" depending on the endianness of the target's CPU.
 
 r[cfg.target_pointer_width]
 ### `target_pointer_width`
@@ -262,12 +241,10 @@ r[cfg.target_has_atomic]
 ### `target_has_atomic`
 
 r[cfg.target_has_atomic.general]
-Key-value option set for each bit width that the target supports
-atomic loads, stores, and compare-and-swap operations.
+Key-value option set for each bit width that the target supports atomic loads, stores, and compare-and-swap operations.
 
 r[cfg.target_has_atomic.stdlib]
-When this cfg is present, all of the stable [`core::sync::atomic`] APIs are available for
-the relevant atomic width.
+When this cfg is present, all of the stable [`core::sync::atomic`] APIs are available for the relevant atomic width.
 
 r[cfg.target_has_atomic.values]
 Possible values:
@@ -282,22 +259,17 @@ Possible values:
 r[cfg.test]
 ### `test`
 
-Enabled when compiling the test harness. Done with `rustc` by using the
-[`--test`] flag. See [Testing] for more on testing support.
+Enabled when compiling the test harness. Done with `rustc` by using the [`--test`] flag. See [Testing] for more on testing support.
 
 r[cfg.debug_assertions]
 ### `debug_assertions`
 
-Enabled by default when compiling without optimizations.
-This can be used to enable extra debugging code in development but not in
-production.  For example, it controls the behavior of the standard library's
-[`debug_assert!`] macro.
+Enabled by default when compiling without optimizations. This can be used to enable extra debugging code in development but not in production.  For example, it controls the behavior of the standard library's [`debug_assert!`] macro.
 
 r[cfg.proc_macro]
 ### `proc_macro`
 
-Set when the crate being compiled is being compiled with the `proc_macro`
-[crate type].
+Set when the crate being compiled is being compiled with the `proc_macro` [crate type].
 
 r[cfg.panic]
 ### `panic`
@@ -448,9 +420,7 @@ Zero, one, or more attributes may be listed. Multiple attributes will each be ex
 r[cfg.macro]
 ### The `cfg` macro
 
-The built-in `cfg` macro takes in a single configuration predicate and evaluates
-to the `true` literal when the predicate is true and the `false` literal when
-it is false.
+The built-in `cfg` macro takes in a single configuration predicate and evaluates to the `true` literal when the predicate is true and the `false` literal when it is false.
 
 For example: