diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 0382a8768a..082448c371 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,45 +1,22 @@
-<!-- HTML Comments can be left in place or removed, dealers choice. They are present simply to guide you on your pull-request journey. --> 
-Proposed changes
-======
-<!-- 
+<!-- HTML Comments can be left in place or removed. -->
 
-Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
+#### Proposed Changes ####
 
--->
+<!-- Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. -->
 
-Types of changes
-======
-<!-- 
+#### Types of Changes ####
 
-What types of changes does your code introduce to Rancher?
-- Bugfix (non-breaking change which fixes an issue)
-- New feature (non-breaking change which adds functionality)
-- Breaking change (fix or feature that would cause existing functionality to not work as expected)
+<!-- What types of changes does your code introduce to K3s? Bugfix, New Feature, Breaking Change, etc -->
 
--->
+#### Verification ####
 
-Verification
-======
-<!--
+<!-- How can the changes be verified? Please provide whatever additional information necessary to help verify the proposed changes. -->
 
-How can the changes be verified? Please provide whatever additional information necessary to help verify the proposed changes.
+#### Linked Issues ####
 
--->
+<!-- Link any related issues, pull-requests, or commit hashes that are relevant to this pull request. If you are opening a PR without a corresponding issue please consider creating one first, at https://github.com/rancher/k3s/issues . A functional example will greatly help QA with verifying/reproducing a bug or testing new features. -->
 
-Linked Issues
-======
-<!--
+#### Further Comments ####
 
-Link any related issues, pull-requests, or commit hashes that are relavent to this pull request.
+<!-- If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... -->
 
-If you are opening a PR without a corresponding issue please consider creating one first, [here](https://github.com/rancher/k3s/issues). A functional example will greatly help QA with verifying/reproducing a bug or testing new features.
-
---> 
-
-Further comments
-======
-<!-- 
-
-If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... 
-
--->