aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorRafael Mendonça França <rafaelmfranca@gmail.com>2014-12-05 18:41:01 -0200
committerRafael Mendonça França <rafaelmfranca@gmail.com>2014-12-05 18:41:01 -0200
commita78736bd48408976459b7ff4279d5e6f356a970f (patch)
treee9cd44f994e40b584b3adc7a4e18af63ceba3e68 /guides
parent19243f3d8c6ac6397a34ae7eb9dc9da368986a22 (diff)
parent1a0e8e06b8d67c8948e91dd79174586cb7aac213 (diff)
downloadrails-a78736bd48408976459b7ff4279d5e6f356a970f.tar.gz
rails-a78736bd48408976459b7ff4279d5e6f356a970f.tar.bz2
rails-a78736bd48408976459b7ff4279d5e6f356a970f.zip
Merge pull request #17932 from brooksreese/master
Fix grammar in Rakefile markup [ci skip]
Diffstat (limited to 'guides')
-rw-r--r--guides/Rakefile2
-rw-r--r--guides/source/contributing_to_ruby_on_rails.md2
2 files changed, 2 insertions, 2 deletions
diff --git a/guides/Rakefile b/guides/Rakefile
index 824bea0b39..fd093b94c1 100644
--- a/guides/Rakefile
+++ b/guides/Rakefile
@@ -40,7 +40,7 @@ part of the generation process.
You can generate HTML, Kindle or both formats using the `guides:generate` task.
-All this process is handled via rake tasks, here's a full list of them:
+All of these processes are handled via rake tasks, here's a full list of them:
#{%x[rake -T]}
Some arguments may be passed via environment variables:
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.