Reordering

Author: ealsur

articles/cosmos-db/bulk-executor-dot-net.md

@@ -11,13 +11,13 @@ ms.author: ramkris
 ms.reviewer: sngun
 ---
 
+# Use the bulk executor .NET library to perform bulk operations in Azure Cosmos DB
+
 > [!NOTE]
 > This bulk executor library described in this article is maintained for applications using the .NET SDK 2.x version. For new applications, you can use the **bulk support** that is directly available with the [.NET SDK version 3.x](tutorial-sql-api-dotnet-bulk-import.md) and it does not require any external library. 
 
 > If you are currently using the bulk executor library and planning to migrate to bulk support on the newer SDK, use the steps in the [Migration guide](how-to-migrate-from-bulk-executor-library.md) to migrate your application.
 
-# Use the bulk executor .NET library to perform bulk operations in Azure Cosmos DB
-
 This tutorial provides instructions on using the bulk executor .NET library to import and update documents to an Azure Cosmos container. To learn about the bulk executor library and how it helps you leverage massive throughput and storage, see the [bulk executor library overview](bulk-executor-overview.md) article. In this tutorial, you will see a sample .NET application that bulk imports randomly generated documents into an Azure Cosmos container. After importing, it shows you how you can bulk update the imported data by specifying patches as operations to perform on specific document fields.
 
 Currently, bulk executor library is supported by the Azure Cosmos DB SQL API and Gremlin API accounts only. This article describes how to use the bulk executor .NET library with SQL API accounts. To learn about using the bulk executor .NET library with Gremlin API accounts, see [perform bulk operations in the Azure Cosmos DB Gremlin API](bulk-executor-graph-dotnet.md).
@@ -198,10 +198,6 @@ Consider the following points for better performance when using the bulk executo
   </system.diagnostics>
   ```
 
-## Migration to .NET SDK version 3
-
-[.NET SDK version 3](tutorial-sql-api-dotnet-bulk-import.md) **includes bulk support** and does not require any external library. If you are currently using the bulk executor library and planning to migrate to bulk support on the newer SDK, follow the steps in our [migration guide](how-to-migrate-from-bulk-executor-library.md).
-
 ## Next steps
 
 * To learn about the Nuget package details and the release notes, see the [bulk executor SDK details](sql-api-sdk-bulk-executor-dot-net.md).

articles/cosmos-db/how-to-migrate-from-bulk-executor-library.md

@@ -60,8 +60,6 @@ After the list of tasks are defined, wait until they are all complete. You can t
 
 The previous code waits until all operations are completed and calculates the required statistics. These statistics are similar to that of the bulk executor library's [BulkImportResponse](https://docs.microsoft.com/dotnet/api/microsoft.azure.cosmosdb.bulkexecutor.bulkimport.bulkimportresponse).
 
-These statistics are similar to that of the bulk executor library's [BulkImportResponse](https://docs.microsoft.com/dotnet/api/microsoft.azure.cosmosdb.bulkexecutor.bulkimport.bulkimportresponse).
-
    :::code language="csharp" source="~/samples-cosmosdb-dotnet-v3/Microsoft.Azure.Cosmos.Samples/Usage/BulkExecutorMigration/Program.cs" ID="ResponseType":::
 
 The `BulkOperationResponse` contains: