docs: Update docs

Author: Abdalrhman Emad Saad

docs/README.md

@@ -1,7 +1,7 @@
 ---
 home: true
 title: Home
-heroImage: /logo.png
+heroImage: logo.png
 actions:
   - text: Introduction
     link: /introduction

docs/features/header-driven-filter-mode.md

@@ -75,7 +75,7 @@ When `fallback_strategy = 'error'`:
 ### Per-Query Selection
 
 ```php
-Filterable::make(Product::query)->withHeaderDrivenMode();
+Filterable::create()->filter(Product::query())->withHeaderDrivenMode([...]);
 ```
 
 #### Method Reference
@@ -97,18 +97,7 @@ withHeaderDrivenMode(array $config)
 'allowed_engines' => ['dynamic', 'tree']
 ```
 
-## Important Notes
-
-### Closure Engine Limitation
-
-::: warning Warning
-Header-driven mode **cannot** be used with [**Closure Pipeline Engine**](engines/closure) because:
-
-- Closures cannot be serialized in headers
-- Runtime pipeline modifications require code-level changes
-  :::
-
-#### Security Considerations
+## Security Considerations
 
 - Always whitelist allowed engines in production
 - Consider rate limiting header modifications

docs/how-it-works.md

@@ -6,12 +6,12 @@ Each **engine** encapsulates a distinct filtering strategy — allowing you to c
 
 ## Engine Overview
 
-| Engine                                  | Description                                                                                            |
-| --------------------------------------- | ------------------------------------------------------------------------------------------------------ |
-| [`Ruleset`](/engines/ruleset)           | Applies a flat array of key-operator-value pairs. Best for simple APIs or when using query strings.    |
-| [`Invokable`](/engines/dynamic-methods) | Maps each filter key to a method on your filter class. Great for encapsulating filter logic per field. |
-| [`Expression`](/engines/sql-expression) | Global callback to handle raw SQL filtering expressions dynamically.                                   |
-| [`Tree`](/engines/tree-based)           | Supports nested and grouped logical filtering (`AND` / `OR`), ideal for advanced search scenarios.     |
+| Engine                             | Description                                                                                            |
+| ---------------------------------- | ------------------------------------------------------------------------------------------------------ |
+| [`Ruleset`](engines/rule-set)      | Applies a flat array of key-operator-value pairs. Best for simple APIs or when using query strings.    |
+| [`Invokable`](engines/invokable)   | Maps each filter key to a method on your filter class. Great for encapsulating filter logic per field. |
+| [`Expression`](engines/expression) | Flexible and expressive filtering engine designed to handle both flat and deeply nested filters.       |
+| [`Tree`](engines/tree)             | Supports nested and grouped logical filtering (`AND` / `OR`), ideal for advanced search scenarios.     |
 
 ---
 

docs/sanitization.md

@@ -9,13 +9,6 @@ To enable sanitization in your filter class,
 define a `protected $sanitizers` property.
 Each entry in this array maps a **request key** to one or more sanitizer classes.
 
-## Important Note
-
-::: danger Important Node
-The [**Closure Pipeline Engine**](/engines/closure) dose **not** og through any [sanitization](sanitization) or [validation](validation) processes.
-Ensuer that you manually handle input validation and security checks when using closures in filter logic to avoid unexpected behavior or security vulnerabilities.
-:::
-
 ## Basic Example
 
 ```php
@@ -51,11 +44,11 @@ You can apply multiple sanitizers to the same field by using array:
 
 ```php
 protected $sanitizers = [
-    'title' => [
-      TrimSanitizer::class,
-      CapitalizeSanitizer::class
-    ]
-  ];
+  'title' => [
+    TrimSanitizer::class,
+    CapitalizeSanitizer::class
+  ]
+];
 ```
 
 Sanitizers are applied **in the order defined**.