diff options
author | Tim Gates <tim.gates@iress.com> | 2019-09-03 20:38:38 +1000 |
---|---|---|
committer | Paul McGuire <ptmcg@users.noreply.github.com> | 2019-09-03 05:38:38 -0500 |
commit | 87016995f05a0b4927eef22f767a349d85e6afd2 (patch) | |
tree | 0c459a362567e7ebddb90fb8bbcb88b659c41852 | |
parent | cbb1d29c639b419fb8e99eddc00d6b5438b30ae9 (diff) | |
download | pyparsing-git-87016995f05a0b4927eef22f767a349d85e6afd2.tar.gz |
Fix simple typo: pyaprsing -> pyparsing (#121)
Thanks!
-rw-r--r-- | CONTRIBUTING.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 830fbcb..0c405a0 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -29,7 +29,7 @@ If you have a question on using pyparsing, there are a number of resources avail and Python features. - [submit an issue](https://github.com/pyparsing/pyparsing/issues) - If you have a problem with pyparsing that looks - like an actual bug, or have an idea for a feature to add to pyaprsing please submit an issue on GitHub. Some + like an actual bug, or have an idea for a feature to add to pyparsing please submit an issue on GitHub. Some pyparsing behavior may be counter-intuitive, so try to review some of the other resources first, or some of the other open and closed issues. Or post your question on SO or reddit. But don't wait until you are desperate and frustrated - just ask! :) |