diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index c4e63bccd..20571b305 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -64,7 +64,6 @@ Resolves #001
 - [ ] If any model was updated to modify/add/delete columns, verified migrations can be run with `makemigrations`
 
 #### Validated user-facing changes as a developer
-
 **Note:** Multiple code reviewers can share the checklists above, a second reviewers should not make a duplicate checklist
 
 - [ ] New pages have been added to .pa11yci file so that they will be tested with our automated accessibility testing
@@ -86,13 +85,11 @@ Resolves #001
 
 - [ ] Checked different states (empty, one, some, error)
 - [ ] Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)
-
-#### Test support on multiple browsers. Check the browser(s) tested.
-- [ ] Chrome
-- [ ] Microsoft Edge
-- [ ] FireFox
-- [ ] Safari
-
+- [ ] Tested with multiple browsers (check off which ones were used)
+  - [ ] Chrome
+  - [ ] Microsoft Edge
+  - [ ] FireFox
+  - [ ] Safari
 - [ ] (Rarely needed) Tested as both an analyst and applicant user
 
 ## Screenshots
diff --git a/docs/dev-practices/code_review.md b/docs/dev-practices/code_review.md
index f30eec64e..09e6e0c1c 100644
--- a/docs/dev-practices/code_review.md
+++ b/docs/dev-practices/code_review.md
@@ -1,5 +1,8 @@
 ## Code Review
 
+Pull requests should be titled in the format of `#issue_number: Descriptive name ideally matching ticket name - [sandbox]`
+Any pull requests including a migration should be suffixed with ` - MIGRATION`
+
 After creating a pull request, pull request submitters should:
 - Add at least 2 developers as PR reviewers (only 1 will need to approve).
 - Message on Slack or in standup to notify the team that a PR is ready for review.
@@ -7,11 +10,13 @@ After creating a pull request, pull request submitters should:
 - If any updated dependencies on Pipfile, also update dependencies in requirements.txt.
 
 Code changes on user-facing features (excluding content updates) require approval from at least one developer and one designer.
-All other changes require just a single approving review.
+All other changes require a single approving review.
 
 ## Pull Requests for User-facing changes
 When making user-facing changes, test that your changes work on multiple browsers including Chrome, Microsoft Edge, Firefox, and Safari.
 
+Add new pages to the .pa11yci file so they are included in our automated accessibility testing.
+
 ## Coding standards
 (The Coding standards section may be moved to a new code standards file in a future ticket.
 For now we're simply moving PR template content into the code review document for consolidation)