Update .github docs

# CONTRIBUTING.md

- Fix relative pathing to other `.github` Markdown docs.
- Update/correct request forwarding, as the Issues tracker has been disabled for the repo.

# CODE_OF_CONDUCT.md

- Fix a grammar nit.
  - `eg` should be spelled `e.g.,` as it's an acronym.
- Remove a broken link to the TODO group's CoC template.
  - It's been updated significantly, along with the URL. Referring to it
    by a direct link doesn't make sense--unless using a service like
    `archive.org`.

# ISSUE_TEMPLATE.md
Remove since the Issue tracker has been disabled on the repo.

# PULL_REQUEST_TEMPLATE.md
Fix branding for `GitHub`.

Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>

Author: ngie-eign

.github/CODE_OF_CONDUCT.md

@@ -17,7 +17,7 @@ Harassment includes, but is not limited to:
 * Offensive comments related to gender, gender identity and expression, sexual orientation, disability, mental illness, neuro(a)typicality, physical appearance, body size, race, age, regional discrimination, political or religious affiliation
 * Unwelcome comments regarding a person’s lifestyle choices and practices, including those related to food, health, parenting, drugs, and employment
 * Deliberate misgendering. This includes deadnaming or persistently using a pronoun that does not correctly reflect a person’s gender identity. You must address people by the name they give you when not addressing them by their username or handle
-* Physical contact and simulated physical contact (eg, textual descriptions like “hug” or “backrub”) without consent or after a request to stop
+* Physical contact and simulated physical contact, e.g, textual descriptions like “hug” or “backrub”, without consent or after a request to stop
 * Threats of violence, both physical and psychological
 * Incitement of violence towards any individual, including encouraging a person to commit suicide or to engage in self-harm
 * Deliberate intimidation
@@ -35,4 +35,4 @@ We encourage everyone to participate and are committed to building a community f
 
 Although this list cannot be exhaustive, we explicitly honor diversity in age, gender, gender identity or expression, culture, ethnicity, language, national origin, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, and technical ability. We will not tolerate discrimination based on any of the protected characteristics above, including participants with disabilities.
 
-_This Code Of Conduct follows the [template](http://todogroup.org/opencodeofconduct/) established by the [TODO Group](http://todogroup.org/)._
+_This Code Of Conduct follows an earlier version of the [TODO Group](http://todogroup.org/)'s Code of Conduct template._

.github/CONTRIBUTING.md

@@ -1,15 +1,17 @@
 # Contributing to Blackduck Software Integration's
 
-If you decide to contribute to our repository, please follow our [Code of conduct](./CODE_OF_CONDUCT.md) when contributing. We value all contributions and will review them as soon as we can.
+If you decide to contribute to our repository, please follow our [Code of conduct](/.github/CODE_OF_CONDUCT.md) when contributing. We value all contributions and will review them as soon as we can.
 
-### Bugs
-When using our software, it is possible that you will come across a bug. If this happens, Be sure to come to our issues page to see if anyone else has ran into this same problem. If no one has reported it, then please submit an issue following this [Issue template](./ISSUE_TEMPLATE.md).
+## Support
 
-### Issues
-When you don't run into a bug, but have an issue or a question, then the best option is to message our [Support team](https://www.blackducksoftware.com/support/contact-support). They are available 24 hours a day and work directly with us to resolve any issues you may have.
+### Paid Support
+The best option for customers with active support contracts is to directly message our [Support team](https://www.blackducksoftware.com/support/contact-support). The support team is available 24 hours a day.
+
+### Community Support
+Community support is available in the [BlackDuck Community portal](https://community.blackduck.com/s/). Questions (which includes, but is not limited to reporting bugs, feature requests, etc) can be directed to the [BlackDuck Community Discussions](https://community.blackduck.com/s/discussions) board.
 
 ## Pull Requests
-Anyone can directly contribute to our integrations by opening their own branch and creating a pull request. When doing so, please follow the [Pull request template](./PULL_REQUEST_TEMPLATE.md) so that we can review your request more quickly and get your code into master.
+Anyone can directly contribute to our integrations by opening their own branch and creating a pull request. When doing so, please follow the [Pull request template](/.github/PULL_REQUEST_TEMPLATE.md) so that we can review your request more quickly and get your code into master.
 
 When creating code to be merged into our project, please adhere to the following as best you can
 * Create variable and method names that describe their functionality

.github/ISSUE_TEMPLATE.md

@@ -1,7 +1,21 @@
+<!--
+Delete all items in between the HTML comments (`&lt;!-- --%gt;`)
+-->
+
 # Description
 
+<!--
+
 Please include a short description of the changes and problems fixed.
 
+-->
+
 # Github Issues
 
-(Optional) Please link to any applicable github issues.
+<!--
+
+(Optional)
+
+Please reference any applicable GitHub issues as discussed in the [GitHub Docs](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword#linking-a-pull-request-to-an-issue-using-a-keyword).
+
+-->