diff --git a/Release-checklist.md b/Release-checklist.md
index d4ad7b6..6c4d48d 100644
--- a/Release-checklist.md
+++ b/Release-checklist.md
@@ -10,14 +10,15 @@ Note that some of these can be done concurrently.
 	- It also needs to be prepended to [the `ReleaseHistory` article](https://tasvideos.org/Bizhawk/ReleaseHistory) (TASVideos Wiki markup). Apart from changing markup language, also remember to include download links and the release date (will need to finish this after publishing).
 	- There's also [the ext. tool changelog](https://github.com/TASEmulators/BizHawk-ExternalTools/wiki/Partial-changelog-for-ApiHawk). If an ApiHawk change doesn't affect Lua then it might not warrant inclusion on the main changelog, but this one includes even the tiny method signature changes.
 1. Update `VersionInfo.MainVersion` if it was set for a point release but this will be a minor release
-1. Update the `release` branch to point to `master` (and wait for CI...)
+1. Update the `release` branch to point to `master`
+	- [GitLab CI](https://gitlab.com/TASVideos/BizHawk/-/pipelines?page=1&scope=all&ref=release) will build the `release` branch shortly after pushing it.
 1. Check for AV false positives
 	- Separately upload the release archive and `EmuHawk.exe` alone to [VirusTotal](https://www.virustotal.com/gui/home/upload). A false positive from the Microsoft engine is the only one that really matters.
 	- If it does happen... add a random `<EmbeddedResource/>` to the assembly or something and try again idk ¯\\\_(ツ)\_/¯
 1. Create a "Release" on GitHub
 	- Check the date—if it's April 1st or thereabouts, ABORT MISSION. Seriously, it's just not worth it.
 	- Set it to create a new tag.
-	- [GitLab CI](https://gitlab.com/TASVideos/BizHawk/-/pipelines?page=1&scope=all&ref=release) will build the `release` branch shortly after pushing it. Grab the `package_release_*` artifacts, replace "VERSIONHERE" in the filenames, recompress the Linux release as `.tar.gz`, and attach them to the Release.
+	- Take the `package_release_*` artifacts you've already downloaded, replace "VERSIONHERE" in the filenames, recompress the Linux release as `.tar.gz`, and attach them to the Release.
 	- For the description, list any new or graduating cores, optionally some large improvements, and if the Windows prereq installer was updated link that too.
 	- Click "Publish" and pray.
 1. Update Issues, Labels, and Milestone on GitHub