Merge pull request #3 from Scotchester/master

Some copyediting and suggestions

Author: virtix

CONTRIBUTING.md

@@ -1,8 +1,8 @@
 # Guidance on how to contribute
 
-> All contributions to this project will be released under the CC0
-> dedication. By submitting a pull request, or filing a bug, issue, or 
-> feature-request you are agreeing to comply with this waiver of copyright interest.
+> All contributions to this project will be released under the CC0 public domain
+> dedication. By submitting a pull request or filing a bug, issue, or 
+> feature request, you are agreeing to comply with this waiver of copyright interest.
 > Details can be found in our [TERMS](TERMS.md) and [LICENCE](LICENSE).
 
 
@@ -25,21 +25,8 @@ guidance below.
 ## Changing the code-base
 
 Generally speaking, you should fork this repository, make changes in your
-own fork, and then submit a pull-request.  All new code should have associated unit
+own fork, and then submit a pull-request. All new code should have associated unit
 tests that validate implemented features and the presence or lack of defects. 
 Additionally, the code should follow any stylistic and architectural guidelines 
 prescribed by the project. In the absence of such guidelines, mimic the styles
 and patterns in the existing code-base.
-
-----
-
-## Public domain
-
-The project is in the public domain within the United States, and
-copyright and related rights in the work worldwide are waived through
-the [CC0 1.0 Universal public domain dedication][CC0].
-
-
-[CC0]: http://creativecommons.org/publicdomain/zero/1.0/
-
-

README.md

@@ -1,64 +1,63 @@
 #### CFPB Open Source Project Template Instructions
 
-1. Create a new project
-2. Copy these files into the new project
-3. Update the README, replacing the contents below as prescribed
-4. Add any libraries, assets, or hard dependencies to the _Exceptions_ section in the [TERMS](TERMS.md)
-5. Delete these instructions and everything up to the _Project Title_ from the README
-6. Write some great software and tell people about it
+1. Create a new project.
+2. Copy these files into the new project.
+3. Update the README, replacing the contents below as prescribed.
+4. Add any libraries, assets, or hard dependencies whose source code will be included
+   in the project's repository to the _Exceptions_ section in the [TERMS](TERMS.md).
+  - If no exceptions are needed, remove that section from TERMS.
+5. Delete these instructions and everything up to the _Project Title_ from the README.
+6. Write some great software and tell people about it.
 
 > Keep the README fresh! It's the first thing people see and will make the initial impression.
 
 ----
 
 # Project Title
 
-**Description**:  Put a meaningful, short, plain-language description of what 
-this project is trying to accomplish and why it matters. 
+**Description**:  Put a meaningful, short, plain-language description of what
+this project is trying to accomplish and why it matters.
 
 Other things to include:
 
-  - **Status**:  Alpha, Beta, 1.1, etc. It's OK to write a sentence, too.  The goal is to let interested people know where this project is at. This is also a good place to link to the [CHANGELOG](CHANGELOG.md)
+  - **Status**:  Alpha, Beta, 1.1, etc. It's OK to write a sentence, too. The goal is to let interested people know where this project is at. This is also a good place to link to the [CHANGELOG](CHANGELOG.md).
   - **Links to production or demo instances**
-  - Describe what sets this apart from related-projects. Linking to another doc or page is OK if this can't be expressed in a sentence or two
+  - Describe what sets this apart from related-projects. Linking to another doc or page is OK if this can't be expressed in a sentence or two.
 
 
-**Screenshot**: If the software has visual components, place a screenshot after the description; e.g.—
+**Screenshot**: If the software has visual components, place a screenshot after the description; e.g.,
 
 ![](https://raw.githubusercontent.com/cfpb/open-source-project-template/master/screenshot.png)
 
 
 ## How to get this running or how to use it
 
 Detailed instructions on how to install, configure, and get the project running.
-This should be frequently tested to ensure reliability. Alternatively, a link to 
+This should be frequently tested to ensure reliability. Alternatively, a link to
 another page is fine, but it's important that this works.
 
 
 ## Getting involved
 
 This section should detail why people should get involved and describe key areas you are
 currently focusing on; e.g., trying to get feedback on features, fixing certain bugs, building
-important pieces, etc.  
+important pieces, etc.
 
-General instructions on _how_ to contribute should be stated with a link to [CONTRIBUTING.md](CONTRIBUTING.md) 
+General instructions on _how_ to contribute should be stated with a link to [CONTRIBUTING](CONTRIBUTING.md).
 
 
-____
+----
 
-## Open Source Licensing Info
-1. [LICENSE](LICENSE)
-2. [TERMS](TERMS.md)
-3. [CFPB Source Code Policy](http://github.com/cfpb/source-code-policy/)
+## Open source licensing info
+1. [TERMS](TERMS.md)
+2. [LICENSE](LICENSE)
+3. [CFPB Source Code Policy](https://github.com/cfpb/source-code-policy/)
 
 
 ----
 
-## Credits and References
+## Credits and references
 
 1. Projects that inspired you
 2. Related projects
 3. Books, papers, talks, or other sources that have meaniginful impact or influence on this project 
-
-
-

TERMS.md

@@ -1,5 +1,5 @@
-As a work of the United States Government, this package (excluding the
-exceptions below) is in the public domain within the United States.
+As a work of the United States Government, this package (excluding any
+exceptions listed below) is in the public domain within the United States.
 Additionally, we waive copyright and related rights in the work worldwide
 through the CC0 1.0 Universal public domain dedication.
 
@@ -44,7 +44,7 @@ author or the affirmer.
 
 ## Exceptions
 
-_:Source code or other assets that are excluded from the TERMS should be listed
+_Source code or other assets that are excluded from the TERMS should be listed
 here. These may include dependencies that may be licensed differently or are
 not in the public domain._