Skip to content

Commit b7a7a7c

Browse files
committed
Merge small edits by hand
2 parents ff95f97 + 09ed920 commit b7a7a7c

File tree

2 files changed

+41
-5
lines changed

2 files changed

+41
-5
lines changed

.gitignore

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
# OS generated files #
2+
######################
3+
.DS_Store
4+
.DS_Store?
5+
.Spotlight-V100
6+
.Trashes
7+
ehthumbs.db
8+
Thumbs.db
9+
10+
# Vim swap files #
11+
##################
12+
*.swp
13+
14+
# Python #
15+
#################
16+
*.pyc
17+
*.egg-info/
18+
__pycache__/
19+
*.py[cod]
20+
21+
# Django #
22+
#################
23+
*.egg-info
24+
.installed.cfg
25+
26+
# Unit test / coverage reports
27+
#################
28+
htmlcov/
29+
.tox/
30+
.coverage
31+
.cache
32+
nosetests.xml
33+
coverage.xml
34+
35+
36+

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Other things to include:
2020

2121
- **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)
2222
- **Links to production or demo instances**
23-
- Describe what sets this apart from related-projects. Again, a link to another doc is OK if this can't be expressed in a sentence or two
23+
- 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
2424

2525

2626
**Screenshot**: If the software has visual components, place a screenshot after the description; e.g.—
@@ -41,24 +41,24 @@ This section should detail why people should get involved and describe key areas
4141
currently focusing on; e.g., trying to get feedback on features, fixing certain bugs, building
4242
important pieces, etc.
4343

44-
General instructions on _how_ to contribute should be stated with a link(CONTRIBUTING.md)
44+
General instructions on _how_ to contribute should be stated with a link to [CONTRIBUTING.md](CONTRIBUTING.md)
4545

4646

4747
____
4848

4949
## Open Source Licensing Info
50-
1. [License](LICENSE)
50+
1. [LICENSE](LICENSE)
5151
2. [TERMS](TERMS.md)
5252
3. [CFPB Source Code Policy](http://github.com/cfpb/source-code-policy/)
5353

5454

5555
----
5656

57-
### Credits and References
57+
## Credits and References
5858

5959
1. Projects that inspired you
6060
2. Related projects
61-
3. Book, papers, or other writings that
61+
3. Books, papers, talks, or other sources that have meaniginful impact or influence on this project
6262

6363

6464

0 commit comments

Comments
 (0)