diff --git a/Documentation/releases/checklist.md b/Documentation/releases/checklist.md
index 49045573d3..706d08e379 100644
--- a/Documentation/releases/checklist.md
+++ b/Documentation/releases/checklist.md
@@ -49,34 +49,34 @@ be more frequent than was needed, so we scaled it back to twice a year.
 ## Checklist
 ### ~2 weeks prior to release
 - [ ] Announce upcoming release to mailing list, ask people to test and
-      to update release notes
+      to update release notes.
 
 ### ~1 week prior to release
 - [ ] Send reminder email to mailing list, ask for people to test,
-      and to update the release notes
-- [ ] Update the topic in the irc channel with the date of the upcoming
-      release
+      and to update the release notes.
+- [ ] Update the topic in the IRC channel with the date of the upcoming
+      release.
 - [ ] If there are any deprecations announced for the following release,
-      make sure that a list of currently affected board and chipsets is
+      make sure that a list of currently affected boards and chipsets is
       part of the release notes.
 - [ ] Finalize release notes (as much as possible), without specifying
-      release commit ids
+      release commit ids.
 
 ### Day of release
 - [ ] Select a commit ID to base the release upon, announce to IRC,
       ask for testing.
-- [ ] Test the commit selected for release
-- [ ] Update release notes with actual commit id, push to repo
-- [ ] Run release script
-- [ ] Test the release from the actual release tarballs
-- [ ] Push signed Tag to repo
-- [ ] Announce that the release tag is done on IRC
+- [ ] Test the commit selected for release.
+- [ ] Update release notes with actual commit id, push to repo.
+- [ ] Run release script.
+- [ ] Test the release from the actual release tarballs.
+- [ ] Push signed Tag to repo.
+- [ ] Announce that the release tag is done on IRC.
 - [ ] Upload release files to web server
-- [ ] Upload crossgcc sources to web server
-- [ ] Update download page to point to files, push to repo
+- [ ] Upload crossgcc sources to web server.
+- [ ] Update download page to point to files, push to repo.
 - [ ] Write and publish blog post with release notes.
-- [ ] Update the topic in the irc channel that the release is done.
-- [ ] Announce the release to the mailing list
+- [ ] Update the topic in the IRC channel that the release is done.
+- [ ] Announce the release to the mailing list.
 
 ## Pre-Release tasks
 Announce the upcoming release to the mailing list release 2 weeks ahead
@@ -102,7 +102,7 @@ to have in the release.  The release was based on the final of those
 patches to be pulled in.
 
 When a release candidate has been selected, announce the commit ID to
-the #coreboot irc channel, and request that it get some testing, just
+the #coreboot IRC channel, and request that it get some testing, just
 to make sure that everything is sane.
 
 ## Generate the release