PR warnings fixed

Author: v-hearya

articles/search/search-get-started-dotnet.md

@@ -18,7 +18,7 @@ Use the new [Azure.Search.Documents (version 11) client library](/dotnet/api/ove
 You can [download the source code](https://github.com/Azure-Samples/azure-search-dotnet-samples/tree/master/quickstart/v11) to start with a finished project or follow the steps in this article to create your own.
 
 > [!NOTE]
-> Looking for an earlier version? See [Create a search index using Microsoft.Azure.Search v10](/azure-docs-archive-pr/articles/search/search-get-started-dotnet-v10.md) instead.
+> Looking for an earlier version? See [Create a search index using Microsoft.Azure.Search v10](/previous-versions/azure/search/search-get-started-dotnet-v10) instead.
 
 ## Prerequisites
 

articles/search/search-howto-complex-data-types.md

@@ -25,7 +25,7 @@ To get started, we recommend the [Hotels data set](https://github.com/Azure-Samp
 > [!Note]
 > Support for complex types became generally available starting in `api-version=2019-05-06`. 
 >
-> If your search solution is built on earlier workarounds of flattened datasets in a collection, you should change your index to include complex types as supported in the newest API version. For more information about upgrading API versions, see [Upgrade to the newest REST API version](search-api-migration.md) or [Upgrade to the newest .NET SDK version](/azure-docs-archive-pr/articles/search/search-dotnet-sdk-migration-version-9.md).
+> If your search solution is built on earlier workarounds of flattened datasets in a collection, you should change your index to include complex types as supported in the newest API version. For more information about upgrading API versions, see [Upgrade to the newest REST API version](search-api-migration.md) or [Upgrade to the newest .NET SDK version](/previous-versions/azure/search/search-dotnet-sdk-migration-version-9).
 
 ## Example of a complex structure