Squash Maruku warnings related to links

Author: James McKinney

faq.md

@@ -56,7 +56,7 @@ Anyone – Federal employees, contractors, developers, the general public – ca
 
 ### Are my interactions to this project subject to any special privacy considerations?
 
-Comments, pull requests, and any other messages received through this repository may be subject to the [Presidential Records Act](http://www.archives.gov/about/laws/presidential-records.html), and may be archived. Learn more at [http://WhiteHouse.gov/privacy].
+Comments, pull requests, and any other messages received through this repository may be subject to the [Presidential Records Act](http://www.archives.gov/about/laws/presidential-records.html), and may be archived. Learn more at [http://WhiteHouse.gov/privacy](http://WhiteHouse.gov/privacy).
 
 ### Who is in charge of Project Open Data?  
 

implementation-guide.md

@@ -7,7 +7,7 @@ filename: implementation-guide.md
 
 
 ## 1) Create and maintain an enterprise data inventory
-*[Due by 11/9/13]*
+*\[Due by 11/9/13\]*
 
 Maintain a complete listing of all datasets owned, managed, collected, and/or created by your agency, described in a common format.
 
@@ -28,7 +28,7 @@ This listing can be maintained in a Data Management System (DMS) such as the ope
 
 
 ## 2) Create and maintain a public data inventory
-*[Due by 11/9/13]*
+*\[Due by 11/9/13\]*
 
 Maintain a publicly accessible listing of all datasets maintained by your agency for harvesting by a central Data.gov search engine and the public at large.
 
@@ -38,7 +38,7 @@ While agencies are only required to list datasets with an "Access Level" value o
 
 Document any datasets or metadata in your enterprise data inventory that your agency does not believe can be made publicly available, in consultation with your Office of General Counsel or its equivalent.
 
-Publish your agency’s enterprise data inventory, with the aforementioned information removed, to a file located at [agency].gov/data.json and described using (at minimum) the [common core metadata](http://project-open-data.github.io/schema/). This file itself must be listed as a dataset within itself (see [an example of format](http://project-open-data.github.io/examples/catalog-sample-extended.json) ); if you have multiple data.json files across your agency, include all of them in the top-level data.json at agency.gov/data.json.
+Publish your agency’s enterprise data inventory, with the aforementioned information removed, to a file located at \[agency\].gov/data.json and described using (at minimum) the [common core metadata](http://project-open-data.github.io/schema/). This file itself must be listed as a dataset within itself (see [an example of format](http://project-open-data.github.io/examples/catalog-sample-extended.json) ); if you have multiple data.json files across your agency, include all of them in the top-level data.json at agency.gov/data.json.
 
 While you could manually create this file in a text editor, it is recommended that you use one of the tools provided to generate this file automatically from your existing DMS or enterprise inventory file.
 
@@ -63,7 +63,7 @@ While you could manually create this file in a text editor, it is recommended th
 
 
 ## 3) Engage with customers to help facilitate and prioritize data release
-*[Due by 11/9/13]*
+*\[Due by 11/9/13\]*
 
 ### Minimum Required for Compliance
 
@@ -82,7 +82,7 @@ Create a process to solicit feedback from customers about existing and potential
 
 
 ## 4) Clarify Roles and Responsibilities
-*[Due by 11/9/13]*
+*\[Due by 11/9/13\]*
 
 ### A) Minimum Required for Compliance
 
@@ -119,7 +119,7 @@ Additionally, you should include information on:
 
 * [44 USC 3506 (b)(2)](http://www.gpo.gov/fdsys/granule/USCODE-2011-title44/USCODE-2011-title44-chap35-subchapI-sec3506/content-detail.html)
 * [OMB Circular A-11](http://www.whitehouse.gov/omb/circulars_a11_current_year_a11_toc)
-* [OMB FY 13 PortfolioStat Guidance] (http://www.whitehouse.gov/blog/2013/03/27/portfoliostat-20-driving-better-management-and-efficiency-federal-it)
+* [OMB FY 13 PortfolioStat Guidance](http://www.whitehouse.gov/blog/2013/03/27/portfoliostat-20-driving-better-management-and-efficiency-federal-it)
 
 <center><h2><u>Ongoing</u></h2></center>  
 

index.md

@@ -111,7 +111,7 @@ Case studies of novel or best practices from agencies who are leading in open da
 
 6-7 [National Renewable Energy Laboratory API program](http://developer.nrel.gov/api-case-study/) - An agency perspective on developing APIs for general use and in particular building the case for the internal re-use of the resources.
 
-6-8 [USAID Crowdsourcing to Open Data] (http://transition.usaid.gov/our_work/economic_growth_and_trade/development_credit/pdfs/2012/USAIDCrowdsourcingCaseStudy.pdf) - A case study that shows how USAID invited the "crowd" to clean and geocode a USAID dataset in order to open and map the data.
+6-8 [USAID Crowdsourcing to Open Data](http://transition.usaid.gov/our_work/economic_growth_and_trade/development_credit/pdfs/2012/USAIDCrowdsourcingCaseStudy.pdf) - A case study that shows how USAID invited the "crowd" to clean and geocode a USAID dataset in order to open and map the data.
 
 
 **For Developers: [View all appendices](http://github.com/project-open-data/) (and source)**

policy-memo.md

@@ -127,11 +127,11 @@ Agencies must update their inventory of agency information resources (as require
 
 ##### b. Create and maintain a public data listing
 
-Any datasets in the agency's enterprise data inventory that can be made publicly available must be listed at www.[agency].gov/data in a human- and machine-readable format that enables automatic aggregation by Data.gov and other services (known as "harvestable files"), to the extent practicable. This should include datasets that can be made publicly available but have not yet been released. This public data listing should also include, to the extent permitted by law and existing terms and conditions, datasets that were produced through agency-funded grants, contracts, and cooperative agreements (excluding any data submitted primarily for the purpose of contract monitoring and administration), and, where feasible, be accompanied by standard citation information, preferably in the form of a persistent identifier. The public data listing will be built out over time, with the ultimate goal of including all agency datasets that can be made publicly available. See Project Open Data for best practices, tools, and schema to implement the public data listing and harvestable files. 
+Any datasets in the agency's enterprise data inventory that can be made publicly available must be listed at www.\[agency\].gov/data in a human- and machine-readable format that enables automatic aggregation by Data.gov and other services (known as "harvestable files"), to the extent practicable. This should include datasets that can be made publicly available but have not yet been released. This public data listing should also include, to the extent permitted by law and existing terms and conditions, datasets that were produced through agency-funded grants, contracts, and cooperative agreements (excluding any data submitted primarily for the purpose of contract monitoring and administration), and, where feasible, be accompanied by standard citation information, preferably in the form of a persistent identifier. The public data listing will be built out over time, with the ultimate goal of including all agency datasets that can be made publicly available. See Project Open Data for best practices, tools, and schema to implement the public data listing and harvestable files. 
 
 ##### c. Create a process to engage with customers to help facilitate and prioritize data release
 
-Agencies must create a process to engage with customers, through their www.[agency].gov/data pages and other necessary means, to solicit help in prioritizing the release of datasets and determining the most usable and appropriate formats for release.[^26] Agencies should make data available in multiple formats according to their customer needs. For example, high-volume datasets of interest to developers should be released using bulk downloads as well as Application Programming Interfaces (APIs). In addition, customer engagement efforts should help agencies prioritize efforts to improve the discoverability and usability of datasets that have already been released to the public but are not yet fully "open" (e.g., they are only available in closed, inaccessible formats). See Project Open Data for best practices and tools that can be used to implement customer engagement efforts.
+Agencies must create a process to engage with customers, through their www.\[agency\].gov/data pages and other necessary means, to solicit help in prioritizing the release of datasets and determining the most usable and appropriate formats for release.[^26] Agencies should make data available in multiple formats according to their customer needs. For example, high-volume datasets of interest to developers should be released using bulk downloads as well as Application Programming Interfaces (APIs). In addition, customer engagement efforts should help agencies prioritize efforts to improve the discoverability and usability of datasets that have already been released to the public but are not yet fully "open" (e.g., they are only available in closed, inaccessible formats). See Project Open Data for best practices and tools that can be used to implement customer engagement efforts.
 
 ##### d. Clarify roles and responsibilities for promoting efficient and effective data release practices
 

transportation-case-study.md

@@ -24,7 +24,7 @@ In response to the [Open Government Directive](http://www.whitehouse.gov/sites/d
 * **Policy**: Provide guidelines for identifying datasets and prioritizing them for release. Institute standing policies for approving, publishing, and managing releases.
 * **Inventory**: Build list of source information systems using budget exhibits. Compare these against data already released on websites and against information collections. Utilize these lists to develop a complete inventory of datasets, prioritize it, and sequence data for release.
 
-DOT detailed the results of its strategic action plan on its open government [Web page](http://www.dot.gov/open). The Department sustained efforts in building its data inventory, responding to the President’s [memorandum](http://www.gpo.gov/fdsys/pkg/DCPD-201100032/pdf/DCPD-201100032.pdf) on regulatory compliance with a comprehensive [plan](http://www.dot.gov/sites/dot.dev/files/docs/DOT Draft Enforcement and Compliance Data Report - 05-18-2011 - OCR.pdf) that was [recognized](http://sunlightfoundation.com/blog/2011/08/31/two-suggestions-for-the-us-national-action-plan/) as a model for other agencies to follow. DOT’s [flagship initiative](http://www.dot.gov/open/plan-chapter3#Section 3.1) in its [second Open Government Plan](http://www.dot.gov/sites/dot.dev/files/docs/open-gov-v2_0.pdf), released in April 2012, is [Safety.Data.gov](http://safety.data.gov/), is intended to create momentum behind the productive use of safety-related datasets, enabling the public to make better safety-related decisions using both current statistical descriptions and explanations of the environment that will affect our future. Safety.Data.gov will tap into the innovation of application developers, the immediacy of the internet, and information that the Federal Government collects to enable informed decisions that will enhance public safety and improve public health in the United States.
+DOT detailed the results of its strategic action plan on its open government [Web page](http://www.dot.gov/open). The Department sustained efforts in building its data inventory, responding to the President’s [memorandum](http://www.gpo.gov/fdsys/pkg/DCPD-201100032/pdf/DCPD-201100032.pdf) on regulatory compliance with a comprehensive [plan](http://www.dot.gov/sites/dot.dev/files/docs/DOT%20Draft%20Enforcement%20and%20Compliance%20Data%20Report%20-%2005-18-2011%20-%20OCR.pdf) that was [recognized](http://sunlightfoundation.com/blog/2011/08/31/two-suggestions-for-the-us-national-action-plan/) as a model for other agencies to follow. DOT’s [flagship initiative](http://www.dot.gov/open/plan-chapter3#sec3-1) in its [second Open Government Plan](http://www.dot.gov/sites/dot.dev/files/docs/open-gov-v2_0.pdf), released in April 2012, is [Safety.Data.gov](http://safety.data.gov/), is intended to create momentum behind the productive use of safety-related datasets, enabling the public to make better safety-related decisions using both current statistical descriptions and explanations of the environment that will affect our future. Safety.Data.gov will tap into the innovation of application developers, the immediacy of the internet, and information that the Federal Government collects to enable informed decisions that will enhance public safety and improve public health in the United States.
 
 ## Challenge
 
@@ -52,7 +52,7 @@ Content releasability is determined with value, quality, security, privacy, and
 
 ## Results
 
-The DOT has released [765 datasets or tools](https://explore.data.gov/browse?Dataset-Summary_Agency=Department+of+Transportation) to Data.gov. The processes and policies that have been established under DOT’s approach to Open Government helped DOT build a comprehensive [plan](http://www.dot.gov/sites/dot.dev/files/docs/DOT Draft Enforcement and Compliance Data Report - 05-18-2011 - OCR.pdf) responding to the President’s [memorandum](http://www.gpo.gov/fdsys/pkg/DCPD-201100032/pdf/DCPD-201100032.pdf) on regulatory compliance that was [recognized](http://sunlightfoundation.com/blog/2011/08/31/two-suggestions-for-the-us-national-action-plan/) as a model for other agencies to follow. In May of 2012, DOT, in partnership with the Department of Justice, Department of Labor, and the Consumer Product Safety Commission, launched [Safety.Data.gov](http://safety.data.gov/) with 713 datasets, four (4) mobile apps, 14 resources and public domain software tools, and three (3) challenges or competitions. In September 2012, we held the first safety datapalooza, and the community now has 869 datasets, 10 mobile apps, and six (6) challenges or competitions encouraging public use of safety data from around the government.
+The DOT has released [765 datasets or tools](https://explore.data.gov/browse?Dataset-Summary_Agency=Department+of+Transportation) to Data.gov. The processes and policies that have been established under DOT’s approach to Open Government helped DOT build a comprehensive [plan](http://www.dot.gov/sites/dot.dev/files/docs/DOT%20Draft%20Enforcement%20and%20Compliance%20Data%20Report%20-%2005-18-2011%20-%20OCR.pdf) responding to the President’s [memorandum](http://www.gpo.gov/fdsys/pkg/DCPD-201100032/pdf/DCPD-201100032.pdf) on regulatory compliance that was [recognized](http://sunlightfoundation.com/blog/2011/08/31/two-suggestions-for-the-us-national-action-plan/) as a model for other agencies to follow. In May of 2012, DOT, in partnership with the Department of Justice, Department of Labor, and the Consumer Product Safety Commission, launched [Safety.Data.gov](http://safety.data.gov/) with 713 datasets, four (4) mobile apps, 14 resources and public domain software tools, and three (3) challenges or competitions. In September 2012, we held the first safety datapalooza, and the community now has 869 datasets, 10 mobile apps, and six (6) challenges or competitions encouraging public use of safety data from around the government.
 
 DOT has already recognized benefits as a result of regulatory transparency efforts. For example, for the first time, FMCSA has begun releasing the information behind its Safety Measurement System (SMS) to the public in bulk, downloadable formats. Business and private citizens are mining this data for potential opportunities. For instance, a windshield repair company looking to grow its business is mining FMCSA information about safety violations to identify new customers. DOT and the public realize a benefit because the commercial vehicle operator customer is using a safer vehicle and operating in compliance with Federal Motor Carrier Safety Regulations. In addition, DOT has pursued innovation in its data release practices:
 * FMCSA released an [API](https://mobile.fmcsa.dot.gov/developer/home.page) and [mobile application](https://www.fmcsa.dot.gov/safety-security/saferbus/saferbus.aspx) to help people easily access a bus