content: fix link formatting in 'Migrating to Go Modules'
Change-Id: I752bd1667a361248f5057087c6c61ba6a504ab57
Reviewed-on: https://go-review.googlesource.com/c/blog/+/191158
Reviewed-by: Jean de Klerk <deklerk@google.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
diff --git a/content/migrating-to-go-modules.article b/content/migrating-to-go-modules.article
index 7c87db7..37bbb89 100644
--- a/content/migrating-to-go-modules.article
+++ b/content/migrating-to-go-modules.article
@@ -112,7 +112,7 @@
go 1.12
$
-Without a configuration file from a previous dependency manager, `go`mod`init` will create a `go.mod` file with only the `module` and `go` directives. In this example, we set the module path to `golang.org/x/blog` because that is its [https://golang.org/cmd/go/#hdr-Remote_import_paths][custom import path]. Users may import packages with this path, and we must be careful not to change it.
+Without a configuration file from a previous dependency manager, `go`mod`init` will create a `go.mod` file with only the `module` and `go` directives. In this example, we set the module path to `golang.org/x/blog` because that is its [[https://golang.org/cmd/go/#hdr-Remote_import_paths][custom import path]]. Users may import packages with this path, and we must be careful not to change it.
The `module` directive declares the module path, and the `go` directive declares the expected version of the Go language used to compile the code within the module.
