From c34721148786b0a3664e25bf003ad53f90907b7f Mon Sep 17 00:00:00 2001
From: q1800 <95879668+q1800@users.noreply.github.com>
Date: Sun, 6 Feb 2022 16:25:07 -0600
Subject: [PATCH] Paragraph fixes as per feedback

---
 Procedural-cosmetic-filters.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Procedural-cosmetic-filters.md b/Procedural-cosmetic-filters.md
index 06f488b..0cea37a 100644
--- a/Procedural-cosmetic-filters.md
+++ b/Procedural-cosmetic-filters.md
@@ -8,9 +8,9 @@ The initial implementation was revised to allow chained/recursive use of the pro
 
 Only use procedural cosmetic filters when plain CSS selectors won't work.
 
-Standard cosmetic filters are _declarative_, i.e. when used as a selector in a CSS rule and handled by browsers through `style` tag elements.
+Regular cosmetic filters are _declarative_, i.e., they are used as a selector in a CSS rule and handled by browsers through `style` tag elements.
 
-_Procedural_ means JavaScript code will find DOM elements that it must hide. A procedural cosmetic filter uses a cosmetic filter _operator_. That will tell uBO how to find/filter DOM elements to find which DOM elements to target.
+_Procedural_ means JavaScript code will find DOM elements that it must hide. A procedural cosmetic filter uses a filter _operator_ that will tell uBO how to find/filter DOM elements to find which DOM elements to target.
 
 #### Important: