aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRob Pike <r@golang.org>2014-10-26 11:27:55 -0700
committerRob Pike <r@golang.org>2014-10-26 11:27:55 -0700
commita9422651f9600c38b3f31f08f1be5a96cb338306 (patch)
tree7ffbe97b0ee8e7a4ea36f20115652d4adeba5fcc
parentffa5e5f7fc51e791427468ebe00a6479191430d7 (diff)
downloadgo-a9422651f9600c38b3f31f08f1be5a96cb338306.tar.gz
go-a9422651f9600c38b3f31f08f1be5a96cb338306.zip
doc/go_faq.html: fix a couple of nits
Wrong article, one stylistic point that bothers someone (but not me). LGTM=bradfitz R=golang-codereviews, bradfitz CC=golang-codereviews https://golang.org/cl/156680043
-rw-r--r--doc/go_faq.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/go_faq.html b/doc/go_faq.html
index ec3689aeb0..9aac058388 100644
--- a/doc/go_faq.html
+++ b/doc/go_faq.html
@@ -1115,7 +1115,7 @@ error but the situation can still be confusing, because sometimes a
<a href="#different_method_sets">pointer
is necessary to satisfy an interface</a>.
The insight is that although a pointer to a concrete type can satisfy
-an interface, with one exception <em>a pointer to an interface can never satisfy a interface</em>.
+an interface, with one exception <em>a pointer to an interface can never satisfy an interface</em>.
</p>
<p>
@@ -1356,7 +1356,7 @@ to speed it up.
</p>
<p>
-Go's goroutine scheduler is not as good as it needs to be. In future, it
+Go's goroutine scheduler is not as good as it needs to be. In the future, it
should recognize such cases and optimize its use of OS threads. For now,
<code>GOMAXPROCS</code> should be set on a per-application basis.
</p>