Implement comments review from Ashley on rspec#1705

Author: benoittgt

CONTRIBUTING.md

@@ -24,27 +24,31 @@ If you need help getting started, check out the [DEVELOPMENT](DEVELOPMENT.md) fi
 
 Thanks for helping us make RSpec better!
 
-## `Small` issues
+## Rspec issues labels definition
+
+### `Your first PR` issues
 
 These issues are the ones that we be believe are best suited for new
 contributors to get started on. They represent a potential meaningful
 contribution to the project that should not be too hard to pull off.
 
-## `Triage` issues
+### `Needs reproduction case` issues
 
 These issues are ones that have been labelled by the maintainers that we
 believe do not currently have enough information to be reproduced the RSpec
 team. While not directly counted by the GitHub contribution graph, we consider
-helping us triage issues to the point where they can be reproduced as an
-extremely meaningful contribution.
+helping us to reproduced the issue with a repro case as an extremely meaningful
+contribution.
 
-## `Has reproduction case` issues
+### `Has reproduction case` issues
 
 Issues that have reproduction cases have a repository that we can clone that
 enable us to quickly determine the issue is valid and then start debugging
 within RSpec. These issues are good ones to tackle to help us actively fix bugs.
 
-## Maintenance branches
+## Dev environment
+
+### Maintenance branches
 
 Maintenance branches are how we manage the different supported point releases
 of RSpec. As such, while they might look like good candidates to merge into

ISSUE_TEMPLATE.md

@@ -14,6 +14,24 @@ resolve your bug faster!
 
 -->
 
+## What Ruby, Rails and RSpec versions are you using?
+
+Ruby version:
+Rails version:
+Rspec version:
+
+<!--
+
+You can run
+
+```
+bundle exec ruby --version
+bundle exec rails --version
+bundle exec rspec --version
+```
+
+-->
+
 ## Observed behaviour
 
 <!--
@@ -45,21 +63,6 @@ your issue, and we typically ask that you follow these steps:
 5. Provide a link to a github repo, a description of the app and what you're expecting here
 -->
 
-## What Ruby, Rails and RSpec versions are you using?
-
-<!--
-
-You can run
-
-```
-bundle exec ruby --version
-bundle exec rails --version
-bundle exec rspec --version
-```
-
-and paste the output below
-
--->
 
 ## Did this problem exist before you upgraded to Rails 5?