diff --git a/content/posts/layered-content-blocking.gmi b/content/posts/layered-content-blocking.gmi
index 1169653..589403f 100644
--- a/content/posts/layered-content-blocking.gmi
+++ b/content/posts/layered-content-blocking.gmi
@@ -18,7 +18,7 @@ Hostname or IP-based based network filtering is the least capable but most relia
 
 ## Context: extension permissions systems
 
-Firefox allows extensions to declare their own permissions. Extensions decide which sites they can run on and when, and which permissions are optional.
+Firefox allows extensions to declare their own permissions. Extensions decide which sites they can run on and when, with required and optional permissions.
 
 Chromium has a similar system with additional functionality: users can choose to enable an extension only when clicked, only for a certain site, or for all sites globally. Safari takes this a step further and also offers the choice to enable an extension for a limited time period (one day).
 
diff --git a/content/posts/layered-content-blocking.md b/content/posts/layered-content-blocking.md
index 3f8474b..82b2f6c 100644
--- a/content/posts/layered-content-blocking.md
+++ b/content/posts/layered-content-blocking.md
@@ -25,7 +25,7 @@ Hostname or IP-based based network filtering is the least capable but most relia
 Context: extension permissions systems
 --------------------------------------
 
-Firefox allows extensions to declare their own permissions. Extensions decide which sites they can run on and when, and which permissions are optional.
+Firefox allows extensions to declare their own permissions. Extensions decide which sites they can run on and when, with required and optional permissions.
 
 Chromium has a similar system with additional functionality: users can choose to enable an extension only when clicked, only for a certain site, or for all sites globally. Safari takes this a step further and also offers the choice to enable an extension for a limited time period (one day).