From: Andrew Gerrand <adg@golang.org>
Date: Mon, 22 Apr 2013 14:57:23 +0000 (+0200)
Subject: doc: fix typo in Effective Go
X-Git-Tag: go1.1rc2~66
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=994c486aa93a443a6cd32a4caa0884b2129392d5;p=gostls13.git

doc: fix typo in Effective Go

Fixes #5329.

R=golang-dev, bradfitz
CC=golang-dev
https://golang.org/cl/8897044
---

diff --git a/doc/effective_go.html b/doc/effective_go.html
index bdbef68c7c..62851871c5 100644
--- a/doc/effective_go.html
+++ b/doc/effective_go.html
@@ -3414,7 +3414,7 @@ func Compile(str string) (regexp *Regexp, err error) {
 <p>
 If <code>doParse</code> panics, the recovery block will set the
 return value to <code>nil</code>&mdash;deferred functions can modify
-named return values.  It then will then check, in the assignment
+named return values.  It will then check, in the assignment
 to <code>err</code>, that the problem was a parse error by asserting
 that it has the local type <code>Error</code>.
 If it does not, the type assertion will fail, causing a run-time error