question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Proposing a PR to fix a few small typos

See original GitHub issue

Issue 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 see aggregated.
  • Examine sc2reader/objects.py and observe acount, however expect to see account.
  • Examine docs/source/tutorials/prettyprinter.rst and observe versitile, however expect to see versatile.
  • Examine docs/source/articles/whatsinareplay.rst and observe unncessary, however expect to see unnecessary.
  • Examine sc2reader/events/game.py and observe targetting, however expect to see targeting.
  • Examine examples/sc2autosave.py and observe substition, however expect to see substitution.
  • Examine sc2reader/resources.py and observe requirments, however expect to see requirements.

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:closed
  • Created 2 years ago
  • Comments:8 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
cclausscommented, Jul 18, 2021

“Small moves.” – Contact

Thanks for doing this.

1reaction
cclausscommented, Jul 6, 2021

@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.

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found