Docs: Updated Title chunker references (#14483)

### What problem does this PR solve?

Updated Title chunker references

### Type of change

- [x] Documentation Update

web/src/locales/en.ts

@@ -1510,16 +1510,16 @@ Example: Virtual Hosted Style`,
         author: 'Author',
         sectionTitle: 'Section title',
       },
-      includeHeadingContent: 'Include heading content',
+      includeHeadingContent: 'Separate parent-heading content',
       includeHeadingContentTip:
-        'When enabled, content directly under a heading is kept as its own chunk. Child chunks keep only the heading path.',
+        'When enabled, chunks include only their heading path and content; content immediately following a parent heading is kept as a separate chunk.',
       rootAsHeading: 'Set first chunk as global context',
       rootAsHeadingTip:
-        'Treats the initial split as a global heading to maintain consistent context across the document hierarchy. Ideal for resumes where the first section identifies the subject.',
-      hierarchyTip: `Build a heading tree and produce self-contained chunks, each carrying its full ancestor heading path (e.g. Part 1 › Chapter 3 › Section 2 + body text).\n
-Best for: Documents with independent, structurally significant sections — such as legal statutes, regulations, contracts, and technical specifications — where each chunk must be identifiable by its structural position even without surrounding context.`,
-      groupTip: `Split the document flat at a chosen heading level and automatically merge adjacent small sections to preserve content continuity. No parent-heading path is injected.\n
-Best for: Documents with flowing, contextually connected content — such as books, manuals, reports, and articles — where adjacent paragraphs should stay together to maintain narrative coherence.`,
+        'Treats the first split as a global heading to maintain consistent context across the document hierarchy. Ideal for resumes where the first section identifies the subject.',
+      hierarchyTip: `Construct a heading tree and produce self-contained chunks, each carrying its full ancestral path (e.g. Part 1 › Chapter 3 › Section 2 + body text).\n
+Best for: Highly structured texts — such as legal statutes, regulations, contracts, and technical specs — where each chunk must be identifiable by its position in the hierarchy.`,
+      groupTip: `Split the document flat at a chosen heading level, merging adjacent small sections to ensure semantic flow. Chunks exclude ancestral path.\n
+Best for: Documents with flowing, contextually connected content — such as books, manuals, reports, and articles — where narrative coherence depends on keeping adjacent paragraphs together.`,
       enableMultiColumn: 'Detect multi-column layout',
       enableMultiColumnTip:
         'Detect and parse multi-column page layouts to preserve the correct reading order. Turn this on for PDFs or documents with two-column or newspaper-style layouts.',

web/src/locales/zh.ts

@@ -1261,9 +1261,9 @@ General：实体和关系提取提示来自 GitHub - microsoft/graphrag：基于
         author: '作者',
         sectionTitle: '章节标题',
       },
-      includeHeadingContent: '包含标题内容',
+      includeHeadingContent: '分离上级标题正文',
       includeHeadingContentTip:
-        '启用后，标题下的直接内容将作为一个独立的块保留。子块仅保留标题路径。',
+        '启用后，每个分块仅保留标题路径和自身内容，与上级标题紧挨着的内容将作为一个独立的块保留。',
       rootAsHeading: '将首个切片设为 H0 标题',
       rootAsHeadingTip:
         '将首个切片设为全局标题，以确保整个文档层级结构中拥有一致的上下文信息。该功能尤其适用于首段包含关键信息的简历。',