aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/contributing_to_ruby_on_rails.md
diff options
context:
space:
mode:
authorXavier Noria <fxn@hashref.com>2015-04-20 11:30:42 +0200
committerXavier Noria <fxn@hashref.com>2015-04-20 11:30:46 +0200
commite539866d80fa614412f65a12a63a9063fd89ce5e (patch)
treeb93dc8283d6df0e8acb4573d9cda184f23e9df0d /guides/source/contributing_to_ruby_on_rails.md
parentb4546b393436fc5bb25aa4b70256306e0d2e988c (diff)
downloadrails-e539866d80fa614412f65a12a63a9063fd89ce5e.tar.gz
rails-e539866d80fa614412f65a12a63a9063fd89ce5e.tar.bz2
rails-e539866d80fa614412f65a12a63a9063fd89ce5e.zip
capitalize title
According to the guidelines: http://guides.rubyonrails.org/ruby_on_rails_guides_guidelines.html#headings References #19821.
Diffstat (limited to 'guides/source/contributing_to_ruby_on_rails.md')
-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 769bcf60db..7778b6c5e0 100644
--- a/guides/source/contributing_to_ruby_on_rails.md
+++ b/guides/source/contributing_to_ruby_on_rails.md
@@ -32,7 +32,7 @@ Your issue report should contain a title and a clear description of the issue at
Then, don't get your hopes up! Unless you have a "Code Red, Mission Critical, the World is Coming to an End" kind of bug, you're creating this issue report in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the issue report will automatically see any activity or that others will jump to fix it. Creating an issue like this is mostly to help yourself start on the path of fixing the problem and for others to confirm it with an "I'm having this problem too" comment.
-### Create an executable test case
+### Create an Executable Test Case
Having a way to reproduce your issue will be very helpful for others to help confirm, investigate and ultimately fix your issue. You can do this by providing an executable test case. To make this process easier, we have prepared several bug report templates for you to use as a starting point: