Merge pull request #227957 from MicrosoftDocs/main

2/20 AM Publish

Author: huypub

articles/active-directory-b2c/technical-overview.md

@@ -38,7 +38,7 @@ The primary resources you work with in an Azure AD B2C tenant are:
 An Azure AD B2C tenant is the first resource you need to create to get started with Azure AD B2C. Learn how to:
 
 * [Create an Azure Active Directory B2C tenant](tutorial-create-tenant.md).
-* [Manage your Azure AD B2C tenant](tenant-management.md)
+* [Manage your Azure AD B2C tenant](tenant-management-manage-administrator.md)
 
 ## Accounts in Azure AD B2C
 

articles/active-directory-b2c/user-overview.md

@@ -21,7 +21,7 @@ In Azure Active Directory B2C (Azure AD B2C), there are several types of account
 The following types of accounts are available:
 
 - **Work account** - A work account can access resources in a tenant, and with an administrator role, can manage tenants.
-- **Guest account** - A guest account can only be a Microsoft account or an Azure AD user that can be used to share administration responsibilities such as [managing a tenant](tenant-management.md).
+- **Guest account** - A guest account can only be a Microsoft account or an Azure AD user that can be used to share administration responsibilities such as [managing a tenant](tenant-management-manage-administrator.md).
 - **Consumer account** - A consumer account is used by a user of the applications you've registered with Azure AD B2C. Consumer accounts can be created by:
   - The user going through a sign-up user flow in an Azure AD B2C application
   - Using Microsoft Graph API

articles/active-directory/develop/scenario-desktop-acquire-token-device-code-flow.md

@@ -68,7 +68,7 @@ static async Task<AuthenticationResult> GetATokenForGraph()
     }
     catch (MsalUiRequiredException ex)
     {
-        // No token found in the cache or AAD insists that a form interactive auth is required (e.g. the tenant admin turned on MFA)
+        // No token found in the cache or Azure AD insists that a form interactive auth is required (e.g. the tenant admin turned on MFA)
         // If you want to provide a more complex user experience, check out ex.Classification
 
         return await AcquireByDeviceCodeAsync(pca);
@@ -253,7 +253,7 @@ if accounts:
     result = app.acquire_token_silent(config["scope"], account=chosen)
 
 if not result:
-    logging.info("No suitable token exists in cache. Let's get a new one from AAD.")
+    logging.info("No suitable token exists in cache. Let's get a new one from Azure AD.")
 
     flow = app.initiate_device_flow(scopes=config["scope"])
     if "user_code" not in flow:

articles/active-directory/governance/understanding-lifecycle-workflows.md

@@ -33,10 +33,10 @@ For delegated scenarios, the admin needs one of the following [Azure AD roles](/
 - Global reader
 - Lifecycle workflows administrator
 
-## Restrictions
+## Limits
 
 
-|Column1  |Limit  |
+|Category  |Limit  |
 |---------|---------|
 |Number of Workflows     |   50 per tenant      |
 |Number of Tasks     |  25 per workflow       |

articles/api-management/how-to-self-hosted-gateway-on-kubernetes-in-production.md

@@ -186,7 +186,7 @@ Request throttling in a self-hosted gateway can be enabled by using the API Mana
 ## Security
 The self-hosted gateway is able to run as non-root in Kubernetes allowing customers to run the gateway securely.
 
-Here's an example of the security context for the self-hosted gateway:
+Here's an example of the security context for the self-hosted gateway container:
 ```yml
 securityContext:
   allowPrivilegeEscalation: false

articles/azure-monitor/essentials/prometheus-metrics-enable.md

@@ -295,7 +295,7 @@ Deploy the template with the parameter file using any valid method for deploying
 
 ## Verify Deployment
 
-Run the following command to which verify that the daemon set was deployed properly:
+Run the following command to verify that the daemon set was deployed properly:
 
 ```
 kubectl get ds ama-metrics-node --namespace=kube-system

articles/azure-signalr/server-graceful-shutdown.md

@@ -44,7 +44,7 @@ In general, there will be four stages in a graceful shutdown process:
 
     Azure SignalR Service will try to reroute the client connection on this server to another valid server. 
 
-    In this scenario, `OnConnectedAsync` and `OnDisconnectedAsync` will be triggered on the new server and the old server respectively with an `IConnectionMigrationFeature` set in the `Context`, which can be used to identify if the client connection was being migrated-in our migrated-out. It could be useful especially for stateful scenarios.
+    In this scenario, `OnConnectedAsync` and `OnDisconnectedAsync` will be triggered on the new server and the old server respectively with an `IConnectionMigrationFeature` set in the `Context`, which can be used to identify if the client connection was being migrated-in or migrated-out. It could be useful especially for stateful scenarios.
 
     The client connection will be immediately migrated after the current message has been delivered, which means the next message will be routed to the new server.
 

articles/azure-signalr/signalr-howto-troubleshoot-guide.md

@@ -389,7 +389,7 @@ public class ThreadPoolStarvationDetector : EventListener
     {
         // See: https://learn.microsoft.com/dotnet/framework/performance/thread-pool-etw-events#threadpoolworkerthreadadjustmentadjustment
         if (eventData.EventId == EventIdForThreadPoolWorkerThreadAdjustmentAdjustment &&
-            eventData.Payload[3] as uint? == ReasonForStarvation)
+            eventData.Payload[2] as uint? == ReasonForStarvation)
         {
             _logger.LogWarning("Thread pool starvation detected!");
         }

articles/backup/restore-sql-database-azure-vm.md

@@ -220,7 +220,7 @@ To relocate the database files from the target restore server, you can frame a T
     GO
   ```
 
-If there are more than two files for the database, you can add additional move clauses to the restore query. You can also use SSMS for database recovery using `.bak` files. [Learn more]( /sql/relational-databases/backup-restore/restore-a-database-backup-using-ssms?view=sql-server-ver16).
+If there are more than two files for the database, you can add additional `MOVE` clauses to the restore query. You can also use SSMS for database recovery using `.bak` files. [Learn more](/sql/relational-databases/backup-restore/restore-a-database-backup-using-ssms?view=sql-server-ver16).
 
 >[!Note]
 >For large database recovery, we recommend you to use TSQL statements. If you want to relocate the specific database files, see the list of database files in the JSON format created during the **Restore as Files** operation.

articles/cosmos-db/whitepapers.md

@@ -1,23 +1,30 @@
 ---
-title: Whitepapers that describe Azure Cosmos DB concepts
-description: Get the list of whitepapers for Azure Cosmos DB, these whitepapers describe the concepts in depth.
+title: Conceptual whitepapers
+titleSuffix: Azure Cosmos DB
+description: This list of conceptual whitepapers describes various Azure Cosmos DB service, development, and data concepts in depth.
 ms.service: cosmos-db
 ms.subservice: nosql
 author: seesharprun
 ms.author: sidandrews
 ms.reviewer: mjbrown
 ms.topic: conceptual
-ms.date: 05/07/2021
+ms.date: 02/20/2023
 ms.custom: seodec18, ignite-2022
 ---
 
-# Azure Cosmos DB whitepapers
+# Azure Cosmos DB conceptual whitepapers
+
 [!INCLUDE[NoSQL, MongoDB, Cassandra, Gremlin, Table](includes/appliesto-nosql-mongodb-cassandra-gremlin-table.md)]
 
 Whitepapers allow you to explore Azure Cosmos DB concepts at a deeper level. This article provides you with a list of available whitepapers for Azure Cosmos DB.
 
 | **Whitepaper** | **Description** |
 | --- | --- |
-|[Schema-Agnostic Indexing with Azure Cosmos DB](https://www.vldb.org/pvldb/vol8/p1668-shukla.pdf) | This paper describes Azure Cosmos DB's indexing subsystem. This paper includes Azure Cosmos DB capabilities such as document representation, query language, document indexing approach, core index support, and early production experiences.|
-| [Azure Cosmos DB and personal data](https://servicetrust.microsoft.com/ViewPage/TrustDocuments?command=Download&downloadType=Document&downloadId=87cc6456-4b23-473c-94d3-6c713b8b8956&docTab=6d000410-c9e9-11e7-9a91-892aae8839ad_FAQ_and_White_Papers)| This paper provides guidance for Azure Cosmos DB customers managing a cloud-based database, an on-premises database, or both, and who need to ensure that the personal data in their database systems is handled and protected in accordance with current rules. |
-|[Next-gen app development with Azure Cosmos DB](https://azure.microsoft.com/resources/microsoft-azure-cosmos-db-flexible-reliable-cloud-nosql-at-any-scale/) | This paper explores how Azure Cosmos DB is uniquely positioned to address the data requirements of modern apps. It includes three customers spotlights highlighting the API for MongoDB, simplified data management, cost-effective scalability, market-leading performance, and reliability. |
+| [Schema-Agnostic Indexing with Azure Cosmos DB](https://www.vldb.org/pvldb/vol8/p1668-shukla.pdf) | This paper describes Azure Cosmos DB's indexing subsystem. This paper includes a deep dive into various Azure Cosmos DB capabilities. These capabilities include; document representation, query language, document indexing approach, core index support, and early production experiences. |
+| [Azure Cosmos DB and personal data](https://servicetrust.microsoft.com/ViewPage/TrustDocuments?command=Download&downloadType=Document&downloadId=87cc6456-4b23-473c-94d3-6c713b8b8956&docTab=6d000410-c9e9-11e7-9a91-892aae8839ad_FAQ_and_White_Papers) | This paper provides guidance for Azure Cosmos DB customers managing a cloud-based database, an on-premises database, or both. This paper is ideal for customers who want to learn more about the rules related to how we handle and protect their personal data in their database systems. |
+| [Next-gen app development with Azure Cosmos DB](https://azure.microsoft.com/resources/microsoft-azure-cosmos-db-flexible-reliable-cloud-nosql-at-any-scale/) | This paper explores how we uniquely positioned Azure Cosmos DB to address the data requirements of modern apps. It includes three customers spotlights highlighting the API for MongoDB, simplified data management, cost-effective scalability, market-leading performance, and reliability. |
+| [Cloud-Scale Data for Spring Developers](https://azure.github.io/cloud-scale-data-for-devs-guide/) | This paper helps you build cloud-native Java applications in Azure. This paper helps you gain insights about using NoSQL and why you should consider Azure Cosmos DB, our fully managed, distributed NoSQL database service on Azure. |
+
+## Next steps
+
+- Learn about [common Azure Cosmos DB use cases](use-cases.md)