Merge pull request rust-lang#285 from emberjs/locks-patch-1

Update 0000-template.md

0000-template.md

@@ -2,51 +2,55 @@
 - RFC PR: (leave this empty)
 - Ember Issue: (leave this empty)
 
-# Summary
+# (fill me with the RFC title)
 
-One paragraph explanation of the feature.
+## Summary
 
-# Motivation
+> One paragraph explanation of the feature.
 
-Why are we doing this? What use cases does it support? What is the expected
+## Motivation
+
+> Why are we doing this? What use cases does it support? What is the expected
 outcome?
 
-# Detailed design
+## Detailed design
+
+> This is the bulk of the RFC.
 
-This is the bulk of the RFC. Explain the design in enough detail for somebody
+> Explain the design in enough detail for somebody
 familiar with the framework to understand, and for somebody familiar with the
 implementation to implement. This should get into specifics and corner-cases,
 and include examples of how the feature is used. Any new terminology should be
 defined here.
 
-# How We Teach This
+## How We Teach This
 
-What names and terminology work best for these concepts and why? How is this
+> What names and terminology work best for these concepts and why? How is this
 idea best presented? As a continuation of existing Ember patterns, or as a
 wholly new one?
 
-Would the acceptance of this proposal mean the Ember guides must be
+> Would the acceptance of this proposal mean the Ember guides must be
 re-organized or altered? Does it change how Ember is taught to new users
 at any level?
 
-How should this feature be introduced and taught to existing Ember
+> How should this feature be introduced and taught to existing Ember
 users?
 
-# Drawbacks
+## Drawbacks
 
-Why should we *not* do this? Please consider the impact on teaching Ember,
+> Why should we *not* do this? Please consider the impact on teaching Ember,
 on the integration of this feature with other existing and planned features,
 on the impact of the API churn on existing apps, etc.
 
-There are tradeoffs to choosing any path, please attempt to identify them here.
+> There are tradeoffs to choosing any path, please attempt to identify them here.
 
-# Alternatives
+## Alternatives
 
-What other designs have been considered? What is the impact of not doing this?
+> What other designs have been considered? What is the impact of not doing this?
 
-This section could also include prior art, that is, how other frameworks in the same domain have solved this problem.
+> This section could also include prior art, that is, how other frameworks in the same domain have solved this problem.
 
-# Unresolved questions
+## Unresolved questions
 
-Optional, but suggested for first drafts. What parts of the design are still
+> Optional, but suggested for first drafts. What parts of the design are still
 TBD?