diff --git a/meeting-notes/20180913.md b/meeting-notes/20180913.md
index df388f84..8be88e6d 100644
--- a/meeting-notes/20180913.md
+++ b/meeting-notes/20180913.md
@@ -15,10 +15,11 @@ We’re still looking for a consensus/further discussion on:
 
 If you’re interested in working on a writeup, please comment on the issue. I’ll be adding some tags to help us organize this. See zulip for the [full log](https://rust-lang.zulipchat.com/#narrow/stream/136281-wg-unsafe-code-guidelines/topic/meeting.202018-09-13).
 
-##How is the format working out?
+## How is the format working out?
 Overall, it seems like the github discussions are productive. However, there’s the question of how we produce concrete summaries/writeups/more permanent artifacts (aka how are we actually writing this reference book?).
 
 **Who/what/why/when/how of writeups**
+
 We should designate people responsible for writeups earlier. This is also a place where we should reach out to members of the community who might be interested/involved in topics elsewhere, but not necessarily aware of the discussions occurring here.
 
 The writeups should reflect whatever consensus was reached in the GH issue—someone will summarize the discussion and open a PR on the mdbook in the repo. We can then iterate on the PR with comments/reviews/suggestions. If needed, we can always merge a starting point PR (for documentation and revisitation) or close a PR if it looks like the topic needs more discussion.
@@ -32,7 +33,7 @@ So, what do I mean by **consensus**? We don’t need to agree on what the answer
 
 We’ll see how this writeup process goes and document it once something seems like it works.
 
-##What’s next?
+## What’s next?
 
 - Oops! We forgot to add a [license](https://github.com/rust-rfcs/unsafe-code-guidelines/issues/20).
 - Start writing up the Data Representation chapter