Fix formatting of instructions for document indexing

Author: mdonovanmsft

articles/search/search-how-to-index-markdown-blobs.md

@@ -471,7 +471,7 @@ Before re-indexing a modified Markdown file, explicitly delete the existing docu
 * Manually indentify individual stale documents by identifying duplicates in the index to be deleted. This may be feasible for small, well-understood changes but can be time-consuming.
 * (**Recommended**) Remove all documents generated from the same parent file before re-indexing. This ensures a clean slate and avoids inconsistencies.
 
-  1. Identify the id  of the documents associated with the file. Use a query like the one below to retrieve the document key IDs (e.g., `id`, `chunk_id`, etc.) for all documents tied to a specific file. Replace `metadata_storage_path` with the appropriate field in your index that maps to the file path or blob URI. Note that this field must be a key.
+1. Identify the id  of the documents associated with the file. Use a query like the one below to retrieve the document key IDs (e.g., `id`, `chunk_id`, etc.) for all documents tied to a specific file. Replace `metadata_storage_path` with the appropriate field in your index that maps to the file path or blob URI. Note that this field must be a key.
 ```http
 GET https://[service name].search.windows.net/indexes/[index name]/docs?api-version=2025-05-01-preview
 Content-Type: application/json