doc: Update contributing guidelines to emphasize issues (#1231)

* Update CONTRIBUTING.md

* Apply suggestions from code review

Co-authored-by: Kendall Totten <[email protected]>

* Update CONTRIBUTING.md

* Update CONTRIBUTING.md

* Update CONTRIBUTING.md

* Update CONTRIBUTING.md

Co-authored-by: Kendall Totten <[email protected]>

Author: castastrophe

CONTRIBUTING.md

@@ -5,30 +5,12 @@
 [cc]: https://www.conventionalcommits.org/en/v1.0.0/#summary
 [doc]: https://patternfly.github.io/patternfly-elements/getting-started/
 
-
 Welcome Flyers!  We're so excited that you're considering contributing to PatternFly Elements, the web component implementation of the PatternFly design system.
 
 Contributions to this project are [released](https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license) to the public under the [project's open source license](LICENSE.md).
 
 Please note that this project is released with a [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.
 
-## Submitting a pull request
-
-1. [Fork][fork] and clone the repository (see the Quick start in the [README][README.md])
-2. Create a new branch.  Please use the [conventional commit](cc) formatting for the branch name.
-    > `git checkout -b feat-my-branch-name`
-3. Make your change, [add tests](https://patternfly.github.io/patternfly-elements/develop/step-3/), and make sure the automated testing passes.
-4. Push to your fork and [submit a pull request][pr].  Be sure to select from the available PR templates.
-
-
-Here are a few things you can do that will increase the likelihood of your pull request being accepted:
-
-- Review the documentation.
-- Follow the style/format of the existing code.
-- Write tests for your changes.
-- Keep your change as focused as possible; if there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
-- Be responsive during code review, as much as possible.
-
 ## Submitting an Issue
 
 ### Bug Reporting
@@ -50,9 +32,26 @@ If you have a feature that you think would be a great addition to the project:
 
 To suggest a feature use the [feature request template](.github/ISSUE_TEMPLATE/feature_request.md).
 
+## Submitting a pull request
+
+1. Check the [issue queue](https://github.com/patternfly/patternfly-elements/issues).  If your pull request does not map to an issue in the queue, please open a [new issue](https://github.com/patternfly/patternfly-elements/issues).
+2. [Fork][fork] and clone the repository (see the Quick start in the [README][README.md])
+3. Create a new branch.  Please use the [conventional commit](cc) formatting for the branch name.
+    git checkout -b feat-my-branch-name
+4. Make your change, [add tests](https://patternfly.github.io/patternfly-elements/develop/step-3/), and make sure the automated testing passes.
+5. Push to your fork and [submit a pull request][pr].  Be sure to select from the available PR templates.
+
+
+Here are a few things you can do that will increase the likelihood of your pull request being accepted:
+
+- Review the documentation.
+- Follow the style/format of the existing code.
+- Write tests for your changes.
+- Keep your change as small and focused as possible; if there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
+- Be responsive during code review, as much as possible.
 
 ## Resources
 
 - [Contributing to Open Source on GitHub](https://guides.github.com/activities/contributing-to-open-source/)
 - [Using Pull Requests](https://help.github.com/articles/using-pull-requests/)
-- [GitHub Help](https://help.github.com)
+- [GitHub Help](https://help.github.com)