Skip to content

Commit 4382863

Browse files
Update tutorial-optimize-indexing-push-api.md
Fixed blocking issue
1 parent 753262a commit 4382863

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/search/tutorial-optimize-indexing-push-api.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -245,8 +245,8 @@ Identify which batch size is most efficient and then use that batch size in the
245245

246246
Now that we've identified the batch size we intend to use, the next step is to begin to index the data. To index data efficiently, this sample:
247247

248-
1. Uses multiple threads/workers
249-
1. Implements an exponential backoff retry strategy
248+
* Uses multiple threads/workers.
249+
* Implements an exponential backoff retry strategy.
250250

251251
### Use multiple threads/workers
252252

@@ -387,4 +387,4 @@ You can find and manage resources in the portal, using the **All resources** or
387387
Now that you're familiar with the concept of ingesting data efficiently, let's take a closer look at Lucene query architecture and how full text search works in Azure Cognitive Search.
388388

389389
> [!div class="nextstepaction"]
390-
> [How full text search works in Azure Cognitive Search](search-lucene-query-architecture.md)
390+
> [How full text search works in Azure Cognitive Search](search-lucene-query-architecture.md)

0 commit comments

Comments
 (0)