Skip to content

Commit ef12dca

Browse files
authored
chore(docs): fix code block language to shell (#28895)
1 parent 5f711fc commit ef12dca

File tree

5 files changed

+9
-9
lines changed

5 files changed

+9
-9
lines changed

benchmarks/source-strapi/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,6 @@ Create a .env file from the template:
88

99
Update data:
1010

11-
```sh
11+
```shell
1212
yarn date-update
1313
```

docs/docs/how-to/styling/using-web-fonts.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -53,13 +53,13 @@ You can add Typekit Web Fonts to your project by using the [gatsby-plugin-web-fo
5353

5454
First, install the Gatsby plugin with npm:
5555

56-
```bash
56+
```shell
5757
npm install --save gatsby-plugin-web-font-loader
5858
```
5959

6060
Or with yarn:
6161

62-
```bash
62+
```shell
6363
yarn add gatsby-plugin-web-font-loader
6464
```
6565

packages/gatsby-admin/README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ A visual interface to configure your Gatsby site. Currently alpha testing.
66

77
For now, Gatsby Admin is marked as experimental and requires a flag to enable. Add the following flag when using `gatsby develop`:
88

9-
```sh
9+
```shell
1010
GATSBY_EXPERIMENTAL_ENABLE_ADMIN=true gatsby develop
1111
```
1212

@@ -98,7 +98,7 @@ The easiest way to work on Admin locally is to develop Admin itself.
9898

9999
To try Admin with one of your sites locally, use the `gatsby-dev-cli` to copy the local versions of `gatsby`, `gatsby-cli`, `gatsby-recipes`, `gatsby-core-utils` and `gatsby-admin` into your project:
100100

101-
```sh
101+
```shell
102102
# Make sure to build the latest local versions of all packages
103103
~/gatsby
104104
yarn run watch

packages/gatsby-recipes/CONTRIBUTING.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@ One note, as you’ll be testing changes to the Gatsby CLI — instead of runnin
114114

115115
When debugging the CLI, you may run into errors without stacktraces. In order to work around that, you can use the node inspector:
116116

117-
```sh
117+
```shell
118118
DEBUG=true node --inspect-brk ./node_modules/.bin/gatsby recipes ./test.mdx
119119
```
120120

starters/gatsby-starter-mdx-basic/README.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -6,19 +6,19 @@ README also applies here.
66

77
1. Create a new Gatsby site using this starter
88

9-
```sh
9+
```shell
1010
gatsby new my-site https://github.com/gatsbyjs/gatsby-starter-mdx-basic
1111
```
1212

1313
2. Install dependencies
1414

15-
```sh
15+
```shell
1616
npm install
1717
```
1818

1919
3. Run the develop script
2020

21-
```sh
21+
```shell
2222
gatsby develop
2323
```
2424

0 commit comments

Comments
 (0)