diff --git a/content/toward-go2.article b/content/toward-go2.article
index 0c506af..ae7f6df 100644
--- a/content/toward-go2.article
+++ b/content/toward-go2.article
@@ -37,7 +37,7 @@
 </div>
 
 With more help from the Go community, we revised and implemented that
-plan, eventually [releasing Go 1](https://blog.golang.org/go-version-1-is-released) on March 28, 2012.
+plan, eventually [releasing Go 1](https://blog.golang.org/go1) on March 28, 2012.
 
 <div style="margin-left: 2em;">
 .image toward-go2/go1-release.png _ 556
@@ -52,7 +52,7 @@
 programs nearly every week. We understood that this was keeping Go
 from use in production settings, where programs could not be rewritten
 weekly to keep up with language changes.
-As the [blog post announcing Go 1](https://blog.golang.org/go-version-1-is-released) says, the driving motivation was to provide a stable foundation
+As the [blog post announcing Go 1](https://blog.golang.org/go1) says, the driving motivation was to provide a stable foundation
 for creating reliable products, projects, and publications (blogs,
 tutorials, conference talks, and books), to make users confident that
 their programs would continue to compile and run without change for
diff --git a/rewrite.go b/rewrite.go
index 6ab9121..ecb3397 100644
--- a/rewrite.go
+++ b/rewrite.go
@@ -62,7 +62,7 @@
 	"/2011/12/building-stathat-with-go.html":                 "building-stathat-with-go",
 	"/2011/12/from-zero-to-go-launching-on-google.html":      "from-zero-to-go-launching-on-google",
 	"/2011/12/getting-to-know-go-community.html":             "getting-to-know-go-community",
-	"/2012/03/go-version-1-is-released.html":                 "go-version-1-is-released",
+	"/2012/03/go-version-1-is-released.html":                 "go1",
 	"/2012/07/gccgo-in-gcc-471.html":                         "gccgo-in-gcc-471",
 	"/2012/07/go-videos-from-google-io-2012.html":            "go-videos-from-google-io-2012",
 	"/2012/08/go-updates-in-app-engine-171.html":             "go-updates-in-app-engine-171",