aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorTony Miller <mcfiredrill@gmail.com>2015-07-10 23:58:39 +0900
committerTony Miller <mcfiredrill@gmail.com>2015-07-10 23:58:39 +0900
commit5c3db80fee1c69e41769585f131c952fceada8a5 (patch)
treedd8dec99844be3318b55016bfa9907176ab62938 /guides
parentf0e922fe4ce5fb836ebe327b3f946aab6f00b31b (diff)
downloadrails-5c3db80fee1c69e41769585f131c952fceada8a5.tar.gz
rails-5c3db80fee1c69e41769585f131c952fceada8a5.tar.bz2
rails-5c3db80fee1c69e41769585f131c952fceada8a5.zip
saying that "behaviour" "behaves" is kind of awkward, how about "works"
Diffstat (limited to 'guides')
-rw-r--r--guides/source/contributing_to_ruby_on_rails.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/contributing_to_ruby_on_rails.md b/guides/source/contributing_to_ruby_on_rails.md
index 118094ccf1..c0d37a83d2 100644
--- a/guides/source/contributing_to_ruby_on_rails.md
+++ b/guides/source/contributing_to_ruby_on_rails.md
@@ -61,7 +61,7 @@ can expect it to be marked "invalid" as soon as it's reviewed.
Sometimes, the line between 'bug' and 'feature' is a hard one to draw.
Generally, a feature is anything that adds new behavior, while a bug is
-anything that causes already existing behavior to behave incorrectly. Sometimes,
+anything that causes existing behavior to work incorrectly. Sometimes,
the core team will have to make a judgement call. That said, the distinction
generally just affects which release your patch will get in to; we love feature
submissions! They just won't get backported to maintenance branches.