Fix typos, round two

docs/manifest.json

@@ -517,8 +517,8 @@
 	},
 	{
 		"title": "Understanding global state, local context and derived state",
-		"slug": "undestanding-global-state-local-context-and-derived-state",
-		"markdown_source": "../docs/reference-guides/interactivity-api/core-concepts/undestanding-global-state-local-context-and-derived-state.md",
+		"slug": "understanding-global-state-local-context-and-derived-state",
+		"markdown_source": "../docs/reference-guides/interactivity-api/core-concepts/understanding-global-state-local-context-and-derived-state.md",
 		"parent": "core-concepts"
 	},
 	{

docs/reference-guides/interactivity-api/core-concepts/README.md

@@ -4,7 +4,7 @@ This section provides some guides on important concepts and mental models relate
 
 1. **[The Reactive and Declarative mindset](/docs/reference-guides/interactivity-api/core-concepts/the-reactive-and-declarative-mindset.md):** This guide covers core concepts of reactivity and declarativeness, providing a foundation for effective use of the Interactivity API.
 
-2. **[Understanding global state, local context and derived state](/docs/reference-guides/interactivity-api/core-concepts/undestanding-global-state-local-context-and-derived-state.md):** The guide explains how to effectively use global state, local context, and derived state within the Interactivity API emphasizing the importance of choosing the appropriate state management technique based on the scope and requirements of your data.
+2. **[Understanding global state, local context and derived state](/docs/reference-guides/interactivity-api/core-concepts/understanding-global-state-local-context-and-derived-state.md):** The guide explains how to effectively use global state, local context, and derived state within the Interactivity API emphasizing the importance of choosing the appropriate state management technique based on the scope and requirements of your data.
 
 3. **[Server-side rendering: Processing directives on the server](/docs/reference-guides/interactivity-api/core-concepts/server-side-rendering.md):** The Interactivity API allows WordPress to use server-side rendering to create interactive and state-aware HTML, smoothly connected with client-side features while maintaining performance and SEO benefits.
 

docs/reference-guides/interactivity-api/core-concepts/server-side-rendering.md

@@ -175,7 +175,7 @@ store( 'myFruitPlugin', {
 
 The derived state, regardless of whether it derives from the global state, local context, or both, can also be processed on the server by the Server Directive Processing.
 
-_Please, visit the [Understanding global state, local context and derived state](./undestanding-global-state-local-context-and-derived-state.md) guide to learn more about how derived state works in the Interactivity API._
+_Please, visit the [Understanding global state, local context and derived state](./understanding-global-state-local-context-and-derived-state.md) guide to learn more about how derived state works in the Interactivity API._
 
 ### Derived state that can be defined statically
 

docs/reference-guides/interactivity-api/core-concepts/the-reactive-and-declarative-mindset.md

@@ -165,7 +165,7 @@ The Interactivity API uses a fine-grained reactivity system. Here's how it works
     - **Local context**: This is local data that is specific to a particular element and its children.
     - **Derived State**: In addition to basic state properties, you can define computed properties that automatically update when their dependencies change.
 
-    _Please, visit the [Understanding global state, local context and derived state](/docs/reference-guides/interactivity-api/core-concepts/undestanding-global-state-local-context-and-derived-state.md) guide to learn more about how to work with the different types of reactive state in the Interactivity API._
+    _Please, visit the [Understanding global state, local context and derived state](/docs/reference-guides/interactivity-api/core-concepts/understanding-global-state-local-context-and-derived-state.md) guide to learn more about how to work with the different types of reactive state in the Interactivity API._
 
 2. **Actions**: These are functions, usually triggered by event handlers, that mutate the global state or local context.
 

docs/reference-guides/interactivity-api/core-concepts/using-typescript.md

@@ -269,7 +269,7 @@ That's it! Now you can access the context properties with the correct types.
 
 The derived state is data that is calculated based on the global state or local context. In the client store definition, it is defined using a getter in the `state` object.
 
-_Please, visit the [Understanding global state, local context and derived state](./undestanding-global-state-local-context-and-derived-state.md) guide to learn more about how derived state works in the Interactivity API._
+_Please, visit the [Understanding global state, local context and derived state](./understanding-global-state-local-context-and-derived-state.md) guide to learn more about how derived state works in the Interactivity API._
 
 Following our previous example, let's create a derived state that is the double of our counter.
 

docs/toc.json

@@ -213,7 +213,7 @@
 								"docs/reference-guides/interactivity-api/core-concepts/the-reactive-and-declarative-mindset.md": []
 							},
 							{
-								"docs/reference-guides/interactivity-api/core-concepts/undestanding-global-state-local-context-and-derived-state.md": []
+								"docs/reference-guides/interactivity-api/core-concepts/understanding-global-state-local-context-and-derived-state.md": []
 							},
 							{
 								"docs/reference-guides/interactivity-api/core-concepts/server-side-rendering.md": []

packages/block-editor/src/components/inserter-draggable-blocks/index.js

@@ -61,7 +61,7 @@ const InserterDraggableBlocks = ( {
 					const type = `wp-block:${ block.name }`;
 					// This will fill in the dataTransfer.types array so that
 					// the drop zone can check if the draggable is eligible.
-					// Unfortuantely, on drag start, we don't have access to the
+					// Unfortunately, on drag start, we don't have access to the
 					// actual data, only the data keys/types.
 					event.dataTransfer.items.add( '', type );
 				}

packages/components/src/menu/types.ts

@@ -258,7 +258,7 @@ export interface MenuCheckboxItemProps {
 	 * The checked state of the checkbox menu item when it is initially rendered.
 	 * Use when not wanting to control its checked state.
 	 *
-	 * Note: this prop will be overriden by the `checked` prop, if it is defined.
+	 * Note: this prop will be overridden by the `checked` prop, if it is defined.
 	 */
 	defaultChecked?: Ariakit.MenuItemCheckboxProps[ 'defaultChecked' ];
 	/**
@@ -321,7 +321,7 @@ export interface MenuRadioItemProps {
 	 * The checked state of the radio menu item when it is initially rendered.
 	 * Use when not wanting to control its checked state.
 	 *
-	 * Note: this prop will be overriden by the `checked` prop, if it is defined.
+	 * Note: this prop will be overridden by the `checked` prop, if it is defined.
 	 */
 	defaultChecked?: Ariakit.MenuItemRadioProps[ 'defaultChecked' ];
 	/**

packages/edit-site/src/components/layout/style.scss

@@ -139,7 +139,7 @@
 	}
 }
 
-// This shouldn't be necessary (we should have a way to say that a skeletton is relative
+// This shouldn't be necessary (we should have a way to say that a skeleton is relative
 .edit-site-layout__mobile .interface-interface-skeleton,
 .edit-site-layout__canvas .interface-interface-skeleton,
 .edit-site-template-pages-preview .interface-interface-skeleton {

packages/element/src/test/create-interpolate-element.js

@@ -217,7 +217,7 @@ describe( 'createInterpolateElement', () => {
 		expect( container ).toContainHTML( '<strong>string!</strong>' );
 		expect( container ).not.toContainHTML( '<em>' );
 	} );
-	it( 'handles parsing emojii correctly', () => {
+	it( 'handles parsing emoji correctly', () => {
 		const testString = '👳‍♀️<icon>🚨🤷‍♂️⛈️fully</icon> here';
 		const expectedElement = createElement(
 			Fragment,

packages/interactivity/src/utils.ts

@@ -91,7 +91,7 @@ function createFlusher( compute: () => void, notify: () => void ): Flusher {
 /**
  * Custom hook that executes a callback function whenever a signal is triggered.
  * Version of `useSignalEffect` with a `useEffect`-like execution. This hook
- * implementation comes from this PR, but we added short-cirtuiting to avoid
+ * implementation comes from this PR, but we added short-circuiting to avoid
  * infinite loops: https://github.com/preactjs/signals/pull/290
  *
  * @param callback The callback function to be executed.

test/e2e/specs/site-editor/site-editor-inserter.spec.js

@@ -82,7 +82,7 @@ test.describe( 'Site Editor Inserter', () => {
 			},
 		} );
 
-		test( 'should intialize correct active tab based on zoom level', async ( {
+		test( 'should initialize correct active tab based on zoom level', async ( {
 			InserterUtils,
 			ZoomUtils,
 		} ) => {