Fix a few last links

James McKinney · James McKinney · commit 1dda1dd81673 · 2013-05-16T02:06:17.000-04:00
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -40,8 +40,8 @@ Project Open Data runs on GitHub pages and automatically regenerates as a static
 
 ## Licensing
 
-By contributing to this project, you grant a world-wide, royalty-free, perpetual, irrevocable, non-exclusive, transferable license to all users under [the same terms under which the project is licensed](readme.md#licensing).
+By contributing to this project, you grant a world-wide, royalty-free, perpetual, irrevocable, non-exclusive, transferable license to all users under [the same terms under which the project is licensed](README.md#licensing).
 
 ## Privacy
 
-All comments, messages, pull requests, and other submissions received through official White House pages including this GitHub page may be subject to archiving requirements. See the [readme](readme.md#privacy) for more information. 
+All comments, messages, pull requests, and other submissions received through official White House pages including this GitHub page may be subject to archiving requirements. See the [readme](README.md#privacy) for more information. 
diff --git a/index.md b/index.md
@@ -36,13 +36,13 @@ This section is a list of definitions and principles used to guide the project.
 
 Implementation guidance for open data practices.  
 
-3-1 [U.S. Government Policy on Open Data](policy-memo/) - Full text of the memorandum.  
+3-1 [U.S. Government Policy on Open Data](/policy-memo/) - Full text of the memorandum.  
 
-3-2 [Implementation Guide](implementation-guide/) - Detailed descriptions and guidance for each step of implementing the policy. 
+3-2 [Implementation Guide](/implementation-guide/) - Detailed descriptions and guidance for each step of implementing the policy. 
 
-3-3 [Public Data Listing](catalog) - The specific guidance for publishing the Open Data Catalog at the agency.gov/data page.  
+3-3 [Public Data Listing](/catalog/) - The specific guidance for publishing the Open Data Catalog at the agency.gov/data page.  
 
-3-4 [Frequently Asked Questions](faq) - A growing list of common questions and answers to facilitate adoption of open data projects.  
+3-4 [Frequently Asked Questions](/faq/) - A growing list of common questions and answers to facilitate adoption of open data projects.  
 
 ----------------
 
diff --git a/policy-memo.md b/policy-memo.md
@@ -36,7 +36,7 @@ To help build on these efforts, the President issued a Memorandum on May 23, 201
 
 This Memorandum is designed to be consistent with existing requirements in the Paperwork Reduction Act,[^7] the E-Government Act of 2002,[^8] the Privacy Act of 1974,[^9] the Federal Information Security Management Act of 2002 (FISMA),[^10] the Confidential Information Protection and Statistical Efficiency Act of 2002 (CIPSEA),[^11] the Freedom of Information Act,[^12] the Information Quality Act,[^13] the Federal Records Act,[^14] and existing OMB and Office of Science and Technology Policy (OSTP) guidance. 
 
-If agencies have any questions regarding this Memorandum, please direct them to OMB at [datause@omb.eop.gov](datause@omb.eop.gov).
+If agencies have any questions regarding this Memorandum, please direct them to OMB at [datause@omb.eop.gov](mailto:datause@omb.eop.gov).
 
 ---
 
diff --git a/schema.md b/schema.md
@@ -225,7 +225,7 @@ Field       | title
 **Cardinality** | (0,1)
 **Required** | Yes, if the dataset is spatial
 **Accepted Values** | See Usage Notes
-**Usage Notes** | This field should contain one of the following types of content: (1) a bounding coordinate box for the dataset represented in latitude / longitude pairs where the coordinates are specified in decimal degrees and in the order of: minimum longitude, minimum latitude, maximum longitude, maximum latitude; (2) a latitude / longitude pair (in decimal degrees) representing a point where the dataset is relevant; (3) a geographic feature expressed in [Geography Markup Language using the Simple Features Profile](http://www.ogcnetwork.net/gml-sf); or (4) a geographic feature from the [GeoNames database](www.geonames.org).
+**Usage Notes** | This field should contain one of the following types of content: (1) a bounding coordinate box for the dataset represented in latitude / longitude pairs where the coordinates are specified in decimal degrees and in the order of: minimum longitude, minimum latitude, maximum longitude, maximum latitude; (2) a latitude / longitude pair (in decimal degrees) representing a point where the dataset is relevant; (3) a geographic feature expressed in [Geography Markup Language using the Simple Features Profile](http://www.ogcnetwork.net/gml-sf); or (4) a geographic feature from the [GeoNames database](http://www.geonames.org).
 **Example** |  `{"spatial":"Lincoln, Nebraska"}`
 
 {.table .table-striped}

-Original file line number
+Diff line change
 This Memorandum is designed to be consistent with existing requirements in the Paperwork Reduction Act,[^7] the E-Government Act of 2002,[^8] the Privacy Act of 1974,[^9] the Federal Information Security Management Act of 2002 (FISMA),[^10] the Confidential Information Protection and Statistical Efficiency Act of 2002 (CIPSEA),[^11] the Freedom of Information Act,[^12] the Information Quality Act,[^13] the Federal Records Act,[^14] and existing OMB and Office of Science and Technology Policy (OSTP) guidance.
 -If agencies have any questions regarding this Memorandum, please direct them to OMB at [[email protected]]([email protected]).
 +If agencies have any questions regarding this Memorandum, please direct them to OMB at [[email protected]](mailto:[email protected]).
 ---