diff options
| author | Luis Valdes <luischivaldes@gmail.com> | 2017-04-16 06:22:51 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-04-16 06:22:51 -0400 |
| commit | 7daa81f0cd65b4038989b53a84f47d8e51baccdb (patch) | |
| tree | 57bfbbd0645e2410ba6a0ba4fd0ed788c19dede5 | |
| parent | 678587271069a222c9fd9fbadb7eccfedab6f067 (diff) | |
Fix typo
Change to improvement
| -rw-r--r-- | contributors/devel/development.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/devel/development.md b/contributors/devel/development.md index 779b6bf5..f0e645fc 100644 --- a/contributors/devel/development.md +++ b/contributors/devel/development.md @@ -64,7 +64,7 @@ Examples of how NOT to suggest a performance bug (these can really lead to a lon The above statements have basically no value to a reviewer, because neither is a strong, testable, assertive statement. This will land your PR in a no-man's-land zone (at best), or waste tons of time for a busy reviewer (at worst). -Of course any improvment is welcome, but performance improvements are the hardest to review. They often make code more +Of course any improvement is welcome, but performance improvements are the hardest to review. They often make code more complex, and to-often are not easily evaluated at review time due to lack of sufficient data submitted by the author of a performance improvement patch. |