From 49b2f01821b572e8d31ed2807dacffa16d0ce251 Mon Sep 17 00:00:00 2001
From: CodeShell <122738806+CodeShellDev@users.noreply.github.com>
Date: Sat, 24 Jan 2026 19:56:59 +0100
Subject: [PATCH 1/2] added mention of regex in endpoints

---
 docs/configuration/endpoints.md      | 9 +++++++--
 docs/configuration/field-policies.md | 2 +-
 2 files changed, 8 insertions(+), 3 deletions(-)

diff --git a/docs/configuration/endpoints.md b/docs/configuration/endpoints.md
index a07b0c4b..9969d27b 100644
--- a/docs/configuration/endpoints.md
+++ b/docs/configuration/endpoints.md
@@ -20,8 +20,13 @@ because of security concerns the following endpoints are blocked:
 
 ## Customize
 
+> [!IMPORTANT]
+>
+> 1. Matching uses [regex](https://regex101.com)
+> 2. On error [glob-style patterns](https://www.gnu.org/software/bash/manual/html_node/Pattern-Matching.html) are used instead
+
 > [!NOTE]
-> Matching uses [glob-like patterns](https://www.gnu.org/software/bash/manual/html_node/Pattern-Matching.html):
+> Quick reminder, how [glob-style patterns](https://www.gnu.org/software/bash/manual/html_node/Pattern-Matching.html) work:
 >
 > - `*` matches any sequence of characters
 > - `?` matches a single character
@@ -51,7 +56,7 @@ By default, adding an endpoint explicitly allows access to it, use `!` to block
 | ---------- | -------------- | ----------------------------------------- |
 | `/v2/send` | —              | **Only** `/v2/send` allowed               |
 | —          | `!/v1/receive` | **All** allowed, **except** `/v1/receive` |
-| `/v2/send` | `!/v2/*`       | **Only** `/v2/send` allowed               |
+| `/v2/send` | `!/v2/.*`      | **Only** `/v2/send` allowed               |
 
 ### Rules
 
diff --git a/docs/configuration/field-policies.md b/docs/configuration/field-policies.md
index 39f2aee6..a3538257 100644
--- a/docs/configuration/field-policies.md
+++ b/docs/configuration/field-policies.md
@@ -24,7 +24,7 @@ settings:
 Set the wanted action on encounter, available options are `block` and `allow`.
 
 > [!TIP]
-> String fields always try to use regex matching, on compile error exact match is used as fallback
+> String fields always try to use [regex matching](https://regex101.com), on compile error exact match is used as fallback
 
 > [!NOTE]
 > Supported [placeholder types](../usage/advanced#placeholders):

From 8e73594a024808c89c501acb94aa67933ae39c7c Mon Sep 17 00:00:00 2001
From: CodeShell <122738806+CodeShellDev@users.noreply.github.com>
Date: Sat, 24 Jan 2026 19:57:46 +0100
Subject: [PATCH 2/2] change Note to Tip

---
 docs/configuration/endpoints.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/configuration/endpoints.md b/docs/configuration/endpoints.md
index 9969d27b..2a0c0531 100644
--- a/docs/configuration/endpoints.md
+++ b/docs/configuration/endpoints.md
@@ -25,7 +25,7 @@ because of security concerns the following endpoints are blocked:
 > 1. Matching uses [regex](https://regex101.com)
 > 2. On error [glob-style patterns](https://www.gnu.org/software/bash/manual/html_node/Pattern-Matching.html) are used instead
 
-> [!NOTE]
+> [!TIP]
 > Quick reminder, how [glob-style patterns](https://www.gnu.org/software/bash/manual/html_node/Pattern-Matching.html) work:
 >
 > - `*` matches any sequence of characters