Skip to content

Commit 42dd59d

Browse files
Trottsagitsofan
authored andcommitted
doc: use backticks around file names in README.md
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>
1 parent f414853 commit 42dd59d

File tree

1 file changed

+2
-10
lines changed

1 file changed

+2
-10
lines changed

README.md

Lines changed: 2 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -116,10 +116,10 @@ _docs_ subdirectory. Version-specific documentation is also at
116116

117117
### Verifying Binaries
118118

119-
Download directories contain a SHASUMS256.txt file with SHA checksums for the
119+
Download directories contain a `SHASUMS256.txt` file with SHA checksums for the
120120
files.
121121

122-
To download SHASUMS256.txt using `curl`:
122+
To download `SHASUMS256.txt` using `curl`:
123123

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

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

147139
```console
148140
$ gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D

0 commit comments

Comments
 (0)