content: use em dashes in module article series links

For the first four articles in the module series, this CL replaces a
hyphen with an em dash before the link to the fifth article, consistent
with other links.

Change-Id: Id9c066079a1467ee432c0284b1692fade32709d1
Reviewed-on: https://go-review.googlesource.com/c/blog/+/244757
Run-TryBot: Jay Conrod <jayconrod@google.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Jean de Klerk <deklerk@google.com>
diff --git a/content/migrating-to-go-modules.article b/content/migrating-to-go-modules.article
index 6fb78b8..c65b013 100644
--- a/content/migrating-to-go-modules.article
+++ b/content/migrating-to-go-modules.article
@@ -13,7 +13,7 @@
   - **Part 2 — Migrating To Go Modules** (this post)
   - Part 3 — [Publishing Go Modules](/publishing-go-modules)
   - Part 4 — [Go Modules: v2 and Beyond](/v2-go-modules)
-  - Part 5 - [Keeping Your Modules Compatible](/module-compatibility)
+  - Part 5 — [Keeping Your Modules Compatible](/module-compatibility)
 
 Go projects use a wide variety of dependency management strategies.
 [Vendoring](https://golang.org/cmd/go/#hdr-Vendor_Directories) tools such
diff --git a/content/publishing-go-modules.article b/content/publishing-go-modules.article
index 0bec57f..951a085 100644
--- a/content/publishing-go-modules.article
+++ b/content/publishing-go-modules.article
@@ -13,7 +13,7 @@
   - Part 2 — [Migrating To Go Modules](/migrating-to-go-modules)
   - **Part 3 — Publishing Go Modules** (this post)
   - Part 4 — [Go Modules: v2 and Beyond](/v2-go-modules)
-  - Part 5 - [Keeping Your Modules Compatible](/module-compatibility)
+  - Part 5 — [Keeping Your Modules Compatible](/module-compatibility)
 
 This post discusses how to write and publish modules so other modules can depend
 on them.
diff --git a/content/using-go-modules.article b/content/using-go-modules.article
index 7325c2a..3894afd 100644
--- a/content/using-go-modules.article
+++ b/content/using-go-modules.article
@@ -15,7 +15,7 @@
   - Part 2 — [Migrating To Go Modules](/migrating-to-go-modules)
   - Part 3 — [Publishing Go Modules](/publishing-go-modules)
   - Part 4 — [Go Modules: v2 and Beyond](/v2-go-modules)
-  - Part 5 - [Keeping Your Modules Compatible](/module-compatibility)
+  - Part 5 — [Keeping Your Modules Compatible](/module-compatibility)
 
 Go 1.11 and 1.12 include preliminary
 [support for modules](https://golang.org/doc/go1.11#modules),
diff --git a/content/v2-go-modules.article b/content/v2-go-modules.article
index fd1afb3..c1693ba 100644
--- a/content/v2-go-modules.article
+++ b/content/v2-go-modules.article
@@ -15,7 +15,7 @@
   - Part 2 — [Migrating To Go Modules](/migrating-to-go-modules)
   - Part 3 — [Publishing Go Modules](/publishing-go-modules)
   - **Part 4 — Go Modules: v2 and Beyond** (this post)
-  - Part 5 - [Keeping Your Modules Compatible](/module-compatibility)
+  - Part 5 — [Keeping Your Modules Compatible](/module-compatibility)
 
 As a successful project matures and new requirements are added, past features
 and design decisions might stop making sense. Developers may want to integrate