Fix "Line must not end with spaces" and link error

Author: chorman0773

src/types/numeric.md

@@ -70,7 +70,7 @@ r[type.numeric.repr.integer-width]
 The range of values an integer type can represent depends on its signedness and its width, in bits. The width of type `uN` or `iN` is `N`. The width of type `usize` or `isize` is the value of the `target_pointer_width` property.
 
 > [!NOTE]
-> There are exactly `1<<N` unique values of an integer type of width `N`. 
+> There are exactly `1<<N` unique values of an integer type of width `N`.
 > In particular, for an unsigned type, these values are in the range `0..(1<<N)` and for a signed type, are in the range `-(1<<(N-1))..(1<<(N-1))`, using rust range syntax.
 
 r[type.numeric.repr.unsigned]
@@ -88,19 +88,19 @@ r[type.numeric.repr.signed]
 A value `i` of a signed integer type with width `N` is represented the same as the corresponding value of the unsigned counterpart type which is congruent modulo `2^N`.
 
 > [!NOTE]
-> This encoding of signed integers is known as the 2s complement encoding. 
+> This encoding of signed integers is known as the 2s complement encoding.
 
 r[type.numeric.repr.float-width]
 Each floating-point type has a width. The type `fN` has a width of `N`.
 
 r[type.numeric.repr.float]
 A floating-point value is represented by the following decoding:
 * The byte sequence is decoded as the unsigned integer type with the same width as the floating-point type,
-* The resulting integer is decoded according to [IEEE 754-2019] into the format used for the type. 
+* The resulting integer is decoded according to [IEEE 754-2019] into the format used for the type.
 
 > [!NOTE]
-> The representation of each finite number and infinity is unique as a result of this. 
-> The exact behaviour of encoding and decoding NaNs is not yet decided 
+> The representation of each finite number and infinity is unique as a result of the definition of [IEEE 754-2019].
+> The exact behaviour of encoding and decoding NaNs is not yet decided
 
 r[type.numeric.repr.float-format]
 The [IEEE 754-2019] `binary32` format is used for `f32`, and the `binary64` format is used for `f64`. The set of values for each floating-point type are determined by the respective format.

src/types/struct.md

@@ -36,13 +36,9 @@ r[type.struct.value]
 r[type.struct.value.intro]
 A value of a struct type consists of a list of values for each field.
 
-
 r[type.struct.value.encode-decode]
 When a value of a struct type is encoded, each field of the struct is encoded at its corresponding offset and each byte that is not within a field of the struct is set to uninit.
-When a value of a struct type is decoded, each field of the struct is decoded from its corresponding offset.
-
-> [!NOTE]
-> It is valid for padding bytes to hold a value other than uninit when decoded, and these bytes are ignored when decoding an struct value.
+When a value of a struct type is decoded, each field of the struct is decoded from its corresponding offset. Each byte that is not within a field of the struct is ignored.
 
 [^structtype]: `struct` types are analogous to `struct` types in C, the
     *record* types of the ML family, or the *struct* types of the Lisp family.

src/types/union.md

@@ -24,7 +24,7 @@ The memory layout of a `union` is undefined by default (in particular, fields do
 *not* have to be at offset 0), but the `#[repr(...)]` attribute can be used to
 fix a layout.
 
-## Union Values 
+## Union Values
 
 r[type.union.value]
 
@@ -37,7 +37,7 @@ A byte `b` in the representation of a struct or union is a value byte if there e
 > [!NOTE]
 > A byte in a union is a value byte if it is a value byte in *any* field.
 
-r[type.struct.value.padding]
+r[type.union.value.padding]
 Every byte in an struct or union which is not a value byte is a padding byte. [Enum types][type.enum.value.value-padding], [tuple types][type.tuple.padding], and other types may also have padding bytes.
 
 > [!NOTE]