diff --git a/CODE_REVIEWS.md b/CODE_REVIEWS.md
index 87206fb20b30..f4680927468b 100644
--- a/CODE_REVIEWS.md
+++ b/CODE_REVIEWS.md
@@ -1,16 +1,19 @@
 # Code reviews for Angular Material
 
-* Before any coding begins on new, large, or breaking work, a design discussion should take place.
-* All code changes require a review and approval.
-* All behaviors should be covered by unit tests in the same PR.
-* Large changes should be accompanied by corresponding e2e tests in the same PR.
-* Authors should attempt to keep PRs to 200 - 300 line changes.
+- Before any coding begins on new, large, or breaking work, a design discussion should take place
+- All code changes require a review and approval
+- All behaviors should be covered by unit tests in the same PR
+- Large changes should be accompanied by corresponding e2e tests in the same PR
+- Authors should attempt to keep PRs to 200 - 300 line changes
 
 ## Workflow
+
 1. The code author sends a PR for review. This request should include:
-  * A high-level description of the change being made.
-  * Links to any relevant issues.
-  * Screenshots (for visual changes or new additions)
+
+   - A high-level description of the change being made
+   - Links to any relevant issues
+   - Screenshots (for visual changes or new additions)
+
 2. Reviews provide comments and the author responds / makes changes. Repeat until LGTM.
 3. One or more of the reviewers approve the pull request.
 4. Once the PR is approved, either the author or the reviewer can add the "merge-ready"
@@ -18,6 +21,7 @@
 5. The party responsible for merging PRs will do so.
 
 ## How PRs are merged
+
 The team has a weekly rotation for the "caretaker" who is responsible for merging PRs. Before being
 merged, the caretaker runs PRs through Google's internal presubmit system. This process helps
 greatly in keeping the library stable by running against the tests of many applications inside of