|
1 | 1 | ###Guidelines
|
2 | 2 |
|
3 |
| -All contributions, bug reports, bug fixes, documentation improvments, |
| 3 | +All contributions, bug reports, bug fixes, documentation improvements, |
4 | 4 | enhancements and ideas are welcome.
|
5 | 5 |
|
6 | 6 | The Github "issues" tab contains some issues labels "Good as first PR", these are
|
@@ -34,7 +34,7 @@ your contribution or address the issue you're having.
|
34 | 34 | See the "Getting Travis-CI going" below.
|
35 | 35 | - We suggest you enable Travis-CI on your fork, to make it easier for the team
|
36 | 36 | to see that the PR does indeed pass all the tests.
|
37 |
| - - Back-compatiblitiy **really** matters. Pandas already has a large user-base and |
| 37 | + - Back-compatibility **really** matters. Pandas already has a large user-base and |
38 | 38 | a lot of existing user code. Don't break old code if you can avoid it
|
39 | 39 | Explain the need if there is one in the PR.
|
40 | 40 | Changes to method signatures should be made in a way which doesn't break existing
|
@@ -113,7 +113,7 @@ page for any PR you submit. For example:
|
113 | 113 |
|
114 | 114 | See the Green "Good to merge!" banner? that's it.
|
115 | 115 |
|
116 |
| -This is especially important for new contributors, as memebers of the pandas dev team |
| 116 | +This is especially important for new contributors, as members of the pandas dev team |
117 | 117 | like to know the test suite passes before considering it for merging.
|
118 | 118 | Even regular contributors who test religiously on their local box (using tox
|
119 | 119 | for example) often rely on a PR+travis=green to make double sure everything
|
|
0 commit comments