Update 2017-08-11-gsoc-peey-1.md

babel · Aug 11, 2017 · cc04f11 · cc04f11
1 parent 0c75299
commit cc04f11
Showing 1 changed file with 8 additions and 8 deletions.
diff --git a/_posts/2017-08-11-gsoc-peey-1.md b/_posts/2017-08-11-gsoc-peey-1.md
@@ -104,22 +104,22 @@ smoothly from here onwards.
 
 ## Footnotes
 
-1.  We have a shortage of manpower when it comes to reviewing PRs. It was also
+1. We have a shortage of manpower when it comes to reviewing PRs. It was also
 recently discussed in one of our weekly meetings ([link to the meeting
 notes](https://github.com/babel/notes/blob/master/2017-06/june-21.md#priority-topics)).
 Perhaps you could help us with this. Drop by [our slack
 chatroom](https://slack.babeljs.io/) and offer your help!
-2.  I feel that the myth stems from the fact that when you’re new to the project the
+2. I feel that the myth stems from the fact that when you’re new to the project the
 mentors definitely do know more about the project than you
-3.  (to illustrate) Some random factors which might affect the chances of you
+3. (to illustrate) Some random factors which might affect the chances of you
 getting help:
-  - If someone was online who worked on the same thing when you post a question on
+- If someone was online who worked on the same thing when you post a question on
 the chatroom
-  - Someone who knows your doubt will take a lot of time to deal with and they
+- Someone who knows your doubt will take a lot of time to deal with and they
 want to give you personal attention and not just throw information at you
-  - Someone who’s able to gauge where you’re coming from, and so on.
-4.  We’d been stuck for [a while](https://github.com/babel/babel/issues/2645) since
-*a lot *of people use a nonstandard implementation for decorators which came at
+- Someone who’s able to gauge where you’re coming from, and so on.
+4. We’d been stuck for [a while](https://github.com/babel/babel/issues/2645) since
+*a lot* of people use a nonstandard implementation for decorators which came at
 around the time the spec was in stage-0. The changes in the spec are not
 backwards-compatible so we were unsure on how we should introduce support for
 the new spec without causing much disruption for people who use Babel. We