From bb0a8fd38f4b14f79b0da1cfe3e732f3bfb63a51 Mon Sep 17 00:00:00 2001
From: Rob Pike <r@golang.org>
Date: Fri, 20 Sep 2019 16:10:03 +1000
Subject: [PATCH] doc: reword to avoid the confusing term 'anew'

Fixes #34415

Change-Id: I8eaa7606ae01e569a076cf7f3c28dbec2a153001
Reviewed-on: https://go-review.googlesource.com/c/go/+/196578
Reviewed-by: Emmanuel Odeke <emm.odeke@gmail.com>
---
 doc/effective_go.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/effective_go.html b/doc/effective_go.html
index 158f39ebc8..be9b8aef9c 100644
--- a/doc/effective_go.html
+++ b/doc/effective_go.html
@@ -624,7 +624,7 @@ if it has already been declared, provided:
 <li>this declaration is in the same scope as the existing declaration of <code>v</code>
 (if <code>v</code> is already declared in an outer scope, the declaration will create a new variable §),</li>
 <li>the corresponding value in the initialization is assignable to <code>v</code>, and</li>
-<li>there is at least one other variable in the declaration that is being declared anew.</li>
+<li>there is at least one other variable that is created by the declaration.</li>
 </ul>
 
 <p>
-- 
2.50.0