From 5c3db80fee1c69e41769585f131c952fceada8a5 Mon Sep 17 00:00:00 2001 From: Tony Miller Date: Fri, 10 Jul 2015 23:58:39 +0900 Subject: saying that "behaviour" "behaves" is kind of awkward, how about "works" --- guides/source/contributing_to_ruby_on_rails.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'guides/source/contributing_to_ruby_on_rails.md') 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. -- cgit v1.2.3