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: https://github.com/nodejs/node/pull/15101
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
This commit is contained in:
Jon Moss 2017-08-30 15:12:31 -04:00 committed by Refael Ackermann
parent 0b0c2ec29a
commit 676522fc02
No known key found for this signature in database
GPG Key ID: CD704BD80FDDDB64

View File

@ -114,11 +114,11 @@ documentation of the latest stable version.
### Verifying Binaries ### Verifying Binaries
Current, LTS and Nightly download directories all contain a _SHASUM256.txt_ Current, LTS and Nightly download directories all contain a _SHASUMS256.txt_
file that lists the SHA checksums for each file available for file that lists the SHA checksums for each file available for
download. download.
The _SHASUM256.txt_ can be downloaded using curl. The _SHASUMS256.txt_ can be downloaded using curl.
```console ```console
$ curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt $ 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
downloaded)_ downloaded)_
Additionally, Current and LTS releases (not Nightlies) have GPG signed Additionally, Current and LTS releases (not Nightlies) have GPG signed
copies of SHASUM256.txt files available as SHASUM256.txt.asc. You can use copies of SHASUMS256.txt files available as SHASUMS256.txt.asc. You can use
`gpg` to verify that the file has not been tampered with. `gpg` to verify that the file has not been tampered with.
To verify a SHASUM256.txt.asc, you will first need to import all of To verify a SHASUMS256.txt.asc, you will first need to import all of
the GPG keys of individuals authorized to create releases. They are the GPG keys of individuals authorized to create releases. They are
listed at the bottom of this README under [Release Team](#release-team). listed at the bottom of this README under [Release Team](#release-team).
Use a command such as this to import the keys: Use a command such as this to import the keys: