rephrased log processor classificaiton justificaiton

Author: jdv

crowdsec-docs/docs/getting_started/intro.md

@@ -19,9 +19,9 @@ See [Version Matrix](/getting_started/versions_matrix.md) for a list of supporte
 ## Why is my Security Engine classed as a "log processor" within the console?
 
 The `Security Engine` comes compiled with a number of core components that can be enabled or disabled at runtime.
+One of these features is called the **"LAPI"** (Local API) and other one is the **"log processor"**.  
 
-One of these features is called the "LAPI" (Local API). If this feature is disabled at runtime, the Security Engine will be classed as a "log processor" within the console as it will only be able to process logs and forward the alerts to the local API you define in the configuration.
+A single `Security Engine` can run in autonomous mode where it handles reading logs (or requests) and processing them as well as handling alerts and other task on its own **"LAPI"**.   
+For **scaling** or **perimeter segmentation** reasons you might want to have a distributed setup. In that case multiple `Security Engines` process logs and send alerts to a central one's **"LAPI"**. In that distributed case you'll see **"log processors"** attached to the central `Security Engines` in the console UI.   
 
 Read more about the [Log Processor](log_processor/intro.mdx) and the [Local API](local_api/intro.md).
-
-Most commonly this is the case when you are running in a distributed setup, where you have a central server that is running the LAPI and a number of remote servers that are running the "Log processors".

crowdsec-docs/unversioned/integrations/genericvendor.mdx

@@ -1,23 +1,23 @@
 ---
 id: genericfirewall
-title: Generic Firewall
+title: Generic Firewall (Raw IP-list)
 ---
 import ThemedImage from "@theme/ThemedImage";
 import useBaseUrl from "@docusaurus/useBaseUrl";
 
-The CrowdSec Generic Firewall integration allows you to block malicious IPs in your Firewall. This guide will walk you through the steps to integrate CrowdSec blocklists with your Firewall.
+The CrowdSec Raw IP List (or Generic Firewall) integration allows you to block malicious IPs in your Firewall. This guide will walk you through the steps to integrate CrowdSec blocklists with your Firewall.
 
 ### Prerequisites
 
-Before you begin, please ensure your Generic Firewall device supports ingesting blocklists. If you are unsure, please refer to the Generic Firewall documentation or contact Generic Firewall support.
+Before you begin, please ensure your device supports ingesting the raw IP format (one ip per line).
 
 ### Steps
 
 We will presume you followed the [Getting Started](integrations/intro.mdx) guide and have created an account on the CrowdSec Console.
 
 Once you are authenticated, you can proceed to the Blocklist tab located on the top menu bar, from there you can select the Integrations sub menu.
 
-Once the page has loaded, you can click the "Connect" button under the Generic Firewall logo.
+Once the page has loaded, you can click the "Connect" button under the Raw IP List (or Generic Firewall) logo.
 
 <ThemedImage
     alt="Generic Firewall Integration Card"