aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorBrooks Reese <brooksreese@gmail.com>2014-12-05 10:00:42 -0600
committerBrooks Reese <brooksreese@gmail.com>2014-12-05 10:00:42 -0600
commit1a0e8e06b8d67c8948e91dd79174586cb7aac213 (patch)
treeb24b375112376576e80c54289c36a2bfec0c94da /guides
parent3e9c16aadbffbefd8c33562ad04bef8236136fe8 (diff)
downloadrails-1a0e8e06b8d67c8948e91dd79174586cb7aac213.tar.gz
rails-1a0e8e06b8d67c8948e91dd79174586cb7aac213.tar.bz2
rails-1a0e8e06b8d67c8948e91dd79174586cb7aac213.zip
Fix sentence structure [ci skip]
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 8e7007d34a..17afd07820 100644
--- a/guides/source/contributing_to_ruby_on_rails.md
+++ b/guides/source/contributing_to_ruby_on_rails.md
@@ -24,7 +24,7 @@ NOTE: Bugs in the most recent released version of Ruby on Rails are likely to ge
### Creating a Bug Report
-If you've found a problem in Ruby on Rails which is not a security risk, do a search in GitHub under [Issues](https://github.com/rails/rails/issues) in case it has already been reported. If you do not find any issue addressing it you may proceed to [open a new one](https://github.com/rails/rails/issues/new). (See the next section for reporting security issues.)
+If you've found a problem in Ruby on Rails which is not a security risk, do a search in GitHub under [Issues](https://github.com/rails/rails/issues) in case it has already been reported. If you are unable to find any open GitHub issues addressing the problem you found, your next step will be to [open a new one](https://github.com/rails/rails/issues/new). (See the next section for reporting security issues.)
Your issue report should contain a title and a clear description of the issue at the bare minimum. You should include as much relevant information as possible and should at least post a code sample that demonstrates the issue. It would be even better if you could include a unit test that shows how the expected behavior is not occurring. Your goal should be to make it easy for yourself - and others - to replicate the bug and figure out a fix.