From 91d9d2168e92d8e97187575344558982e9e233f9 Mon Sep 17 00:00:00 2001
From: AnastasiaTWW <61460069+AnastasiaTWW@users.noreply.github.com>
Date: Tue, 29 Jul 2025 13:33:42 +0400
Subject: [PATCH 1/2] add the manual trigger for docs build in actions

---
 .github/workflows/documentation.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.github/workflows/documentation.yml b/.github/workflows/documentation.yml
index a14dd508..18d6dcef 100644
--- a/.github/workflows/documentation.yml
+++ b/.github/workflows/documentation.yml
@@ -5,6 +5,7 @@ on:
       - main
     paths:
       - 'docs/**'
+  workflow_dispatch:
 
 permissions:
   contents: write

From a7a745da72ddab9c5de2fa32d267934cf0ee6070 Mon Sep 17 00:00:00 2001
From: AnastasiaTWW <61460069+AnastasiaTWW@users.noreply.github.com>
Date: Tue, 29 Jul 2025 13:35:19 +0400
Subject: [PATCH 2/2] trigger docs deploy

---
 docs/configuration-guides/denylist-leaked-tokens.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/configuration-guides/denylist-leaked-tokens.md b/docs/configuration-guides/denylist-leaked-tokens.md
index 8bdb9e9d..b7ec9bc0 100644
--- a/docs/configuration-guides/denylist-leaked-tokens.md
+++ b/docs/configuration-guides/denylist-leaked-tokens.md
@@ -8,7 +8,7 @@ For REST API, should any of the flagged tokens surface in a request, the API Fir
 
 To enable the denylist feature:
 
-1. Draft a .txt file with the compromised tokens. Each token should be on a new line. Here is an example:
+1. Draft a `.txt` file with the compromised tokens. Each token should be on a new line. Here is an example:
 
     ```txt
     eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzb21lIjoicGF5bG9hZDk5OTk5ODIifQ.CUq8iJ_LUzQMfDTvArpz6jUyK0Qyn7jZ9WCqE0xKTCA