diff --git a/ai-for-service/apis/searchai/chunk-apis.mdx b/ai-for-service/apis/searchai/chunk-apis.mdx
index f9be49b8..1f6b1f7c 100644
--- a/ai-for-service/apis/searchai/chunk-apis.mdx
+++ b/ai-for-service/apis/searchai/chunk-apis.mdx
@@ -150,7 +150,7 @@ This API enables targeted deletion of indexed content without a full re-index. P
 | Field | Value |
 |---|---|
 | **Method** | POST |
-| **URL** | `/api/public/bot/{AppId}/search/delete-chunks-by-cond` |
+| **URL** | `/api/public/bot/{AppId}/search/deleteChunksById` |
 | **Content-Type** | `application/json` |
 | **Authentication** | `auth: <JWT Token>` |
 | **API Scope** | Chunk Management |
@@ -172,7 +172,7 @@ This API enables targeted deletion of indexed content without a full re-index. P
 **Example: Delete by chunkId**
 
 ```bash
-curl --location 'https://<HOST>/api/public/bot/<BOT_ID>/search/delete-chunks-by-cond' \
+curl --location 'https://<HOST>/api/public/bot/<BOT_ID>/search/deleteChunksById' \
 --header 'auth: <JWT_TOKEN>' \
 --header 'Content-Type: application/json' \
 --data '{
@@ -190,6 +190,7 @@ curl --location 'https://<HOST>/api/public/bot/<BOT_ID>/search/delete-chunks-by-
 | `totalRequested` | Number of chunks requested for deletion. |
 | `totalDeleted` | Number of chunks successfully deleted. |
 | `totalNotFound` | Number of chunks that were not found. |
+|`notFoundChunkIds`| Array of chunk Ids that were not found|
 
 #### Sample Response
 
@@ -199,7 +200,8 @@ curl --location 'https://<HOST>/api/public/bot/<BOT_ID>/search/delete-chunks-by-
   "Data": {
     "totalRequested": 4,
     "totalDeleted": 4,
-    "totalNotFound": 0
+    "totalNotFound": 0,
+    "notFoundChunkIds": []
   }
 }
 ```
diff --git a/ai-for-service/searchai/agentic-rag-and-business-rules.mdx b/ai-for-service/searchai/agentic-rag-and-business-rules.mdx
index 7aa0e9b4..85e32f6d 100644
--- a/ai-for-service/searchai/agentic-rag-and-business-rules.mdx
+++ b/ai-for-service/searchai/agentic-rag-and-business-rules.mdx
@@ -67,10 +67,6 @@ Example:
 - Extracted fields: Assignee, Status, Priority
 - Action: Filter applied (no boost needed)
 
-### Supported Models
-
-Currently, only **OpenAI 4.0** and **Azure OpenAI 4.0** models are supported for Agentic RAG.
-
 ### Enabling Agentic RAG
 
 **Prerequisites**
diff --git a/ai-for-service/searchai/connectors/youtube.mdx b/ai-for-service/searchai/connectors/youtube.mdx
index 10d0ef17..a89f3b69 100644
--- a/ai-for-service/searchai/connectors/youtube.mdx
+++ b/ai-for-service/searchai/connectors/youtube.mdx
@@ -143,7 +143,7 @@ Once the sync is complete, go to the **Content** tab to review the ingested cont
 The system converts each synced video into a single Markdown document. It extracts and indexes the following key fields:
 
 - `title` - The video title.
-- `content` - The full transcript organized by chapters (if available) with timestamps, plus the first 2,000 characters of the video description.
+- `content` - The full transcript organized by chapters (if available) with timestamps.
 - `doc_id` - A unique identifier for the ingested video document, derived from the YouTube video ID.
 - `doc_source_type` - Identifies the source as a YouTube video.
 - `doc_created_on` / `doc_updated_on` - Timestamp of video publishing and last update.
@@ -165,7 +165,7 @@ Each ingested video document follows this structured layout:
 
 ## Description
 
-<First 2,000 characters of the video description>
+<Description>
 
 ## Chapter Title 1 (0:00)
 
@@ -191,7 +191,7 @@ The connector fetches video captions or transcripts using the YouTube Captions A
 | 4th      | Auto-generated captions in any language     |
 
 - If a video has no captions at all, it's still synced - the video metadata and description are indexed without a transcript.
-- Chapter markers in the video description (for example: `0:00 Introduction`, `5:30 Setup`) are automatically detected and used to organize the transcript into sections.
+- Chapter markers in the video description (for example: `0:00 Introduction`, `5:30 Setup`) are automatically detected and used to organize the transcript into sections. This affects only the organization of content within each chunk. Chunks are still created using [token-based](/ai-for-service/searchai#chunking-strategies) splitting, regardless of chapter boundaries.
 
 ## API Quota