chore: update PR template

Author: dreamorosi

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,25 +1,28 @@
-**Issue #, if available:**
+## Summary
 
-## Description of changes:
+### Changes
 
-<!--- One or two sentences as a summary of what's being changed -->
+> Please provide a summary of what's being changed
 
-**Checklist**
+<!-- What is this PR solving? Write a clear description or reference the issue(s) it addresses. -->
 
-<!--- Leave unchecked if your change doesn't seem to apply --> 
+> Please add the issue number below, if no issue is present the PR might get blocked and not be reviewed
 
-* [ ] [Meet tenets criteria](https://docs.powertools.aws.dev/lambda-java/#tenets)
-* [ ] Update tests
-* [ ] Update docs
-* [ ] PR title follows [conventional commit semantics](https://www.conventionalcommits.org/en/v1.0.0/)
+**Issue number:** 
 
-## Breaking change checklist
+<!-------
+Before creating the pull request, please make sure you do the following:
 
-<!--- Ignore if it's not a breaking change -->
+- Read the Contributing Guidelines at https://github.com/aws-powertools/powertools-lambda-java/blob/main/CONTRIBUTING.md#sending-a-pull-request
+- Check that there isn't already a PR that addresses the same issue. If you find a duplicate, please leave a comment under the existing PR so we can discuss how to move forward
+- Check that the change meets the project's tenets https://docs.powertools.aws.dev/lambda/typescript/java/#tenets
+- Add a PR title that follows the conventional commit semantics - https://www.conventionalcommits.org/en/v1.0.0/
+- If relevant, add tests that prove that the change is effective and works
+- Whenever relevant, make sure to comment functions/methods/types and make appropriate changes to the documentation
+------->
 
-**RFC issue #**:
-
-* [ ] Migration process documented
-* [ ] Implement warnings (if it can live side by side)
+---
 
 By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
+
+**Disclaimer**: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.