Proposing a PR to fix a few small typos
See original GitHub issueIssue Type
[x] Bug (Typo)
Steps to Replicate and Expected Behaviour
- Examine docs/source/articles/creatingagameengineplugin.rst, sc2reader/engine/engine.py and observe
aggrated
, however expect to seeaggregated
. - Examine sc2reader/objects.py and observe
acount
, however expect to seeaccount
. - Examine docs/source/tutorials/prettyprinter.rst and observe
versitile
, however expect to seeversatile
. - Examine docs/source/articles/whatsinareplay.rst and observe
unncessary
, however expect to seeunnecessary
. - Examine sc2reader/events/game.py and observe
targetting
, however expect to seetargeting
. - Examine examples/sc2autosave.py and observe
substition
, however expect to seesubstitution
. - Examine sc2reader/resources.py and observe
requirments
, however expect to seerequirements
.
Notes
Semi-automated issue generated by https://github.com/timgates42/meticulous/blob/master/docs/NOTE.md
To avoid wasting CI processing resources a branch with the fix has been prepared but a pull request has not yet been created. A pull request fixing the issue can be prepared from the link below, feel free to create it or request @timgates42 create the PR. Alternatively if the fix is undesired please close the issue with a small comment about the reasoning.
https://github.com/timgates42/sc2reader/pull/new/bugfix_typos
Thanks.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Proposing a PR to fix a few small typos · Issue #395 - GitHub
Issue Type. [x] Bug (Typo). Steps to Replicate and Expected Behaviour. Examine pyhive/presto.py and observe queryes , however expect to see ...
Read more >Developers - Proposing a PR to fix a few small typos - - Bountysource
Issue Type. [x] Bug (Typo). Steps to Replicate and Expected Behaviour. Examine README.md and observe similiarly , however expect to see similarly ....
Read more >github - Should I submit a pull request to correct minor typos in ...
Of course in that case it's not worthwhile. Fixing typos in a README is trivial, but the cost of accepting a PR is...
Read more >9 Sales Proposal Mistakes You Have to Avoid - Prospero Blog
Mistake #4: Not Proofreading Your Proposal for Grammar, Jargon, and Typos ... In a sales proposal, you're communicating how you can help your ......
Read more >Questions and Answers about CRISPR | Broad Institute
A: “CRISPR” (pronounced “crisper”) stands for Clustered Regularly Interspaced Short Palindromic Repeats, which are the hallmark of a bacterial defense ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
“Small moves.” – Contact
Thanks for doing this.
@timgates42 You might consider contributing some of these off-by-just-one-letter fixes to codespell. Especially the account one might be done in other repos.