diff --git a/cypress/integration/word-list/index.spec.ts b/cypress/integration/word-list/index.spec.ts
index e48466450d..e9b758c079 100644
--- a/cypress/integration/word-list/index.spec.ts
+++ b/cypress/integration/word-list/index.spec.ts
@@ -15,7 +15,7 @@ describe("Word list with filters", function () {
   it("should filter the table when a filter string is provided", () => {
     cy.get('[data-cy="word-list-table"] tbody tr').as("table-rows");
     cy.get('[data-cy="word-list-filter-input"]').click().type("ad");
-    cy.get("@table-rows").its("length").should("eq", 4);
+    cy.get("@table-rows").its("length").should("eq", 6);
   });
 
   it("should show empty state when nothing returned", () => {
diff --git a/packages/paste-website/src/data/word-list.json b/packages/paste-website/src/data/word-list.json
index ecf7f4916c..cf424aec72 100644
--- a/packages/paste-website/src/data/word-list.json
+++ b/packages/paste-website/src/data/word-list.json
@@ -27,6 +27,7 @@
   "disabled": "Use for conveying a status where the entity or feature is preventing a broader feature to function. \n This is a more technical word that could be perceived as jargon, so consider content best practices (simple words!) and your audience. Use the less technical term 'off' if it won't hinder comprehension or accuracy, or if you're writing for a less technical audience (like marketers).",
   "dismiss": "Avoid. Use 'close' instead.",
   "done": "Avoid. Use 'finish' or 'close' instead, depending on the use case. Actions more closely describe what will happen when the user clicks the button.",
+  "downgrade": "Avoid using this.",
   "download": "Use as a call to action when a user need to copy data from Twilio to a computer system",
   "duplicate": "Use when allowing user to create a replica of an existing item.",
   "easy / easily": "Avoid. This contains a value judgement and can make users feel dumb if it doesn't feel easy to them.",
@@ -75,6 +76,8 @@
   "success/successfully": "Avoid because it is almost always redundant. For example, instead of saying 'Your account was sucessfully created.' we can say 'Your account was created.'",
   "team member": "Don't use 'teammate' or 'team mate'",
   "thank you": "Don't use when users completed something they'd do otherwise. Only use when we've asked them to do something extremely inconvenient.",
+  "update": "Use when you are moving to a newer version (most likely in the context of a minor version). For example, 'Update to the latest version of Flex', 'Auto updates for Flex'.",
+  "upgrade": "Reserve for bigger updates that will involve a lot of work. Use the term appropriate to the amount of work involved. Consider this spectrum: [Very little work, one click] Update > Upgrade > Migrate [A lot of work, several steps]",
   "upload": "Use as a call to action when a user needs to copy data of the same format from a computer system into a Twilio product",
   "utilize": "Avoid. Use 'use' instead.",
   "us": "Using 'us' when referring to Twilio is okay for in-product content. Avoid in technical documentation.",