update PR template for new etiquette

Author: roothorp

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,5 +1,25 @@
-### All Submissions:
+# Summary
+
+<!-- Enter your issue summary here.-->
+
+## Proof of Work
+
+<!-- Enter your proof that it works here.-->
+
+## Checklist
+- [ ] Have you linked a jira ticket and/or is the ticket in the title?
+- [ ] Have you checked whether your jira ticket required DOCSP changes?
+- [ ] Have you checked for release_note changes?
+- [ ] Have you signed our [CLA](https://www.mongodb.com/legal/contributor-agreement)?
+
+## Reminder (Please remove this when merging)
+- Please try to Approve or Reject Changes the PR, keep PRs in review as short as possible
+- Our Short Guide for PRs: [Link](https://docs.google.com/document/d/1T93KUtdvONq43vfTfUt8l92uo4e4SEEvFbIEKOxGr44/edit?tab=t.0)
+- Remember the following Communication Standards - use comment prefixes for clarity:
+  * **blocking**: Must be addressed before approval.
+  * **follow-up**: Can be addressed in a later PR or ticket.
+  * **q**: Clarifying question.
+  * **nit**: Non-blocking suggestions.
+  * **note**: Side-note, non-actionable. Example: Praise 
+  * --> no prefix is considered a question
 
-* [ ] Have you signed our [CLA](https://www.mongodb.com/legal/contributor-agreement)?
-* [ ] Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if there is one).
-* [ ] Update docs/release-notes/release-notes-template.md if your changes should be included in the release notes for the next release.