Docs: Fix some types (#43175)

WordPress · Aug 12, 2022 · 9a4b95e · 9a4b95e
1 parent 10cacc3
commit 9a4b95e
Show file tree

Hide file tree

Showing 5 changed files with 5 additions and 5 deletions.
diff --git a/docs/contributors/code/getting-started-with-code-contribution.md b/docs/contributors/code/getting-started-with-code-contribution.md
@@ -71,7 +71,7 @@ To stop the running environment:
 npm run wp-env stop
 ```
 
-If everyting went well, you should see the following message in your terminal:
+If everything went well, you should see the following message in your terminal:
 
 ```bash
 WordPress development site started at http://localhost:8888/

diff --git a/docs/explanations/architecture/performance.md b/docs/explanations/architecture/performance.md
@@ -26,7 +26,7 @@ Based on the idea that **when editing a given block, it is very rare that an upd
 
 ## The performance benchmark job
 
-A tool to compare performance accross multiple branches/tags/commits is provided. You can run it locally like so: `./bin/plugin/cli.js perf [branches]`, example:
+A tool to compare performance across multiple branches/tags/commits is provided. You can run it locally like so: `./bin/plugin/cli.js perf [branches]`, example:
 
 ```
 ./bin/plugin/cli.js perf trunk v8.1.0 v8.0.0

diff --git a/docs/explanations/architecture/styles.md b/docs/explanations/architecture/styles.md
@@ -464,7 +464,7 @@ In addition to the CSS Custom Properties, all presets but duotone generate CSS c
 /* vivid-red */
 .has-vivid-red-color { color: var(--wp--preset--color--vivid-red) !important; }
 .has-vivid-red-background-color { background-color: var(--wp--preset--color--vivid-red) !important; }
-.has-vivid-red-bordfer-color { border-color: var(--wp--preset--color--vivid-red) !important; }
+.has-vivid-red-border-color { border-color: var(--wp--preset--color--vivid-red) !important; }
 
 /* foreground */
 .has-foreground-color { color: var(--wp--preset--color--foreground) !important; }

diff --git a/docs/how-to-guides/platform/README.md b/docs/how-to-guides/platform/README.md
@@ -49,7 +49,7 @@ You can then add a scripts section to your package.json file, for example:
 	}
 ```
 
-You can then use `npm run build` to build your project with all the default webpack settings already configured, likewise for formating and linting. The `start` command is used for development mode. See [the scripts package](https://www.npmjs.com/package/@wordpress/scripts) for full documentation.
+You can then use `npm run build` to build your project with all the default webpack settings already configured, likewise for formatting and linting. The `start` command is used for development mode. See [the scripts package](https://www.npmjs.com/package/@wordpress/scripts) for full documentation.
 
 You can also play with the [Gutenberg Example #03](https://github.com/WordPress/gutenberg-examples/tree/HEAD/03-editable-esnext) for a complete setup using the wp-scripts package.
 

diff --git a/docs/how-to-guides/platform/custom-block-editor/tutorial.md b/docs/how-to-guides/platform/custom-block-editor/tutorial.md
@@ -519,7 +519,7 @@ And with that we have covered the render of our custom `<BlockEditor>`!
 ## Block Persistence
 
 We've come a long way on our journey to create a custom block editor. But there is
-one major area left to touch upon - Block persistance; that is the act of having our
+one major area left to touch upon - Block persistence; that is the act of having our
 Blocks saved and **available _between_ page refreshes**.
 
 ![alt text](https://wordpress.org/gutenberg/files/2020/03/block-persistance.gif 'Screencapture showing added Blocks being restored between page refreshes.')