diff --git a/client/pwa/src/db.ts b/client/pwa/src/db.ts
index eb8031511e32..3a2696c9fbbf 100644
--- a/client/pwa/src/db.ts
+++ b/client/pwa/src/db.ts
@@ -54,7 +54,7 @@ export interface ContentStatus {
 
 export class MDNOfflineDB extends Dexie {
   // Declare implicit table properties.
-  // (just to inform Typescript. Instanciated by Dexie in stores() method)
+  // (just to inform Typescript. Instantiated by Dexie in stores() method)
   whoami!: Dexie.Table<Whoami, number>; // number = type of the primkey
   contentStatusHistory!: Dexie.Table<ContentStatus, number>;
 
diff --git a/client/src/settings/db.ts b/client/src/settings/db.ts
index eb8031511e32..3a2696c9fbbf 100644
--- a/client/src/settings/db.ts
+++ b/client/src/settings/db.ts
@@ -54,7 +54,7 @@ export interface ContentStatus {
 
 export class MDNOfflineDB extends Dexie {
   // Declare implicit table properties.
-  // (just to inform Typescript. Instanciated by Dexie in stores() method)
+  // (just to inform Typescript. Instantiated by Dexie in stores() method)
   whoami!: Dexie.Table<Whoami, number>; // number = type of the primkey
   contentStatusHistory!: Dexie.Table<ContentStatus, number>;
 
diff --git a/client/src/ui/README.md b/client/src/ui/README.md
index 757415721dbc..f6e30cf268fc 100644
--- a/client/src/ui/README.md
+++ b/client/src/ui/README.md
@@ -46,7 +46,7 @@ is now manually kept in sync. In future we hope to automate this process.
 
 When we embarked on the redesign, the idea was to use
 [mdn-minimalist](https://github.com/mdn/mdn-minimalist) as the base and override
-what is different. In the end this prooved more cumbersome than we had hoped.
+what is different. In the end this proved more cumbersome than we had hoped.
 This means that either the `theme` folder will be removed in future or, the
 `client/src/ui/minimalist` folder.
 
diff --git a/copy/plus/features/collections.md b/copy/plus/features/collections.md
index 945eda43cec2..50b301f9891f 100644
--- a/copy/plus/features/collections.md
+++ b/copy/plus/features/collections.md
@@ -8,7 +8,7 @@ title: Collections
 >
 > Collections allow you to save MDN articles and share your library across
 > devices. We also automatically save for you the pages you visit most
-> frequently. They wil help you find what you need quicker by showing first in
+> frequently. They will help you find what you need quicker by showing first in
 > your search results when looking for a relevant topic and you’ll be able to
 > curate the lists to your liking.
 
diff --git a/deployer/src/deployer/search/models.py b/deployer/src/deployer/search/models.py
index c68e0328821c..34b0a22b23e6 100644
--- a/deployer/src/deployer/search/models.py
+++ b/deployer/src/deployer/search/models.py
@@ -45,7 +45,7 @@
     "yari_word_delimiter",
     type="word_delimiter",
     # When it splits on 'Array.prototype.forEach' it first of all becomes
-    # 'array', 'protoype', and 'foreach'. But also, still includes
+    # 'array', 'prototype', and 'foreach'. But also, still includes
     # as a word 'array.prototype.foreach'.
     # With this configuration we'll get good matches for both
     # 'array foreach' and if people type the full 'array.prototype.foreach'.
diff --git a/kumascript/macros/SVGElement.ejs b/kumascript/macros/SVGElement.ejs
index 247dcc87c70e..30302bf6bf51 100644
--- a/kumascript/macros/SVGElement.ejs
+++ b/kumascript/macros/SVGElement.ejs
@@ -13,7 +13,7 @@ const term = $0;
 //
 // you *want* flaws to bubble up. E.g. a typo like `{{SVGElement("imge")}}`
 // But this macro is called from another macro, like `SVGRef` then, all those
-// macro calls' flaws should be "supressed" because it's a problem with the that
+// macro calls' flaws should be "suppressed" because it's a problem with the that
 // sidebar macro, not the page the current user is viewing/working on.
 // So if this 2nd argument is passed, it will potentially ignore the macro flaw.
 const ignoreFlawMacro = $1;