content/go1.15-proposals.article: use relative links for other blog articles
Change-Id: I5ee0c1e2688fe1d42bc03e5435eb7f9eb9944c65
Reviewed-on: https://go-review.googlesource.com/c/blog/+/216626
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
diff --git a/content/go1.15-proposals.article b/content/go1.15-proposals.article
index 01bfe48..62a3034 100644
--- a/content/go1.15-proposals.article
+++ b/content/go1.15-proposals.article
@@ -9,7 +9,7 @@
We are close to the Go 1.14 release, planned for February assuming all goes
well, with an RC1 candidate almost ready. Per the process outlined in the
-[[https://blog.golang.org/go2-here-we-come][Go 2, here we come!]] blog post,
+[[/go2-here-we-come][Go 2, here we come!]] blog post,
it is again the time in our development and release cycle to consider if and
what language or library changes we might want to include for our next release,
Go 1.15, scheduled for August of this year.
@@ -81,7 +81,7 @@
to have the proposals implemented at the beginning of the Go 1.15 release cycle
(at or shortly after the Go 1.14 release) so that there is plenty of time to
gather experience and provide feedback. Per the
-[[https://blog.golang.org/go2-here-we-come][proposal evaluation process]],
+[[/go2-here-we-come][proposal evaluation process]],
the final decision will be made at the end of the development cycle, at the
beginning of May, 2020.
