aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJean de Klerk <deklerk@google.com>2019-11-07 15:35:38 -0700
committerAndrew Bonventre <andybons@golang.org>2019-11-07 22:36:19 +0000
commit498b2a48ebbe8ac260bd80b8c436a66141693eb3 (patch)
treec7240ea1da70e5306ff7c8cc94e674b264f752c1
parente330e64302df4bd5b1d90575a4a30b284a1ec27e (diff)
content: fix numbering on v2 post
Change-Id: Ic338e840a45ddf4f7da2de18941c352fab882bfb Reviewed-on: https://go-review.googlesource.com/c/blog/+/205919 Reviewed-by: Andrew Bonventre <andybons@golang.org>
-rw-r--r--content/v2-go-modules.article2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/v2-go-modules.article b/content/v2-go-modules.article
index f66f134..634c3dc 100644
--- a/content/v2-go-modules.article
+++ b/content/v2-go-modules.article
@@ -13,7 +13,7 @@ This post is part 4 in a series.
- Part 1 — [[/using-go-modules][Using Go Modules]]
- Part 2 — [[/migrating-to-go-modules][Migrating To Go Modules]]
- Part 3 — [[/publishing-go-modules][Publishing Go Modules]]
-- *Part*3*—*Go*Modules:*v2*and*Beyond* (this post)
+- *Part*4*—*Go*Modules:*v2*and*Beyond* (this post)
As a successful project matures and new requirements are added, past features
and design decisions might stop making sense. Developers may want to integrate