Commit cb09959
doc: improve readability of README.md
Use consistent typography and other minor changes to Verifying Binaries
section.
PR-URL: #17519
Reviewed-By: Jon Moss <me@jonathanmoss.me>
Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>1 parent 0948238 commit cb09959
1 file changed
Lines changed: 6 additions & 10 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -116,11 +116,11 @@ documentation of the latest stable version. | |||
| 116 | 116 | ||
| 117 | 117 | ### Verifying Binaries | |
| 118 | 118 | ||
| 119 | - Current, LTS, and Nightly download directories all contain a _SHASUMS256.txt_ | ||
| 119 | + Current, LTS, and Nightly download directories all contain a SHASUMS256.txt | ||
| 120 | 120 | file that lists the SHA checksums for each file available for | |
| 121 | 121 | download. | |
| 122 | 122 | ||
| 123 | - The _SHASUMS256.txt_ can be downloaded using curl. | ||
| 123 | + The SHASUMS256.txt can be downloaded using `curl`. | ||
| 124 | 124 | ||
| 125 | 125 | ```console | |
| 126 | 126 | $ curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt | |
@@ -133,12 +133,9 @@ it through `sha256sum` with a command such as: | |||
| 133 | 133 | $ grep node-vx.y.z.tar.gz SHASUMS256.txt | sha256sum -c - | |
| 134 | 134 | ``` | |
| 135 | 135 | ||
| 136 | - _(Where "node-vx.y.z.tar.gz" is the name of the file you have | ||
| 137 | - downloaded)_ | ||
| 138 | - | ||
| 139 | - Additionally, Current and LTS releases (not Nightlies) have the GPG | ||
| 140 | - detached signature of SHASUMS256.txt available as SHASUMS256.txt.sig. | ||
| 141 | - You can use `gpg` to verify that SHASUMS256.txt has not been tampered with. | ||
| 136 | + Current and LTS releases (but not Nightlies) also have the GPG detached | ||
| 137 | + signature of SHASUMS256.txt available as SHASUMS256.txt.sig. You can use `gpg` | ||
| 138 | + to verify that SHASUMS256.txt has not been tampered with. | ||
| 142 | 139 | ||
| 143 | 140 | To verify SHASUMS256.txt has not been altered, you will first need to import | |
| 144 | 141 | all of the GPG keys of individuals authorized to create releases. They are | |
@@ -149,8 +146,7 @@ Use a command such as this to import the keys: | |||
| 149 | 146 | $ gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D | |
| 150 | 147 | ``` | |
| 151 | 148 | ||
| 152 | - _(See the bottom of this README for a full script to import active | ||
| 153 | - release keys)_ | ||
| 149 | + See the bottom of this README for a full script to import active release keys. | ||
| 154 | 150 | ||
| 155 | 151 | Next, download the SHASUMS256.txt.sig for the release: | |
| 156 | 152 | ||
0 commit comments