From bb2283b44bf288096156259febe9807dc2e51d2e Mon Sep 17 00:00:00 2001 From: Amaan Iqbal Date: Wed, 16 Jun 2021 21:34:15 +0530 Subject: [PATCH] Fix multiple grammar issues --- packages/gatsby-cli/README.md | 4 ++-- packages/gatsby-codemods/README.md | 2 +- packages/gatsby-design-tokens/README.md | 4 ++-- packages/gatsby-dev-cli/README.md | 6 +++--- packages/gatsby-plugin-gatsby-cloud/README.md | 2 +- 5 files changed, 9 insertions(+), 9 deletions(-) diff --git a/packages/gatsby-cli/README.md b/packages/gatsby-cli/README.md index ea20ce9667d4b..0620689989386 100644 --- a/packages/gatsby-cli/README.md +++ b/packages/gatsby-cli/README.md @@ -102,7 +102,7 @@ At the root of a Gatsby app run `gatsby build` to do a production build of a sit | `--open-tracing-config-file` | Tracer configuration file (OpenTracing compatible). See https://www.gatsbyjs.org/docs/performance-tracing/ | | | `--no-color`, `--no-colors` | Disables colored terminal output | `false` | -For prefixing paths, most will want to use the CLI flag (`gatsby build --prefix-paths`). For environments where you can't pass the --prefix-paths flag (ie Gatsby Cloud),the environment variable `PREFIX_PATHS` can be set to `true` to provide another way to prefix paths. +For prefixing paths, most will want to use the CLI flag (`gatsby build --prefix-paths`). For environments where you can't pass the --prefix-paths flag (ie Gatsby Cloud), the environment variable `PREFIX_PATHS` can be set to `true` to provide another way to prefix paths. ### `serve` @@ -117,7 +117,7 @@ At the root of a Gatsby app run `gatsby serve` to serve the production build of | `-o`, `--open` | Open the site in your (default) browser for you | | | `--prefix-paths` | Serve site with link paths prefixed (if built with pathPrefix in your gatsby-config.js). | `env.PREFIX_PATHS` or `false` | -For prefixing paths, most will want to use the CLI flag (`gatsby build --prefix-paths`). For environments where you can't pass the --prefix-paths flag (ie Gatsby Cloud),the environment variable `PREFIX_PATHS` can be set to `true` to provide another way to prefix paths. +For prefixing paths, most will want to use the CLI flag (`gatsby build --prefix-paths`). For environments where you can't pass the --prefix-paths flag (ie Gatsby Cloud), the environment variable `PREFIX_PATHS` can be set to `true` to provide another way to prefix paths. ### `clean` diff --git a/packages/gatsby-codemods/README.md b/packages/gatsby-codemods/README.md index 85037062370cc..5a26ff44ba524 100644 --- a/packages/gatsby-codemods/README.md +++ b/packages/gatsby-codemods/README.md @@ -16,7 +16,7 @@ npx gatsby-codemods `filepath` is not required and will default to the directory you're currently in. -Note that you cannot pass additional flags to this command. It will automatically run the codemod against file extenstions `js, jsx, ts, tsx` and ignore the `node_modules`, `.cache` and `public` directories of your project. +Note that you cannot pass additional flags to this command. It will automatically run the codemod against file extensions `js, jsx, ts, tsx` and ignore the `node_modules`, `.cache` and `public` directories of your project. 2. Use JSCodeshift directly diff --git a/packages/gatsby-design-tokens/README.md b/packages/gatsby-design-tokens/README.md index b94a95902bd68..49dc8813fa5eb 100644 --- a/packages/gatsby-design-tokens/README.md +++ b/packages/gatsby-design-tokens/README.md @@ -28,7 +28,7 @@ Gatsby's design tokens are following the [System UI Theme Specification](https:/ - Minor fixes to tokens will be released as patch versions. - Major design changes will be released as minor versions -- _Breaking_ public API changes will be released in a major versions only. +- _Breaking_ public API changes will be released in major versions only. To prevent your site from breaking due to a breaking change or looking dramatically different due to a minor version bump, we recommend the [~](https://docs.npmjs.com/misc/semver#tilde-ranges-123-12-1) comparator when using this package. @@ -182,7 +182,7 @@ Follow the [official guide](https://www.gatsbyjs.org/contributing/setting-up-you git clone https://github.com/gatsbyjs/gatsby.git cd gatsby -# set up the repo,install dependencies for `packages`, and build the latter +# set up the repo, install dependencies for `packages`, and build the latter yarn run bootstrap # make sure tests are passing diff --git a/packages/gatsby-dev-cli/README.md b/packages/gatsby-dev-cli/README.md index 89a05f8e6a3d9..375f077111e59 100644 --- a/packages/gatsby-dev-cli/README.md +++ b/packages/gatsby-dev-cli/README.md @@ -33,7 +33,7 @@ watchers to build Gatsby source code. ## Revert to current packages -If you've recently run `gatsby-dev` your `node_modules` will be out of sync with current published packages. In order to undo this, you can remove the `node_modules` directory or run: +If you've recently run `gatsby-dev` your `node_modules` will be out of sync with currently published packages. In order to undo this, you can remove the `node_modules` directory or run: ```shell git checkout package.json; yarn --force @@ -47,7 +47,7 @@ git checkout package.json; npm install --force **[Demo Video](https://www.youtube.com/watch?v=D0SwX1MSuas)** -More detailed instruction for setting up your Gatsby development environment can +More detailed instructions for setting up your Gatsby development environment can be found [here](https://www.gatsbyjs.org/contributing/how-to-contribute/). ### Other commands @@ -78,4 +78,4 @@ Copy all modules/files in the gatsby source repo in packages/ #### `--force-install` -Disables copying files into node_modules and forces usage of local npm repository. +Disable copying files into node_modules and force usage of local npm repository. diff --git a/packages/gatsby-plugin-gatsby-cloud/README.md b/packages/gatsby-plugin-gatsby-cloud/README.md index 06005903e9b77..51d16411799d8 100644 --- a/packages/gatsby-plugin-gatsby-cloud/README.md +++ b/packages/gatsby-plugin-gatsby-cloud/README.md @@ -129,7 +129,7 @@ An asterix, `*`, will match anything that follows. i.e. `/packages/gatsby-plugin [HSTS Cheatsheet](https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Strict_Transport_Security_Cheat_Sheet.html) -Since this header is an opt-in security enhancement with permanent consequences we don't include it as a default feature but use can use the `allPagesHeaders` to include it. +Since this header is an opt-in security enhancement with permanent consequences we don't include it as a default feature but use the `allPagesHeaders` to include it. ```javascript {