Skip to content

Commit 0491f4e

Browse files
authored
Update use-ai-foundry.md
1 parent 6bd98f2 commit 0491f4e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/ai-services/content-understanding/quickstart/use-ai-foundry.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ Follow these steps to create a custom task in the Azure AI Foundry. This task wi
4949

5050
Now that everything is configured to get started, we can walk through, step-by-step, how to build your first analyzer.
5151

52-
### Single-file task (Standard mode)
52+
# [Single-file task (Standard mode](#tab/standard)
5353

5454
When you create a single-file Content Understanding task, you'll start by building your field schema. The schema is the customizable framework that allows the analyzer to extract insights from your data. In this example, the schema is created to extract key data from an invoice document, but you can bring in any type of data and the steps remain the same. [Compare the output of this invoice analysis use case to the output of a Content Understanding Pro invoice analysis scenario](). For a complete list of supported file types, see [input file limits](../service-limits.md#input-file-limits).
5555

@@ -88,7 +88,7 @@ When you create a single-file Content Understanding task, you'll start by buildi
8888

8989
Now you successfully built your first Content Understanding analyzer, and are ready to start extracting insights from your data. Check out [Quickstart: Azure AI Content Understanding REST APIs](./use-rest-api.md) to utilize the REST API to call your analyzer.
9090

91-
### Multi-file task (Pro mode)
91+
# [Multi-file task (Pro mode](#tab/pro)
9292

9393
When you create a multi-file Content Understanding task, you'll start by building your field schema. The schema is the customizable framework that guides the analyzer to extract the preferred insights from your data.
9494

0 commit comments

Comments
 (0)