Skip to content

Commit 80dc295

Browse files
committed
Acrolinx fixes
1 parent 241bce9 commit 80dc295

File tree

5 files changed

+11
-11
lines changed

5 files changed

+11
-11
lines changed

learn-pr/wwl-data-ai/ai-knowldge-mining/8-knowledge-check.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -29,13 +29,13 @@ quiz:
2929
choices:
3030
- content: "Azure Functions"
3131
isCorrect: false
32-
explanation: "Incorrect. Azure Functions can be used to implement custom skills, but is not required for built-in skills."
32+
explanation: "Incorrect. Azure Functions can be used to implement custom skills, but isn't required for built-in skills."
3333
- content: "Azure AI services"
3434
isCorrect: true
35-
explanation: "Correct. Azure AI services is required to support built-in skills."
35+
explanation: "Correct. An Azure AI services resource is required to support built-in skills."
3636
- content: "Azure Cosmos DB"
3737
isCorrect: false
38-
explanation: "Incorrect. Azure Cosmos DB could be a data source fo Azure AI Search, but it is not required for built-in skills."
38+
explanation: "Incorrect. Azure Cosmos DB could be a data source fo Azure AI Search, but it isn't required for built-in skills."
3939
- content: "Which kind of projection results in a relational data schema for extracted fields?"
4040
choices:
4141
- content: "File"
@@ -46,6 +46,6 @@ quiz:
4646
explanation: "Incorrect. Object projections are used to store extracted documents as JSON files."
4747
- content: "Table"
4848
isCorrect: true
49-
explanation: "Correct. Use table projections to persists extracted data in a relational schema."
49+
explanation: "Correct. Use table projections to persist extracted data in a relational schema."
5050

5151

learn-pr/wwl-data-ai/ai-knowldge-mining/includes/3-indexing.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@ At the heart of Azure AI Search solutions is the creation of an *index* An index
22

33
![Diagram of an indexer extracting documents from a source and creating an index.](../media/indexer.png)
44

5-
The indexing process starts with a data source: the storage location of your original data artifacts; for example an Azure blob store container full of documents, a database, or some other store.
5+
The indexing process starts with a data source: the storage location of your original data artifacts; for example, an Azure blob store container full of documents, a database, or some other store.
66

77
The Indexer automates the extraction and indexing of data *fields* through an *enrichment pipeline*, in which it applies *document cracking* to extract the contents of the source documents and applies incremental steps to create a hierarchical (JSON-based) document with the required fields for the index definition.
88

9-
The result is a populated index which can be queried to return specified fields from documents that match the query criteria.
9+
The result is a populated index, which can be queried to return specified fields from documents that match the query criteria.
1010

1111
## How documents are constructed during indexing
1212

learn-pr/wwl-data-ai/ai-knowldge-mining/includes/4-ai-skills.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ To use the built-in skills, your indexer must have access to an Azure AI service
1818

1919
## Custom skills
2020

21-
You can further extend the enrichment capabilities of your index by creating *custom* skills. As the name suggests, custom skills perform custom logic on input data from your index document to return new field values that can be incorporated into the index. Often, custom skills are "wrappers" around services that are specifically designed to extract data from documents. For example, you could implement a custom skill as an Azure Function, and use it to pass data from your index document to an Azure AI Document Intelligence model which can extract fields from a form.
21+
You can further extend the enrichment capabilities of your index by creating *custom* skills. As the name suggests, custom skills perform custom logic on input data from your index document to return new field values that can be incorporated into the index. Often, custom skills are "wrappers" around services that are specifically designed to extract data from documents. For example, you could implement a custom skill as an Azure Function, and use it to pass data from your index document to an Azure AI Document Intelligence model, which can extract fields from a form.
2222

2323
> [!TIP]
2424
> To learn mode about using custom skills with Azure AI Search, see **[Add a custom skill to an Azure AI Search enrichment pipeline](/azure/search/cognitive-search-custom-skill-interface)** in the Azure AI Search documentation.

learn-pr/wwl-data-ai/ai-knowldge-mining/includes/5-search-index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,11 @@ Each index field can be configured with the following attributes:
1111
- **facetable**: Fields that can be used to determine values for *facets* (user interface elements used to filter the results based on a list of known field values).
1212
- **retrievable**: Fields that can be included in search results (*by default, all fields are retrievable unless this attribute is explicitly removed*).
1313

14-
## Full text search
14+
## Full-text search
1515

16-
While you could retrieve index entries based on simple field value matching, most search solutions use *full text search* semantics to query an index.
16+
While you could retrieve index entries based on simple field value matching, most search solutions use *full-text search* semantics to query an index.
1717

18-
Full text search describes search solutions that parse text-based document contents to find query terms. Full text search queries in Azure AI Search are based on the *Lucene* query syntax, which provides a rich set of query operations for searching, filtering, and sorting data in indexes. Azure AI Search supports two variants of the Lucene syntax:
18+
Full-text search describes search solutions that parse text-based document contents to find query terms. Full-text search queries in Azure AI Search are based on the *Lucene* query syntax, which provides a rich set of query operations for searching, filtering, and sorting data in indexes. Azure AI Search supports two variants of the Lucene syntax:
1919

2020
- **Simple** - An intuitive syntax that makes it easy to perform basic searches that match literal query terms submitted by a user.
2121
- **Full** - An extended syntax that supports complex filtering, regular expressions, and other more sophisticated queries.

learn-pr/wwl-data-ai/ai-knowldge-mining/includes/9-summary.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
In this module, you've learned how Azure AI Search enables you to build intelligent search and knowledge mining solutions by indexing and enriching data from a variety of sources. You explored the indexing process, the use of AI skills for data enrichment, and how to persist enriched data in a knowledge store for further analysis and integration.
1+
In this module, you've learned how Azure AI Search enables you to build intelligent search and knowledge mining solutions by indexing and enriching data from various sources. You explored the indexing process, the use of AI skills for data enrichment, and how to persist enriched data in a knowledge store for further analysis and integration.
22

33
With these skills, you're now equipped to design and implement solutions that unlock valuable insights from your data using Azure AI Search.
44

0 commit comments

Comments
 (0)