2 files changed, 45 insertions, 49 deletions
diff --git a/events/2016/developer-summit-2016/KubDevSummitVoting.md b/events/2016/developer-summit-2016/KubDevSummitVoting.md
index 46909c02..265a27e5 100644
--- a/events/2016/developer-summit-2016/KubDevSummitVoting.md
+++ b/events/2016/developer-summit-2016/KubDevSummitVoting.md
@@ -1,33 +1,31 @@
-###Kubernetes Developer's Summit Discussion Topics Voting
-###
-A voting poll for discussion topic proposals has been created, and the link to the poll can be found [here][poll]. 
-
-The poll will close on 10/07/16 at 23:59:59 PDT. 
-
-#### How Does it Work?
-####
-The voting uses the Condorcet method, which relies on relative rankings to pick winners. You can read more about the Condorcet method and the voting service we're using on the [CIVS website][civs].
-
-There are 27 topics to choose from, and you will rank them from 1 (favorite) to 27 (least favorite). You can also mark "no opinion" on topics that you don't wish to include in the ranking. 
-
-The poll on CIVS has just the topic titles for ease of viewing. For topic descriptions, please see this [spreadsheet][topics]. The topic order on the voting service should mirror the order on the spreadsheet. 
-
-You will note the message saying "*Only the 15 favorite choices will win the poll*". CIVS requires a number be selected for winners, and we have arbitrarily chosen 15. The final schedule may include more or less than 15 of the submitted topics. 
-
-##### A Small Request 
-#####
-
-In order to make the poll accessible via URL, it has to be made "public". This means than any unique IP address can vote, which can be easily exploited for multiple votes. 
-
-We fully expect the community to behave with sportsmanship and only vote once, and as such we almost didn't bring this concern up to begin with. However, we have chosen to explicitly address it, in order to reiterate the importance of everyone's voice receiving equal weight in a community-driven event.
-
-#### After the Poll
-####
-A schedule will be made from the winning topics with
-some editorial license, and the schedule will be announced to the group
-at least a week before the event.
-
-[//]: # (Reference Links)
-   [civs]: <http://civs.cs.cornell.edu/>
-   [poll]: <http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_9ef4ac5e58c4cab1&akey=7cc2652f9715b525>
-   [topics]: <https://docs.google.com/spreadsheets/d/1bmp6uLG8H32MVz02-zsieeKKZDZITw-8B6UjOaNTXOA/edit?usp=sharing>
-\ No newline at end of file
+### Kubernetes Developer's Summit Discussion Topics Voting
+
+A voting poll for discussion topic proposals has been created, and the link to the poll can be found [here][poll].
+
+The poll will close on 10/07/16 at 23:59:59 PDT.
+
+#### How Does it Work?
+
+The voting uses the Condorcet method, which relies on relative rankings to pick winners. You can read more about the Condorcet method and the voting service we're using on the [CIVS website][civs].
+
+There are 27 topics to choose from, and you will rank them from 1 (favorite) to 27 (least favorite). You can also mark "no opinion" on topics that you don't wish to include in the ranking.
+
+The poll on CIVS has just the topic titles for ease of viewing. For topic descriptions, please see this [spreadsheet][topics]. The topic order on the voting service should mirror the order on the spreadsheet.
+
+You will note the message saying "*Only the 15 favorite choices will win the poll*". CIVS requires a number be selected for winners, and we have arbitrarily chosen 15. The final schedule may include more or less than 15 of the submitted topics.
+
+##### A Small Request
+
+In order to make the poll accessible via URL, it has to be made "public". This means than any unique IP address can vote, which can be easily exploited for multiple votes.
+
+We fully expect the community to behave with sportsmanship and only vote once, and as such we almost didn't bring this concern up to begin with. However, we have chosen to explicitly address it, in order to reiterate the importance of everyone's voice receiving equal weight in a community-driven event.
+
+#### After the Poll
+
+A schedule will be made from the winning topics with
+some editorial license, and the schedule will be announced to the group
+at least a week before the event.
+
+[civs]: <http://civs.cs.cornell.edu/>
+[poll]: <http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_9ef4ac5e58c4cab1&akey=7cc2652f9715b525>
+[topics]: <https://docs.google.com/spreadsheets/d/1bmp6uLG8H32MVz02-zsieeKKZDZITw-8B6UjOaNTXOA/edit?usp=sharing>
diff --git a/events/2016/developer-summit-2016/Kubernetes_Dev_Summit.md b/events/2016/developer-summit-2016/Kubernetes_Dev_Summit.md
index f66df508..e0448e41 100644
--- a/events/2016/developer-summit-2016/Kubernetes_Dev_Summit.md
+++ b/events/2016/developer-summit-2016/Kubernetes_Dev_Summit.md
@@ -1,12 +1,11 @@
 # Kubernetes Dev Summit
-# 
 
 ## Edit - Event Location
-##
+
 The event is on the 4th Floor of the *Union Street Tower* of the Sheraton Seattle Hotel. 
 
 # About the Event
-#
+
 The Kubernetes Developers' Summit provides an avenue for Kubernetes
 developers  to connect face to face and mindshare about future community
 development and community governance endeavors.
@@ -15,7 +14,7 @@ In some sense, the summit is a real-life extension of the community
 meetings and SIG meetings.
 
 ## Event Format
-## 
+
 The Dev Summit is a "loosely-structured [unconference][uncf]". Rather
 than speakers and presentations, we will have moderators/facilitators
 and discussion topics, alongside all-day completely unstructured
@@ -35,7 +34,7 @@ Then, there will be 2 smaller rooms for hacking / unstructured
 discussion all day.
 
 #### Who Should Go?
-#### 
+
 The target audience is the Kubernetes developer community. The group
 will be relatively small (~120-150 attendees), to improve communication
 and facilitate easier decision-making. The majority of the attendees
@@ -52,7 +51,7 @@ Please note that this Summit is not the right environment for people to
 involved initially.
 
 #### Call for Proposals
-#### 
+
 Proposals for discussion topics can be submitted through [this
 form][propfrm] by September 30, 23:59 PT. If you propose a session topic,
 please be prepared to attend and facilitate the session if it gets
@@ -71,7 +70,7 @@ some editorial license, and the schedule will be announced to the group
 at least a week before the event.
 
 ## When & Where?
-## 
+
 The Dev Summit will follow [Kubecon][kbc] on November 10th, 2016.
 Fortunately for those who attend Kubecon, the Dev Summit will be at the
 same venue, [the Sheraton Seattle Hotel][sher]. As of now, the day's
@@ -79,18 +78,17 @@ activities should run from breakfast being served at 8 AM to closing
 remarks ending around 3:30 PM, with an external happy hour to follow.
 
 ## Desired outcomes
-## 
+
 * Generate notes from the sessions to feed the project's documentation
 and knowledge base, and also to keep non-attendees plugged in 
 * Make (and document) recommendations and decisions for the near-term and
 mid-term future of the project 
 * Come up with upcoming action items, as well as leaders for those action items, for the various topics that we discuss
 
-[//]: # (Reference Links)
-   [uncf]: <https://en.wikipedia.org/wiki/Unconference>
-   [mtp]: <http://www.meetup.com/topics/kubernetes/all/>
-   [lotfrm]: <https://docs.google.com/forms/d/e/1FAIpQLSe8t6pvRjh1OeF6xrXKbXmzHGMhQ4c-MbZ6QUr9APJNjpgAzA/viewform>
-   [propfrm]: <https://docs.google.com/forms/d/e/1FAIpQLSf30x18OGCv_Und7qah4y5Zs3Z-0YoBCo964ZsmhtbxBjMzxA/viewform>
-   [civs]: <http://civs.cs.cornell.edu/>
-   [kbc]: <http://events.linuxfoundation.org/events/kubecon>
-   [sher]: <http://www.sheratonseattle.com/>
+[uncf]: <https://en.wikipedia.org/wiki/Unconference>
+[mtp]: <http://www.meetup.com/topics/kubernetes/all/>
+[lotfrm]: <https://docs.google.com/forms/d/e/1FAIpQLSe8t6pvRjh1OeF6xrXKbXmzHGMhQ4c-MbZ6QUr9APJNjpgAzA/viewform>
+[propfrm]: <https://docs.google.com/forms/d/e/1FAIpQLSf30x18OGCv_Und7qah4y5Zs3Z-0YoBCo964ZsmhtbxBjMzxA/viewform>
+[civs]: <http://civs.cs.cornell.edu/>
+[kbc]: <http://events.linuxfoundation.org/events/kubecon>
+[sher]: <http://www.sheratonseattle.com/>