@@ -18,7 +18,7 @@ New to here
1818Any issue with good first issue tag on it is a great place to start! Feel free to ask any questions here.
1919
2020Don't know how to start
21- ~~~~~~~~~~~
21+ ~~~~~~~~~~~~~~~~~~~~~~~
2222
2323Review codebases and PRs can give you quite a knowledge to know what's going on here!
2424
@@ -39,8 +39,8 @@ Fix Bugs
3939Look through the GitHub issues for bugs. Anything tagged with "bug"
4040is open to whoever wants to implement it.
4141
42- Implement Features & imporvments
43- ~~~~~~~~~~~~~~~~~~
42+ Implement Features & improvments
43+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
4444
4545Look through the GitHub issues for features. Anything tagged with "feature" or "improvments"
4646is open to whoever wants to implement it.
@@ -70,7 +70,7 @@ Get Started!
7070Ready to contribute? Here's how to set up `scrapy-redis ` for local development.
7171
7272Setup environment
73- ~~~~~~~~~~~~~~~
73+ ~~~~~~~~~~~~~~~~~
7474
75751. Fork the `scrapy-redis ` repo on GitHub.
76762. Clone your fork locally::
@@ -93,7 +93,7 @@ Setup environment
9393 Now you can make your changes locally.
9494
9595Setup testing environment
96- ~~~~~~~~~~~~~~~
96+ ~~~~~~~~~~~~~~~~~~~~~~~~~
9797
98981. When you're done making changes, check that your changes pass flake8 and the tests, including testing other Python versions with tox::
9999
@@ -128,9 +128,7 @@ Before you submit a pull request, check that it meets these guidelines:
1281282. If the pull request adds functionality, the docs should be updated. Put
129129 your new functionality into a function with a docstring, and add the
130130 feature to the list in README.rst.
131- 3. The pull request should work for Python 2.6, 2.7, 3.3, 3.4 and 3.5, and for PyPy. Check
132- https://travis-ci.org/rolando/scrapy-redis/pull_requests
133- and make sure that the tests pass for all supported Python versions.
131+ 3. Make sure that the tests pass for all supported Python versions.
134132
135133Tips
136134----
0 commit comments