diff --git a/docs/manifest.json b/docs/manifest.json
index 8f267e79ef4fe..a2facf0b1d14a 100644
--- a/docs/manifest.json
+++ b/docs/manifest.json
@@ -517,7 +517,7 @@
 	},
 	{
 		"title": "Understanding global state, local context and derived state",
-		"slug": "undestanding-global-state-local-context-and-derived-state",
+		"slug": "understanding-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",
 		"parent": "core-concepts"
 	},
diff --git a/docs/reference-guides/interactivity-api/core-concepts/server-side-rendering.md b/docs/reference-guides/interactivity-api/core-concepts/server-side-rendering.md
index 075c2cb977bdf..30deb39d92718 100644
--- a/docs/reference-guides/interactivity-api/core-concepts/server-side-rendering.md
+++ b/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
 
diff --git a/docs/reference-guides/interactivity-api/core-concepts/undestanding-global-state-local-context-and-derived-state.md b/docs/reference-guides/interactivity-api/core-concepts/understanding-global-state-local-context-and-derived-state.md
similarity index 100%
rename from docs/reference-guides/interactivity-api/core-concepts/undestanding-global-state-local-context-and-derived-state.md
rename to docs/reference-guides/interactivity-api/core-concepts/understanding-global-state-local-context-and-derived-state.md
diff --git a/docs/reference-guides/interactivity-api/core-concepts/using-typescript.md b/docs/reference-guides/interactivity-api/core-concepts/using-typescript.md
index ed0bdd88211d1..10e69aa844055 100644
--- a/docs/reference-guides/interactivity-api/core-concepts/using-typescript.md
+++ b/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.
 
diff --git a/packages/edit-site/src/components/layout/style.scss b/packages/edit-site/src/components/layout/style.scss
index 8d44015d52967..831c73382731c 100644
--- a/packages/edit-site/src/components/layout/style.scss
+++ b/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 {
diff --git a/packages/element/src/test/create-interpolate-element.js b/packages/element/src/test/create-interpolate-element.js
index 17b1cc9b3ab2c..d459a19424c21 100644
--- a/packages/element/src/test/create-interpolate-element.js
+++ b/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,
diff --git a/packages/interactivity/src/utils.ts b/packages/interactivity/src/utils.ts
index ab6b0074727ee..ef97d16cb089e 100644
--- a/packages/interactivity/src/utils.ts
+++ b/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.