diff options
| author | Rohan Daxini <rohandaxini@users.noreply.github.com> | 2015-06-27 22:35:43 +0530 |
|---|---|---|
| committer | Rohan Daxini <rohandaxini@users.noreply.github.com> | 2015-06-27 22:35:43 +0530 |
| commit | 88973f8d3633886e112d7cec0047453fb9dafa0a (patch) | |
| tree | 0c84443ca966d03060427ed2842730cabc7a3050 | |
| parent | 329c249c9aff0b2cd37e17086477514d1c5d7eac (diff) | |
| download | rails-88973f8d3633886e112d7cec0047453fb9dafa0a.tar.gz rails-88973f8d3633886e112d7cec0047453fb9dafa0a.tar.bz2 rails-88973f8d3633886e112d7cec0047453fb9dafa0a.zip | |
Maintaining consistency in wordings [ci skip]
"reproduce" word is better suited then "replicate" as its also used at other places in this same document having same context. It will then be consistent across document.
| -rw-r--r-- | guides/source/contributing_to_ruby_on_rails.md | 2 |
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 3279c99c42..c19813c8a5 100644 --- a/guides/source/contributing_to_ruby_on_rails.md +++ b/guides/source/contributing_to_ruby_on_rails.md @@ -28,7 +28,7 @@ NOTE: Bugs in the most recent released version of Ruby on Rails are likely to ge If you've found a problem in Ruby on Rails which is not a security risk, do a search on 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. +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 reproduce the bug and figure out a fix. 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. |