diff --git a/nostarch/chapter03.md b/nostarch/chapter03.md
index ad98c5794..b7a54aee7 100644
--- a/nostarch/chapter03.md
+++ b/nostarch/chapter03.md
@@ -375,7 +375,7 @@ When you’re compiling in debug mode, Rust includes checks for integer overflow
that cause your program to *panic* at runtime if this behavior occurs. Rust
uses the term *panicking* when a program exits with an error; we’ll discuss
panics in more depth in “Unrecoverable Errors with panic!” on page XX.
-
+>
> When you’re compiling in release mode with the `--release` flag, Rust does
*not* include checks for integer overflow that cause panics. Instead, if
overflow occurs, Rust performs *two’s complement wrapping*. In short, values
@@ -384,17 +384,17 @@ of the values the type can hold. In the case of a `u8`, the value 256 becomes
0, the value 257 becomes 1, and so on. The program won’t panic, but the
variable will have a value that probably isn’t what you were expecting it to
have. Relying on integer overflow’s wrapping behavior is considered an error.
-
+>
> To explicitly handle the possibility of overflow, you can use these families
of methods provided by the standard library for primitive numeric types:
-
+>
> * Wrap in all modes with the `wrapping_*` methods, such as `wrapping_add`.
> * Return the `None` value if there is overflow with the `checked_*` methods.
> * Return the value and a boolean indicating whether there was overflow with
the `overflowing_*` methods.
> * Saturate at the value’s minimum or maximum values with the `saturating_*`
methods.
->
+
#### Floating-Point Types
Rust also has two primitive types for *floating-point numbers*, which are
diff --git a/tools/docx-to-md.xsl b/tools/docx-to-md.xsl
index 6008f652f..f9c005bf8 100644
--- a/tools/docx-to-md.xsl
+++ b/tools/docx-to-md.xsl
@@ -101,9 +101,14 @@
> *
-
- >
-
+
+
+ >
+
+
+
+
+
@@ -199,7 +204,14 @@
>
-
+
+
+
>
+
+
+
+
+