Apply suggestions from code review

Co-authored-by: Diana <[email protected]>

app/_gateway_entities/consumer.md

@@ -46,12 +46,10 @@ faqs:
 
   - q: Can you scope authentication plugins to Consumers?
     a: |
-      No. You can associate Consumers with an auth plugin by configuring credentials - for example, a Consumer with basic
+      No. You can associate Consumers with an auth plugin by configuring credentials. For example, a Consumer with basic
       auth credentials will use the Basic Authentication plugin.
-      But that plugin must be scoped to either a route, service, or globally, so that the Consumer can access it.
+      But that plugin must be scoped to either a Route, Service, or globally, so that the Consumer can access it.
 
-  - q: Are consumers used in Kuma/Mesh?
-    a: No.
 
   - q: Can you manage Consumers with decK?
     a: |

app/plugins/scopes.md

@@ -29,13 +29,11 @@ Each plugin can run globally, or be scoped to some combination of the following:
 Using scopes, you can customize how {{site.base_gateway}} handles functions in your environment, 
 either before a request is sent to your backend services or after it receives a response.
 For example, if you apply a plugin to a single [**Route**](/gateway/entities/route/), 
-that plugin will trigger only on the specific path requests take through your system.
-On the other hand, if you apply the plugin [**globally**](#global-scope), it will 
-run on every request, regardless of any other configuration.
+that plugin will only trigger when a request matches the Route's specific path.
 
 ### Global scope
 
-A global plugin is not associated to any Gateway Service, Route, Consumer, or Consumer Group is 
+A global plugin is not associated to any Service, Route, Consumer, or Consumer Group is 
 considered global, and will be run on every request, regardless of any other configuration.
 
 * In self-managed {{site.ee_product_name}}, the plugin applies to every entity in a given Workspace.