Update CONTRIBUTING.md

Author: jackzhxng

.github/pull_request_template.md

@@ -1,9 +1,10 @@
 ### Summary
-[PLEASE REMOVE] Describe the goal of this PR and any add any relevant context.
+[PLEASE REMOVE] Describe the goal of this PR and add any relevant context.
 
 [PLEASE REMOVE] If this PR closes an issue, please add a `Fixes #<issue-id>` line.
 
 [PLEASE REMOVE] If this PR introduces a fix or feature that should be the upcoming release notes, please add a "Release notes: <area>" label.
 
 ### Test plan
-[PLEASE REMOVE] How did you test this PR? Please write down any manual commands you used and note down tests that you have written.
+[PLEASE REMOVE] How did you test this PR? Please write down any manual commands you used and note down tests that you have written if applicable.
+

CONTRIBUTING.md

@@ -250,8 +250,8 @@ for basics.
        future editor understand how to test the code that you're modifying
        today.
    - If your PR contains or is representative of a feature/bug fix that should be
-     called out in the release notes, please add a label for "Release notes: <area>",
-	 where <area> describes which part of ExecuTorch the change pertains to, e.g.
+     called out in the release notes, please add a label for "Release notes: \<area\>",
+	 where \<area\> describes which part of ExecuTorch the change pertains to, e.g.
 	 "Release notes: runtime". A few of these areas include  "runtime", "backends",
 	 and "build". If you aren't sure whether to add a release label, you should
 	 probably still add one since it immensely facilitates release management.