content: remove irrelevant bug documentation
The aforementioned bug has been resolved in https://golang.org/cl/183991.
Removing it from the blog content reduces cognitive overhead for readers.
Change-Id: I19b944599d97895217e3178b31edf6a25c4c1fdc
GitHub-Last-Rev: b7ec54580b8d1cd9c37d261bb92d95d955696149
GitHub-Pull-Request: golang/blog#48
Reviewed-on: https://go-review.googlesource.com/c/blog/+/277612
Reviewed-by: Bryan C. Mills <bcmills@google.com>
diff --git a/content/using-go-modules.article b/content/using-go-modules.article
index 3894afd..3f706ba 100644
--- a/content/using-go-modules.article
+++ b/content/using-go-modules.article
@@ -422,7 +422,7 @@
Reading the docs, we can see that `Hello` has become `HelloV3`:
$ go doc rsc.io/quote/v3
- package quote // import "rsc.io/quote"
+ package quote // import "rsc.io/quote/v3"
Package quote collects pithy sayings.
@@ -433,10 +433,6 @@
func OptV3() string
$
-(There is also a
-[known bug](https://golang.org/issue/30778) in the output;
-the displayed import path has incorrectly dropped the `/v3`.)
-
We can update our use of `quote.Hello()` in `hello.go` to use `quoteV3.HelloV3()`:
package hello
