change the naming example from Vector to Ring due to loss of vector.New()

R=rsc
CC=golang-dev
https://golang.org/cl/164082

diff --git a/doc/effective_go.html b/doc/effective_go.html
index 3ab05fc1cf2611f074fbb0f97e2864656bfd4d28..5c786b4514a53c5a5da8bc78ad73bdaadfb24bff 100644 (file)
--- a/doc/effective_go.html
+++ b/doc/effective_go.html
@@ -308,12 +308,12 @@ which is a clear, concise name.
 Moreover,
 because imported entities are always addressed with their package name, <code>bufio.Reader</code>
 does not conflict with <code>io.Reader</code>.
-Similarly, the function to make new instances of <code>vector.Vector</code>&mdash;which
+Similarly, the function to make new instances of <code>ring.Ring</code>&mdash;which
 is the definition of a <em>constructor</em> in Go&mdash;would
-normally be called <code>NewVector</code>, but since
-<code>Vector</code> is the only type exported by the package, and since the
-package is called <code>vector</code>, it's called just <code>New</code>.
-Clients of the package see that as <code>vector.New</code>.
+normally be called <code>NewRing</code>, but since
+<code>Ring</code> is the only type exported by the package, and since the
+package is called <code>ring</code>, it's called just <code>New</code>.
+Clients of the package see that as <code>ring.New</code>.
 Use the package structure to help you choose good names.
 </p>