Commit 1d879fe7 authored by Rob Pike's avatar Rob Pike

doc/go1.3.html: fix spelling mistakes

Keep those builders busy.

LGTM=bradfitz
R=golang-codereviews, bradfitz
CC=golang-codereviews
https://golang.org/cl/85710046
parent 2dbc5d26
...@@ -192,7 +192,7 @@ is now about 40% faster. ...@@ -192,7 +192,7 @@ is now about 40% faster.
<li> <li>
The regular expression package <a href="/pkg/regexp/"><code>regexp</code></a> The regular expression package <a href="/pkg/regexp/"><code>regexp</code></a>
is now significantly faster for certain simple expressions due to the implemenation of is now significantly faster for certain simple expressions due to the implementation of
a second, one-pass execution engine. The choice of which engine to use is automatic; a second, one-pass execution engine. The choice of which engine to use is automatic;
the details are hidden from the user. the details are hidden from the user.
</li> </li>
...@@ -216,7 +216,7 @@ No new packages appear in the core libraries in Go 1.3. ...@@ -216,7 +216,7 @@ No new packages appear in the core libraries in Go 1.3.
<p> <p>
A previous bug in <a href="/pkg/crypto/tls/"><code>crypto/tls</code></a> A previous bug in <a href="/pkg/crypto/tls/"><code>crypto/tls</code></a>
made it possible to skip verfication in TLS inadvertently. made it possible to skip verification in TLS inadvertently.
In Go 1.3, the bug is fixed: one must specify either ServerName or In Go 1.3, the bug is fixed: one must specify either ServerName or
InsecureSkipVerify, and if ServerName is specified it is enforced. InsecureSkipVerify, and if ServerName is specified it is enforced.
This may break existing code that incorrectly depended on insecure This may break existing code that incorrectly depended on insecure
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment