Merge pull request project-open-data#255 from leahbannon/small-edits

fixing markdown in front of 'background'

Author: gbinal

governance.md

@@ -7,13 +7,14 @@ published: true
 ---
 
 # Project Open Data Governance
+
 ## Background
 Project Open Data is an online collection of code, best practices, and case studies developed to help agencies adopt the framework presented in the OMB memorandum M-13-13 “[Open Data Policy-Managing Information as an Asset](/policy-memo).” Project Open Data will evolve over time as a community resource to facilitate adoption of open data practices. To facilitate collaboration across the Federal Government and in partnership with public developers, the Project is published on the developer social network GitHub.
 
 As the Project founders, the Office of Management and Budget and the Office of Science and Technology Policy, components of the Executive Office of the President, are dedicated to maximizing openness, participation, and collaboration while ensuring the integrity of the resources hosted within the Project. This page provides information on ways to participate in the Project and how the OMB and OSTP will govern it.
 
 ##Contributing
-Project Open Data is a collaborative, open source project.  Both Federal employees and members of the public are strongly encouraged to improve the project by contributing.  Fortunately, contributing is very easy. Simply click the “Improve this content” button at the top of every page, make your edit, and hit “submit.” Your changes will appear once they are approved. Ultimately, the goal is for users to contribute to the project by suggesting changes to code/content (making “[pull requests](https://help.github.com/articles/using-pull-requests)”).
+Project Open Data is a collaborative, open source project.  Both Federal employees and members of the public are strongly encouraged to improve the project by contributing.  Fortunately, contributing is very easy. Simply log into GitHub, click the “Improve this content” button at the top of every page, make your edit, and hit “submit.” Your changes will appear once they are approved. Ultimately, the goal is for users to contribute to the project by suggesting changes to code/content (making “[pull requests](https://help.github.com/articles/using-pull-requests)”).
 However, there are many ways to participate:
 
 * _Browse_. Look around at the different resources available.
@@ -35,4 +36,4 @@ Given that the breadth of Project Open Data supports both technical and policy w
 There are two policies repos that will have very regulated release cycles:
 
 * _Common Core Metadata Schema_— Changes to the common core metadata schema will be reviewed on an ongoing basis. Starting November 9th, new releases of the schema will only be issued every 6 months, as needed. Suggested changes that alter implementation and structure of the schema will not be merged in-between the regular release cycles, though discussion and commenting during these periods are encouraged. Each version of the schema will have a depreciation date of one year.   
-* _The Open Data Policy M-13-13_— A version of The Open Data Policy (M-13-13) is available for public feedback and suggested changes through Project Open Data. Suggested changes to the policy will be reviewed bi-annually.  Adjudication times will depend on the extent of the suggested policy changes and decisions regarding the mechanism for dissemination (e.g., the need to consider updating official version of M-13-13, or other forms of guidance). Accepted changes to the policy will not be merged in-between the regular release cycles to prevent inconsistencies and confusion, though discussion and commenting during these periods are encouraged.
+* _The Open Data Policy M-13-13_— A version of The Open Data Policy (M-13-13) is available for public feedback and suggested changes through Project Open Data. Suggested changes to the policy will be reviewed bi-annually.  Adjudication times will depend on the extent of the suggested policy changes and decisions regarding the mechanism for dissemination (e.g., the need to consider updating official version of M-13-13, or other forms of guidance). Accepted changes to the policy will not be merged in-between the regular release cycles to prevent inconsistencies and confusion, though discussion and commenting during these periods are encouraged.