moving toc

Author: stoopidJSON

README.md

@@ -1,3 +1,10 @@
+# ProjectTemplate
+The project template for Code for Baltimore github projects.  This project will help your project get started by giving you:
+* A standard issues template
+* A standard pull request
+* A standard docs folder with example documentation.
+* A big thumbs up :thumbsup:
+
 <!-- TOC -->
 
 - [ProjectTemplate](#projecttemplate)
@@ -10,13 +17,6 @@
 
 <!-- /TOC -->
 
-# ProjectTemplate
-The project template for Code for Baltimore github projects.  This project will help your project get started by giving you:
-* A standard issues template
-* A standard pull request
-* A standard docs folder with example documentation.
-* A big thumbs up :thumbsup:
-
 ## Documentation
 We've included a `docs` folder with a template [Tech Spec](/docs/Tech_Spec.md) and [Best Practices](/docs/Best_Practices.md) document, though using Github's Wiki capabilities is also a good idea. This will get you started with documenting your project.  Other documents and relevant information that has no other place can live in the `docs` folder.  Replace this paragraph with a brief breakdown of what you've included in your `docs` folder.
 

docs/Best_Practices.md

@@ -1,3 +1,6 @@
+# Best Practices
+Code for Baltimore projects should be built with the intention of deploying on [Heroku](https://heroku.com) or [Netlify](https://netlify.com). For details on Heroku Best Practices see their [developer documentation](https://devcenter.heroku.com/articles/node-best-practices).
+
 <!-- TOC -->
 
 - [Best Practices](#best-practices)
@@ -14,9 +17,6 @@
 
 <!-- /TOC -->
 
-# Best Practices
-Code for Baltimore projects should be built with the intention of deploying on [Heroku](https://heroku.com) or [Netlify](https://netlify.com). For details on Heroku Best Practices see their [developer documentation](https://devcenter.heroku.com/articles/node-best-practices).
-
 ## Project Management
 We are using Github Issues to track outstanding issues and work for projects.
 

docs/Tech_Spec.md

@@ -1,3 +1,8 @@
+
+
+# Tech Spec
+The _Tech Spec_ is an important part of a project, but it's a part that's often overlooked or skipped. The intention of this document is to organize everyone's thoughts on the project into one simple, succinct document. It doesn't have to be super detailed but filling out this document will help keep everyone focused on the project goal.
+
 <!-- TOC -->
 
 - [Tech Spec](#tech-spec)
@@ -12,9 +17,6 @@
 
 <!-- /TOC -->
 
-# Tech Spec
-The _Tech Spec_ is an important part of a project, but it's a part that's often overlooked or skipped. The intention of this document is to organize everyone's thoughts on the project into one simple, succinct document. It doesn't have to be super detailed but filling out this document will help keep everyone focused on the project goal.
-
 ## Overview
 This section should be comprised of 1-3 short paragraphs giving a high-level overview of what the project hopes to accomplish. This overview should quickly define what the project hopes to do, what this document will cover, and what will not be covered.