@@ -41,13 +41,13 @@ The release process works as follows:
 3. Jenkins SSHs into www and uses `rclone` to copy the file from www to R2 dist-staging
 
 During the v22.22.1 release:
-1. The first Jenkins job (17:14 UTC) completed successfully, uploading the initial signed package to both www and R2
+1. The first Jenkins job (17:14 UTC) completed successfully, uploading the initial signed package to both direct and R2
 2. The job was re-run, producing a new signed package at 21:00 UTC
-3. The second run successfully copied the new package to www
+3. The second run successfully copied the new package to direct
 4. The `rclone` step to R2 failed with `kex_exchange_identification: Connection closed by remote host`
-5. The Jenkins job marked the build as failed but did not roll back the www upload
+5. The Jenkins job marked the build as failed but did not roll back the direct upload
 
-This left www with the correct file (matching SHASUMS256.txt) while R2 served the outdated file, creating a checksum mismatch for most users.
+This left `direct.` with the correct file (matching SHASUMS256.txt) while R2 served the outdated file, creating a checksum mismatch for most users.
 
 ## Fix