Merge pull request #5203 from HeidiSteen/heidist-freshness

Fix typo

Author: prmerger-automator[bot]

articles/search/search-agentic-retrieval-how-to-pipeline.md

@@ -202,7 +202,7 @@ def agentic_retrieval() -> str:
     messages = project_client.agents.list_messages(thread.id, limit=5, order=ListSortOrder.DESCENDING)
     # Reverse the order so the most recent message is last
     messages.data.reverse()
-    retrieval_result = agent_client.knowledge_retrieval.retrieve(
+    retrieval_result = retrieval_result = agent_client.retrieve(
         retrieval_request=KnowledgeAgentRetrievalRequest(
             messages=[KnowledgeAgentMessage(role=msg["role"], content=[KnowledgeAgentMessageTextContent(text=msg.content[0].text)]) for msg in messages.data],
             target_index_params=[KnowledgeAgentIndexParams(index_name=index_name, reranker_threshold=2.5)]

articles/search/search-howto-reindex.md

@@ -256,7 +256,7 @@ To minimize disruption to application code, consider [creating an index alias](s
 
 ## Add an index description (preview)
 
-Beginning with REST API version 2025-05-01-preview, an `indexdescription` is now supported. This human-readable text is invaluable when a system must access several indexes and make a decision based on the description. Consider a Model Context Protocol (MCP) server that must pick the correct index at run time. The decision can be  based on the description rather than on the index name alone.
+Beginning with REST API version 2025-05-01-preview, a `ddescription` is now supported. This human-readable text is invaluable when a system must access several indexes and make a decision based on the description. Consider a Model Context Protocol (MCP) server that must pick the correct index at run time. The decision can be  based on the description rather than on the index name alone.
 
 An index description is a schema update, and you can add it without having to rebuild the entire index.
 
@@ -275,7 +275,7 @@ The Azure portal supports the latest preview API.
 
 1. Select **Edit JSON**.
 
-1. Insert `"indexDescription"`, followed by the description.
+1. Insert `"description"`, followed by the description.
 
    :::image type="content" source="media/search-how-to-index/edit-index-json.png" alt-text="Screenshot of the JSON definition of an index in the Azure portal.":::
 
@@ -285,11 +285,11 @@ The Azure portal supports the latest preview API.
 
 1. [GET an index definition](/rest/api/searchservice/indexes/get).
 
-1. Copy the JSON.
+1. Copy the JSON so that you can use it as the basis of a new request.
 
-1. [Formulate an index update PUT request](/rest/api/searchservice/indexes/create-or-update?view=rest-searchservice-2025-05-01-preview&preserve-view=true) using the preview API, providing the *full* JSON of the existing schema, plus the new description field.
+1. [Formulate an index update using a PUT request](/rest/api/searchservice/indexes/create-or-update?view=rest-searchservice-2025-05-01-preview&preserve-view=true) and the preview API, providing the *full* JSON of the existing schema, plus the new description field.
 
-1. To confirm the description, issue another [GET using the 2025-05-01-preview REST API](/rest/api/searchservice/indexes/create-or-update?view=rest-searchservice-2025-05-01-preview&preserve-view=true).
+1. To confirm the change, issue another [GET using the 2025-05-01-preview REST API](/rest/api/searchservice/indexes/create-or-update?view=rest-searchservice-2025-05-01-preview&preserve-view=true).
 
 ---