diff --git a/_books/ion-1-1/src/modules/encoding_modules.md b/_books/ion-1-1/src/modules/encoding_modules.md
index 7bdb7e56..4ed965a8 100644
--- a/_books/ion-1-1/src/modules/encoding_modules.md
+++ b/_books/ion-1-1/src/modules/encoding_modules.md
@@ -237,4 +237,4 @@ $ion::(encoding)
 You can also consider writing an Ion verson marker, which is more compact.
 The behavior is slightly different, however:
 an IVM will also add `$ion` to the encoding module sequence.
-See the [Default encoding module sequence](#default-encoding-module-sequence) section for details.
\ No newline at end of file
+See the [Default encoding module sequence](#default-encoding-module-sequence) section for details.
diff --git a/_books/ion-1-1/src/whats_new.md b/_books/ion-1-1/src/whats_new.md
index cb1e1a42..c45de3b5 100644
--- a/_books/ion-1-1/src/whats_new.md
+++ b/_books/ion-1-1/src/whats_new.md
@@ -34,6 +34,7 @@ have been supplanted by Ion 1.1's more general [opcodes](binary/opcodes.md),
 which have been organized to prioritize the most commonly used encodings and make leveraging macros as inexpensive as possible.
 
 In both text and binary Ion 1.1, the Ion Version Marker syntax is compatible with Ion 1.0's version marker syntax.
+
 This means that an Ion 1.0-only reader can correctly identify when a stream uses Ion 1.1 (allowing it to report an error),
 and an Ion 1.1 reader can correctly "downshift" to expecting Ion 1.0 data when it encounters a stream using Ion 1.0.