From 9b6f9a0b18a922713ce69ed9c76dc3dda6133441 Mon Sep 17 00:00:00 2001 From: Zeke Sikelianos Date: Tue, 26 Sep 2017 11:10:29 -0700 Subject: [PATCH] fix typos in releasing doc --- docs/development/releasing.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/development/releasing.md b/docs/development/releasing.md index 1f289382b617..ebb74beefb61 100644 --- a/docs/development/releasing.md +++ b/docs/development/releasing.md @@ -235,10 +235,11 @@ Then edit the release on GitGub: ## Fix missing binaries of a release manually In the case of a corrupted release with broken CI machines, we might have to -re-upload the binaries for a already published release. +re-upload the binaries for an already published release. -The first step is to go to the Releases page and delete the corrupted binaries -with the `SHASUMS256.txt` checksum file. +The first step is to go to the +[Releases](https://github.com/electron/electron/releases) page and delete the +corrupted binaries with the `SHASUMS256.txt` checksum file. Then manually create distributions for each platform and upload them: @@ -255,9 +256,9 @@ git checkout vTHE.RELEASE.VERSION ./script/upload.py --overwrite ``` -After re-uploading all distributions, do publish again to upload the checksum +After re-uploading all distributions, publish again to upload the checksum file: ```sh npm run release -``` +``` \ No newline at end of file