From 8c3a5b49c8ed9a906664f98bcf76c87ab6307a5b Mon Sep 17 00:00:00 2001 From: Russ Cox Date: Wed, 8 Jul 2015 16:35:52 -0400 Subject: content/open-source: fix hyperlinks Change-Id: Icd4157f0a818bf5c93885b3f9c508a03c834a711 Reviewed-on: https://go-review.googlesource.com/11984 Reviewed-by: Russ Cox --- content/open-source.article | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'content/open-source.article') diff --git a/content/open-source.article b/content/open-source.article index 82cd338..cb85b93 100644 --- a/content/open-source.article +++ b/content/open-source.article @@ -96,7 +96,7 @@ Other people have made similar observations. Here are two. Last year, on RedMonk.com, Donnie Berkholz wrote about -[[Go as the emerging language of cloud infrastructure][http://redmonk.com/dberkholz/2014/03/18/go-the-emerging-language-of-cloud-infrastructure/], +“[[http://redmonk.com/dberkholz/2014/03/18/go-the-emerging-language-of-cloud-infrastructure/][Go as the emerging language of cloud infrastructure]],” observing that “[Go's] marquee projects ... are cloud-centric or otherwise made for dealing with distributed systems @@ -104,7 +104,7 @@ or transient environments.” This year, on Texlution.com, the author wrote an article titled -[[Why Golang is doomed to succeed][https://texlution.com/post/why-go-is-doomed-to-succeed/]], +“[[https://texlution.com/post/why-go-is-doomed-to-succeed/][Why Golang is doomed to succeed]],” pointing out that this focus on large-scale development was possibly even better suited to open source than to Google itself: “This open source fitness is why I think -- cgit v1.2.3