From 498b2a48ebbe8ac260bd80b8c436a66141693eb3 Mon Sep 17 00:00:00 2001 From: Jean de Klerk Date: Thu, 7 Nov 2019 15:35:38 -0700 Subject: content: fix numbering on v2 post Change-Id: Ic338e840a45ddf4f7da2de18941c352fab882bfb Reviewed-on: https://go-review.googlesource.com/c/blog/+/205919 Reviewed-by: Andrew Bonventre --- content/v2-go-modules.article | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 -- cgit v1.2.3