From 0c8415699e0a790551b2f6964efac2569a997bfd Mon Sep 17 00:00:00 2001
From: Rob Pike <r@golang.org>
Date: Fri, 21 Mar 2014 08:37:27 +1100
Subject: [PATCH] doc/effective_go.html: fix typo Prose referred to 'b', code
 used 'buf'. Fixes #7601.

LGTM=dominik.honnef
R=golang-codereviews, dominik.honnef
CC=golang-codereviews
https://golang.org/cl/78470043
---
 doc/effective_go.html | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/doc/effective_go.html b/doc/effective_go.html
index 74f9f3db9f..6006724e5a 100644
--- a/doc/effective_go.html
+++ b/doc/effective_go.html
@@ -1386,8 +1386,9 @@ func (file *File) Read(buf []byte) (n int, err error)
 </pre>
 <p>
 The method returns the number of bytes read and an error value, if
-any.  To read into the first 32 bytes of a larger buffer
-<code>b</code>, <i>slice</i> (here used as a verb) the buffer.
+any.
+To read into the first 32 bytes of a larger buffer
+<code>buf</code>, <i>slice</i> (here used as a verb) the buffer.
 </p>
 <pre>
     n, err := f.Read(buf[0:32])
@@ -1488,7 +1489,7 @@ If the slices might grow or shrink, they should be allocated independently
 to avoid overwriting the next line; if not, it can be more efficient to construct
 the object with a single allocation.
 For reference, here are sketches of the two methods.
-First, a line a time:
+First, a line at a time:
 </p>
 
 <pre>
-- 
2.50.0