Skip to content

Commit

Permalink
doc: use backticks around file names in README.md
Browse files Browse the repository at this point in the history
Use backticks around `SHASUM256.txt` etc. in README.md.

PR-URL: nodejs#23299
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
  • Loading branch information
Trott authored and sagitsofan committed Oct 12, 2018
1 parent f414853 commit 42dd59d
Showing 1 changed file with 2 additions and 10 deletions.
12 changes: 2 additions & 10 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -116,10 +116,10 @@ _docs_ subdirectory. Version-specific documentation is also at

### Verifying Binaries

Download directories contain a SHASUMS256.txt file with SHA checksums for the
Download directories contain a `SHASUMS256.txt` file with SHA checksums for the
files.

To download SHASUMS256.txt using `curl`:
To download `SHASUMS256.txt` using `curl`:

```console
$ curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt
Expand All @@ -132,17 +132,9 @@ it through `sha256sum` with a command such as:
$ grep node-vx.y.z.tar.gz SHASUMS256.txt | sha256sum -c -
```

<<<<<<< HEAD
For Current and LTS, the GPG detached signature of `SHASUMS256.txt` is in
`SHASUMS256.txt.sig`. You can use it with `gpg` to verify the integrity of
`SHASUM256.txt`. You will first need to import all the GPG keys of individuals
=======
For Current and LTS, the GPG detached signature of SHASUMS256.txt is in
SHASUMS256.txt.sig. You can use it with `gpg` to verify the integrity of
SHASUM256.txt. You will first need to import all the GPG keys of individuals
>>>>>>> doc: improve instructions for verifying binaries
authorized to create releases. They are at the bottom of this README under
[Release Team](#release-team). To import the keys:

```console
$ gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D
Expand Down

0 comments on commit 42dd59d

Please sign in to comment.