diff --git a/doc/langref.html.in b/doc/langref.html.in
index 974acb49716d37308f88150d92c2a6ac3268127c..a0ea833d85a0f16320c71a784a4fd35a8a855f1a 100644
--- a/doc/langref.html.in
+++ b/doc/langref.html.in
@@ -7274,46 +7274,27 @@ fn readU32Be() u32 {}
       </ul>
       {#header_close#}
       {#header_close#}
+
       {#header_open|Source Encoding#}
-      <p>Zig source code is encoded in UTF-8. An invalid UTF-8 byte sequence results in a compile error.</p>
-      <p>Throughout all zig source code (including in comments), some code points are never allowed:</p>
+      <p>Zig source code is UTF-8 encoded. Invalid UTF-8 byte sequences are not allowed anywhere.</p>
+      <p>Some code points are never allowed, even in {#link|Comments#}:</p>
       <ul>
-        <li>Ascii control characters, except for U+000a (LF), U+000d (CR), and U+0009 (HT): U+0000 - U+0008, U+000b - U+000c, U+000e - U+0001f, U+007f.</li>
-        <li>Non-Ascii Unicode line endings: U+0085 (NEL), U+2028 (LS), U+2029 (PS).</li>
+        <li>ASCII control characters, except for U+000a (LF): U+0000...U+0009, U+000b...U+0001f, U+007f.</li>
+        <li>Non-ASCII Unicode line endings: U+0085 (NEL), U+2028 (LS), U+2029 (PS).</li>
+        <li>Byte order marks: U+FEFF (BOM).</li>
       </ul>
       <p>
-      LF (byte value 0x0a, code point U+000a, {#syntax#}'\n'{#endsyntax#}) is the line terminator in Zig source code.
-      This byte value terminates every line of zig source code except the last line of the file.
-      It is recommended that non-empty source files end with an empty line, which means the last byte would be 0x0a (LF).
-      </p>
-      <p>
-      Each LF may be immediately preceded by a single CR (byte value 0x0d, code point U+000d, {#syntax#}'\r'{#endsyntax#})
-      to form a Windows style line ending, but this is discouraged. Note that in multiline strings, CRLF sequences will
-      be encoded as LF when compiled into a zig program.
-      A CR in any other context is not allowed.
-      </p>
-      <p>
-      HT hard tabs (byte value 0x09, code point U+0009, {#syntax#}'\t'{#endsyntax#}) are interchangeable with
-      SP spaces (byte value 0x20, code point U+0020, {#syntax#}' '{#endsyntax#}) as a token separator,
-      but use of hard tabs is discouraged. See {#link|Grammar#}.
-      </p>
-      <p>
-      For compatibility with other tools, the compiler ignores a UTF-8-encoded byte order mark (U+FEFF)
-      if it is the first Unicode code point in the source text. A byte order mark is not allowed anywhere else in the source.
-      </p>
-      <p>
-      Note that running <kbd>zig fmt</kbd> on a source file will implement all recommendations mentioned here.
-      </p>
-      <p>
-      Note that a tool reading Zig source code can make assumptions if the source code is assumed to be correct Zig code.
-      For example, when identifying the ends of lines, a tool can use a naive search such as <code>/\n/</code>,
-      or an <a href="https://msdn.microsoft.com/en-us/library/dd409797.aspx">advanced</a>
-      search such as <code>/\r\n?|[\n\u0085\u2028\u2029]/</code>, and in either case line endings will be correctly identified.
-      For another example, when identifying the whitespace before the first token on a line,
-      a tool can either use a naive search such as <code>/[ \t]/</code>,
-      or an <a href="https://tc39.es/ecma262/#sec-characterclassescape">advanced</a> search such as <code>/\s/</code>,
-      and in either case whitespace will be correctly identified.
-      </p>
+      LF (byte value 0x0a, code point U+000a, {#syntax#}'\n'{#endsyntax#}) is
+      the line terminator in Zig source code. This byte value terminates every
+      line of Zig source code, including last line of the file.
+      </p>
+      <p>These conservative rules mean that third party tools reading
+      already-validated Zig source code may make simplifying assumptions, such
+      as naively separating lines based on {#syntax#}'\n'{#endsyntax#}.
+      However, tooling such as <kbd>zig fmt</kbd> provides convenience
+      functionality to convert invalid source encodings to valid source
+      encodings, for instance by stripping byte order marks and carriage
+      returns.</p>
       {#header_close#}
 
       {#header_open|Keyword Reference#}