Skip to content

doc: use consistent markdown in README #7971

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Trott wants to merge 4 commits into from
Closed

doc: use consistent markdown in README #7971

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
33fb018
doc: use consistent markdown in README
Trott Aug 3, 2016
8644a27
squash: shell -> console
Trott Aug 4, 2016
7582f08
squash: console -> shell
Trott Aug 4, 2016
3605f4b
squash: single line command
Trott Aug 4, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
squash: shell -> console
  • Loading branch information
@Trott
Trott committed Aug 4, 2016
commit 8644a278c958109de089ff73235ccfdf4cd9db4f
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,14 +92,14 @@ download.

The _SHASUM256.txt_ can be downloaded using curl.

```shell
```console
$ curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt
```

To check that a downloaded file matches the checksum, run
it through `sha256sum` with a command such as:

```shell
```console
$ grep node-vx.y.z.tar.gz SHASUMS256.txt | sha256sum -c -
```

Expand All @@ -115,7 +115,7 @@ the GPG keys of individuals authorized to create releases. They are
listed at the bottom of this README under [Release Team](#release-team).
Use a command such as this to import the keys:

```shell
```console
$ gpg --keyserver pool.sks-keyservers.net \
--recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D
```
Expand Down Expand Up @@ -346,7 +346,7 @@ Releases of Node.js and io.js will be signed with one of the following GPG keys:

The full set of trusted release keys can be imported by running:

```shell
```console
Copy link
Copy Markdown
Member

@ChALkeR ChALkeR Aug 4, 2016 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This either shouldn't be «```console» or the lines should start with a prompt like «$ » or «> ».
Or this is going to be formatted like text output.

I would just use sh or shell here (in this specific block), perhaps.

gpg --keyserver pool.sks-keyservers.net --recv-keys 9554F04D7259F04124DE6B476D5A82AC7E37093B
gpg --keyserver pool.sks-keyservers.net --recv-keys 94AE36675C464D64BAFA68DD7434390BDBE9B9C5
gpg --keyserver pool.sks-keyservers.net --recv-keys 0034A06D9D9B0064CE8ADF6BF1747F4AD2306D93
Expand Down