[x/blog] content: add missing word to migrating-to-go-modules
Change-Id: Ic3a9e4ef81408b6bb1a0f0b73eb3e4ed5994260c
Reviewed-on: https://go-review.googlesource.com/c/blog/+/191177
Reviewed-by: Ian Lance Taylor <iant@golang.org>
X-Blog-Commit: de9a6dab436af6b5ae84dabf1202a651f48b6f79
diff --git a/blog/content/migrating-to-go-modules.article b/blog/content/migrating-to-go-modules.article
index 37bbb89..162560d 100644
--- a/blog/content/migrating-to-go-modules.article
+++ b/blog/content/migrating-to-go-modules.article
@@ -199,7 +199,7 @@
* Conclusion
-Converting to Go modules should be a straightforward process for most users. Occasional issues may arise due to non-canonical import paths or breaking changes within dependency. Future posts will explore publishing new versions, v2 and beyond, and ways to debug strange situations.
+Converting to Go modules should be a straightforward process for most users. Occasional issues may arise due to non-canonical import paths or breaking changes within a dependency. Future posts will explore publishing new versions, v2 and beyond, and ways to debug strange situations.
To provide feedback and help shape the future of dependency management in Go, please send us [[https://golang.org/issue/new][bug reports]] or [[https://golang.org/wiki/ExperienceReports][experience reports]].
