From 76f233fe045788e71b7460ea82947e4bda6d76ff Mon Sep 17 00:00:00 2001
From: Austin Clements <austin@google.com>
Date: Fri, 5 Jun 2020 09:48:44 -0400
Subject: [PATCH] doc/go1.15: exclude spaces from <code> block

Per the note at the top of go1.15.html.

Updates #37419.

Change-Id: Ia6917347ca1e3ebe8c55f9c0ec74e49ff481a64f
Reviewed-on: https://go-review.googlesource.com/c/go/+/236719
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
---
 doc/go1.15.html | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/doc/go1.15.html b/doc/go1.15.html
index 6c4206d50b..7a1924227c 100644
--- a/doc/go1.15.html
+++ b/doc/go1.15.html
@@ -228,15 +228,15 @@ TODO
 
 <h2 id="compiler">Compiler</h2>
 
-<p><!-- https://golang.org/cl/229578 -->
+<p><!-- CL 229578 -->
   Package <code>unsafe</code>'s <a href="/pkg/unsafe/#Pointer">safety
   rules</a> allow converting an <code>unsafe.Pointer</code>
   into <code>uintptr</code> when calling certain
   functions. Previously, in some cases, the compiler allowed multiple
-  chained conversions (for example, <code>syscall.Syscall(…,
-  uintptr(uintptr(ptr)), …)</code>). The compiler now requires exactly
-  one conversion. Code that used multiple conversions should be
-  updated to satisfy the safety rules.
+  chained conversions (for example, <code>syscall.Syscall(…,</code>
+  <code>uintptr(uintptr(ptr)),</code> <code>…)</code>). The compiler
+  now requires exactly one conversion. Code that used multiple
+  conversions should be updated to satisfy the safety rules.
 </p>
 
 <p><!-- CL 230544, CL 231397 -->
-- 
2.50.0