diff --git a/content/contributors-summit.article b/content/contributors-summit.article
index a213674..33d41ed 100644
--- a/content/contributors-summit.article
+++ b/content/contributors-summit.article
@@ -1,10 +1,11 @@
-Contributors Summit
+# Contributors Summit
 3 Aug 2017
 Tags: community
+Summary: The day before GopherCon, a group of Go team members and contributors gathered in Denver to discuss and plan for the future of the Go project. This was the first ever event of its kind, a major milestone for the Go project. The event comprised a morning session revolving around focused discussions on a theme, and an afternoon session made up of round table discussions in small break-out groups.
 
 Sam Whited
 
-* Introduction
+## Introduction
 
 The day before GopherCon, a group of Go team members and contributors gathered
 in Denver to discuss and plan for the future of the Go project.
@@ -13,7 +14,7 @@
 theme, and an afternoon session made up of round table discussions in small
 break-out groups.
 
-** Compiler and runtime
+### Compiler and runtime
 
 The compiler and runtime session started out with a discussion about refactoring
 `gc` and related tools into importable packages.
@@ -42,9 +43,9 @@
 I learned a lot about the current state of the world, the problems, and where
 people want to go from here.
 
-** Dependency management
+### Dependency management
 
-After a quick update from the [[https://github.com/golang/dep][dep]] team on the
+After a quick update from the [dep](https://github.com/golang/dep) team on the
 status of the project, the dependency management session gravitated towards how
 the Go world will work once dep (or something dep-like) becomes the primary
 means of package management.
@@ -64,10 +65,10 @@
 There are many good options for making the Go tooling easier to use, and
 discussion will likely continue on the mailing lists.
 
-** The standard library
+### The standard library
 
 The discussions we had around the future of the Go language are mostly covered
-in Russ Cox's blog post: [[https://blog.golang.org//toward-go2][Toward Go 2]], so
+in Russ Cox's blog post: [Toward Go 2](https://blog.golang.org//toward-go2), so
 let's move on to the standard library session.
 
 As a contributor to the standard library and subrepos, this session was
@@ -88,15 +89,15 @@
 For instance, it would be nice if `io.Reader` accepted a context so that
 blocking read operations could be canceled.
 
-More [[https://golang.org/wiki/experiencereports][experience reports]] are
+More [experience reports](https://golang.org/wiki/experiencereports) are
 necessary before we can determine what will change in the standard library.
 
-** Tooling and editors
+### Tooling and editors
 
 A language server for editors to use was a hot topic in the tooling session,
 with a number of people advocating for IDE and tool developers to adopt a common
 "Go Language Server" to index and display information about code and packages.
-Microsoft's [[https://www.github.com/Microsoft/language-server-protocol][Language Server Protocol]]
+Microsoft's [Language Server Protocol](https://www.github.com/Microsoft/language-server-protocol)
 was suggested as a good starting point because of its wide support in editors
 and IDEs.
 
@@ -107,7 +108,7 @@
 experience reports from the community will be required before such an API can be
 designed.
 
-** The contributor experience
+### The contributor experience
 
 The final session of the day was on the contributor experience.
 The first discussion was all about how the current Gerrit workflow could be made
@@ -121,7 +122,7 @@
 Hopefully we'll see improvements to these and many more areas of the
 contribution process in the coming weeks and months!
 
-** Breakout sessions
+### Breakout sessions
 
 In the afternoon, participants broke out into smaller groups to have more
 in-depth discussions about some of the topics from the morning session.
@@ -129,7 +130,7 @@
 For example, one group worked on identifying the useful parts of an experience
 report and a list of existing literature documenting Go user experiences,
 resulting in the experience report
-[[https://golang.org/wiki/experiencereports][wiki page]].
+[wiki page](https://golang.org/wiki/experiencereports).
 
 Another group considered the future of errors in Go.
 Many Go users are initially confused by, or don't understand the fact that
@@ -139,7 +140,7 @@
 these issues in upcoming Go releases, but also ways error handling could be
 improved in Go 2.
 
-* Community
+## Community
 
 Outside of the technical discussions, the summit also provided an opportunity
 for a group of people from all over the world who often talk and work together
@@ -151,7 +152,7 @@
 for discussions both about Go and a little general socialization, which really
 helped to put faces to the names that review our code every day.
 
-As Russ discussed in [[https://blog.golang.org//toward-go2][Toward Go 2]],
+As Russ discussed in [Toward Go 2](https://blog.golang.org//toward-go2),
 communicating effectively requires knowing your audience.
 Having a broad sample of Go contributors in a room together helped us all to
 understand the Go audience better and start many productive discussions about