Merge pull request #314733 from ecfan/patch-1

Clarify region limit for Parse document

Author: prmerger-automator[bot]

articles/logic-apps/parse-document-chunk-text.md

@@ -1,6 +1,6 @@
 ---
 title: Parse Documents and Chunk Text in Workflows
-description: Parse documents and chunk text to transform content into tokenized strings in workflows for Azure Logic Apps.
+description: Parse documents and chunk text to transform content into tokenized strings for workflows in Azure Logic Apps.
 services: azure-logic-apps
 ms.suite: integration
 ms.collection: ce-skilling-ai-copilot
@@ -11,11 +11,11 @@ ms.date: 04/13/2026
 # Customer intent: As an integration developer who works with Azure Logic Apps, I want to parse a document or chunk text as tokenized strings for Azure AI Search or Azure OpenAI actions in my workflows.
 ---
 
-# Parse documents and chunk text as tokenized strings for AI actions in workflows for Azure Logic Apps
+# Parse documents and chunk text as tokenized strings for workflows in Azure Logic Apps
 
 [!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
 
-Sometimes you have to convert content into tokens, which are words or chunks of characters, or divide a large document into smaller pieces before you can use this content with some actions. For example, the **Azure AI Search** or **Azure OpenAI** actions expect tokenized input and can handle only a limited number of tokens.
+Sometimes you have to convert content into tokens, which are words or chunks of characters, or divide a large document into smaller pieces before you can use this content with specific actions. For example, the **Azure AI Search** or **Azure OpenAI** actions expect tokenized input and can handle only a limited number of tokens.
 
 For these scenarios, use the **Data Operations** actions named **Parse a document** and **Chunk text** in your logic app workflow. These actions respectively transform content, such as a PDF document, CSV file, Excel file, and so on, into tokenized string output and then split the string into pieces, based on the number of tokens. You can then reference and use these outputs with subsequent actions in your workflow.
 
@@ -35,7 +35,7 @@ This guide shows how to add and set up actions for parsing documents and chunkin
 
 ## Known issues and limitations
 
-- The **Parse a document** action is available only in the following Azure regions:
+- In Consumption workflows, the **Parse a document** action is available only in the following Azure regions:
 
   - Australia East
   - Brazil South