Skip to content

Commit fd3685b

Browse files
authored
Merge pull request #3000 from canyon289/contributing_typo
Fix minor typos in CONTRIBUTING.md
2 parents 7f1d433 + 8d17b01 commit fd3685b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

CONTRIBUTING.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ There are 4 main ways of contributing to the PyMC3 project (in descending order
1111

1212
# Opening issues
1313

14-
We appreciate being notified of problems with the existing PyMC code. We prefer that issues be filed the on [Gitub Issue Tracker](https://github.com/pymc-devs/pymc3/issues), rather than on social media or by direct email to the developers.
14+
We appreciate being notified of problems with the existing PyMC code. We prefer that issues be filed the on [Github Issue Tracker](https://github.com/pymc-devs/pymc3/issues), rather than on social media or by direct email to the developers.
1515

1616
Please verify that your issue is not being currently addressed by other issues or pull requests by using the GitHub search tool to look for key words in the project issue tracker.
1717

@@ -21,7 +21,7 @@ While issue reporting is valuable, we strongly encourage users who are inclined
2121

2222
Contributors are also encouraged to contribute new code to enhance PyMC3's functionality, also via pull requests. Please consult the [PyMC3 documentation](https://pymc-devs.github.io/pymc3/) to ensure that any new contribution does not strongly overlap with existing functionality.
2323

24-
The preferred workflow for contributing to PyMC3 is to fork the [GitHUb repository](https://github.com/pymc-devs/pymc3/), clone it to your local machine, and develop on a feature branch.
24+
The preferred workflow for contributing to PyMC3 is to fork the [GitHub repository](https://github.com/pymc-devs/pymc3/), clone it to your local machine, and develop on a feature branch.
2525

2626
## Steps:
2727

@@ -145,8 +145,8 @@ $ . ./scripts/test.sh # takes a while!
145145
This should be quite close to how the tests run on TravisCI.
146146

147147
If the container was started without opening the browser, you
148-
need the a token to work with the notebook. This token can be
149-
access with
148+
need the notebook instances token to work with the notebook. This token can be
149+
accessed with
150150

151151
```
152152
docker exec -it pymc3 jupyter notebook list

0 commit comments

Comments
 (0)