Skip to content

Commit 1b0e660

Browse files
maclover7MylesBorins
authored andcommitted
doc: /s/SHASUM256/SHASUMS256
As an example, `curl https://nodejs.org/dist/v8.4.0/SHASUM256.txt` will return a 404 right now. PR-URL: #15101 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Refael Ackermann <[email protected]>
1 parent 6a7e46e commit 1b0e660

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -114,11 +114,11 @@ documentation of the latest stable version.
114114

115115
### Verifying Binaries
116116

117-
Current, LTS and Nightly download directories all contain a _SHASUM256.txt_
117+
Current, LTS and Nightly download directories all contain a _SHASUMS256.txt_
118118
file that lists the SHA checksums for each file available for
119119
download.
120120

121-
The _SHASUM256.txt_ can be downloaded using curl.
121+
The _SHASUMS256.txt_ can be downloaded using curl.
122122

123123
```console
124124
$ curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt
@@ -135,10 +135,10 @@ _(Where "node-vx.y.z.tar.gz" is the name of the file you have
135135
downloaded)_
136136

137137
Additionally, Current and LTS releases (not Nightlies) have GPG signed
138-
copies of SHASUM256.txt files available as SHASUM256.txt.asc. You can use
138+
copies of SHASUMS256.txt files available as SHASUMS256.txt.asc. You can use
139139
`gpg` to verify that the file has not been tampered with.
140140

141-
To verify a SHASUM256.txt.asc, you will first need to import all of
141+
To verify a SHASUMS256.txt.asc, you will first need to import all of
142142
the GPG keys of individuals authorized to create releases. They are
143143
listed at the bottom of this README under [Release Team](#release-team).
144144
Use a command such as this to import the keys:

0 commit comments

Comments
 (0)