_content/blog/normalization: update golang.org/x/text links
Fixes golang/go#51891.
Change-Id: I15a634926cb34316c5d1c2231aca470e1763b750
GitHub-Last-Rev: 1478424e1110bb72c966e3e67265b9ba09c1c986
GitHub-Pull-Request: golang/website#147
Reviewed-on: https://go-review.googlesource.com/c/website/+/395134
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Run-TryBot: Dmitri Shuralyov <dmitshur@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Ian Lance Taylor <iant@google.com>
diff --git a/_content/blog/normalization.md b/_content/blog/normalization.md
index aff5705..d336786 100644
--- a/_content/blog/normalization.md
+++ b/_content/blog/normalization.md
@@ -17,7 +17,7 @@
and characters in Go. I've been working on various packages for multilingual
text processing for the go.text repository. Several of these packages deserve a
separate blog post, but today I want to focus on
-[go.text/unicode/norm](https://godoc.org/code.google.com/p/go.text/unicode/norm),
+[go.text/unicode/norm](https://pkg.go.dev/golang.org/x/text/unicode/norm),
which handles normalization, a topic touched in the
[strings article](https://blog.golang.org/strings) and the subject of this
post. Normalization works at a higher level of abstraction than raw bytes.
@@ -58,7 +58,7 @@
As mentioned in the strings blog post, Go does not guarantee that characters in
a string are normalized. However, the go.text packages can compensate. For
example, the
-[collate](https://godoc.org/code.google.com/p/go.text/collate) package, which
+[collate](https://pkg.go.dev/golang.org/x/text/collate) package, which
can sort strings in a language-specific way, works correctly even with
unnormalized strings. The packages in go.text do not always require normalized
input, but in general normalization may be necessary for consistent results.
@@ -136,7 +136,7 @@
in and output your text as NFC like the rest of the world.
To write your text as NFC, use the
-[unicode/norm](https://godoc.org/code.google.com/p/go.text/unicode/norm) package
+[unicode/norm](https://pkg.go.dev/golang.org/x/text/unicode/norm) package
to wrap your `io.Writer` of choice:
wc := norm.NFC.Writer(w)
@@ -213,7 +213,7 @@
Another tool provided by the norm package that may help dealing with character
boundaries is its iterator,
-[`norm.Iter`](https://godoc.org/code.google.com/p/go.text/unicode/norm#Iter).
+[`norm.Iter`](https://pkg.go.dev/golang.org/x/text/unicode/norm#Iter).
It iterates over characters one at a time in the normal form of choice.
## Performing magic
@@ -253,7 +253,7 @@
to minimize the need for normalization at run time. The type `norm.Properties`
provides access to the per-rune information needed by these packages, most
notably the Canonical Combining Class and decomposition information. Read the
-[documentation](https://godoc.org/code.google.com/p/go.text/unicode/norm/#Properties)
+[documentation](https://pkg.go.dev/golang.org/x/text/unicode/norm#Properties)
for this type if you want to dig deeper.
## Performance
