Skip to content

Fix a typo "kids" –> "kinds" #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 12, 2015
Merged

Fix a typo "kids" –> "kinds" #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/rationale.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ There are perfectly sane use cases for monkey-patching (aka *weaving*):

Then in those situations:

* You would need to handle yourself all different kids of patching (patching
* You would need to handle yourself all different kinds of patching (patching
a module is different than patching a class, a function or a method for that matter).
``aspectlib`` will handle all this gross patching mumbo-jumbo for you, consistently, over many Python versions.
* Writing the actual wrappers is repetitive, boring and error-prone. You can't reuse wrappers
Expand Down