From 852a4b617a67227bcca161e58aaf586ea03b95bc Mon Sep 17 00:00:00 2001
From: Muescha <184316+muescha@users.noreply.github.com>
Date: Wed, 6 Jan 2021 19:00:24 +0100
Subject: [PATCH] fix code block to shell

---
 benchmarks/source-strapi/README.md          | 2 +-
 docs/docs/how-to/styling/using-web-fonts.md | 4 ++--
 packages/gatsby-admin/README.md             | 4 ++--
 packages/gatsby-recipes/CONTRIBUTING.md     | 2 +-
 starters/gatsby-starter-mdx-basic/README.md | 6 +++---
 5 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/benchmarks/source-strapi/README.md b/benchmarks/source-strapi/README.md
index a7b2647def253..e33c2be17e50a 100644
--- a/benchmarks/source-strapi/README.md
+++ b/benchmarks/source-strapi/README.md
@@ -8,6 +8,6 @@ Create a .env file from the template:
 
 Update data:
 
-```sh
+```shell
 yarn date-update
 ```
diff --git a/docs/docs/how-to/styling/using-web-fonts.md b/docs/docs/how-to/styling/using-web-fonts.md
index 809ff1336ff99..6fd5e0b226aad 100644
--- a/docs/docs/how-to/styling/using-web-fonts.md
+++ b/docs/docs/how-to/styling/using-web-fonts.md
@@ -53,13 +53,13 @@ You can add Typekit Web Fonts to your project by using the [gatsby-plugin-web-fo
 
 First, install the Gatsby plugin with npm:
 
-```bash
+```shell
 npm install --save gatsby-plugin-web-font-loader
 ```
 
 Or with yarn:
 
-```bash
+```shell
 yarn add gatsby-plugin-web-font-loader
 ```
 
diff --git a/packages/gatsby-admin/README.md b/packages/gatsby-admin/README.md
index 5b8ef3a10ad35..f51d2c5b7ccb6 100644
--- a/packages/gatsby-admin/README.md
+++ b/packages/gatsby-admin/README.md
@@ -6,7 +6,7 @@ A visual interface to configure your Gatsby site. Currently alpha testing.
 
 For now, Gatsby Admin is marked as experimental and requires a flag to enable. Add the following flag when using `gatsby develop`:
 
-```sh
+```shell
 GATSBY_EXPERIMENTAL_ENABLE_ADMIN=true gatsby develop
 ```
 
@@ -98,7 +98,7 @@ The easiest way to work on Admin locally is to develop Admin itself.
 
 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:
 
-```sh
+```shell
 # Make sure to build the latest local versions of all packages
 ~/gatsby
 yarn run watch
diff --git a/packages/gatsby-recipes/CONTRIBUTING.md b/packages/gatsby-recipes/CONTRIBUTING.md
index 2801332257e2d..59c5363b9ac9c 100644
--- a/packages/gatsby-recipes/CONTRIBUTING.md
+++ b/packages/gatsby-recipes/CONTRIBUTING.md
@@ -114,7 +114,7 @@ One note, as you’ll be testing changes to the Gatsby CLI — instead of runnin
 
 When debugging the CLI, you may run into errors without stacktraces. In order to work around that, you can use the node inspector:
 
-```sh
+```shell
 DEBUG=true node --inspect-brk ./node_modules/.bin/gatsby recipes ./test.mdx
 ```
 
diff --git a/starters/gatsby-starter-mdx-basic/README.md b/starters/gatsby-starter-mdx-basic/README.md
index 886eaf2d7df44..2fb4a899caf70 100644
--- a/starters/gatsby-starter-mdx-basic/README.md
+++ b/starters/gatsby-starter-mdx-basic/README.md
@@ -6,19 +6,19 @@ README also applies here.
 
 1. Create a new Gatsby site using this starter
 
-```sh
+```shell
 gatsby new my-site https://github.com/gatsbyjs/gatsby-starter-mdx-basic
 ```
 
 2. Install dependencies
 
-```sh
+```shell
 npm install
 ```
 
 3. Run the develop script
 
-```sh
+```shell
 gatsby develop
 ```