Add some more detail on contributing

Author: dhower-qc

CONTRIBUTING.adoc

@@ -7,25 +7,33 @@ We welcome all contributions that fall within our xref:CODE_OF_CONDUCT.adoc[code
 
 === Bug Reports
 
-Bug reports should be filed as a GitHub Issue using the Bug report template.
+Bug reports should be filed as a https://github.com/riscv-software-src/riscv-unified-db/issues[GitHub Issue] using the `Bug report` template.
 
 === Feature Requests
 
-Bug reports should be filed as a GitHub Issue using the Feature request template.
+Bug reports should be filed as a https://github.com/riscv-software-src/riscv-unified-db/issues[GitHub Issue] using the `Feature request` template.
 
 === Bug Fixes
 
 Bug fixes should be submitted as a Pull Request.
 
+There should be a corresponding https://github.com/riscv-software-src/riscv-unified-db/issues[GitHub Issue] for the PR. Ensure the two are linked by adding "closes #<issue number>" in the PR description.
+
 === New data, tools, and features
 
 New data (for example, adding an extension), tools, or features should be submitted as a Pull Request.
 
-== Submitting a patch
+There should be a corresponding https://github.com/riscv-software-src/riscv-unified-db/issues[GitHub Issue] for the PR. Ensure the two are linked by adding "closes #<issue number>" in the PR description.
+
+== Submitting a Pull Request
 
 All patches must meet the UnifiedDB code standards. This includes:
 
 * Pass regression tests (run locally as `./do test:regress`)
 * Go through code review as a Pull Request
 ** Code owners must approve
 * Use appropriate commit messages (TODO: commit message policy)
+
+== Finding tasks
+
+If you are looking to contribute but are unsure what to do, browse through the https://github.com/riscv-software-src/riscv-unified-db/issues[issues]. We try to keep them tagged by area and mark easier tasks with "good first issue".