Merge pull request #272461 from wmwxwa/patch-23

Fix most visible mentions of "RU" & "vCore"

Author: JamesJBarnett

articles/cosmos-db/mongodb/TOC.yml

@@ -8,11 +8,11 @@
   href: cosmos-db-vs-mongodb-atlas.md
 - name: RU
   items:
-    - name: MongoDB RU documentation
+    - name: MongoDB (RU) documentation
       href: index.yml
     - name: Overview
       items:
-        - name: What is Azure Cosmos DB for MongoDB RU?
+        - name: What is Azure Cosmos DB for MongoDB (RU)?
           href: ru/introduction.md
         - name: API versions
           items:

articles/cosmos-db/mongodb/faq.yml

@@ -1,79 +1,79 @@
 ### YamlMime:FAQ
 metadata:
   title: Frequently asked questions
-  titleSuffix: Azure Cosmos DB for MongoDB RU
-  description: Get answers to frequently asked questions about Azure Cosmos DB for MongoDB RU.
+  titleSuffix: Azure Cosmos DB for MongoDB (RU)
+  description: Get answers to frequently asked questions about RU-based Azure Cosmos DB for MongoDB.
   author: seesharprun
   ms.author: sidandrews
   ms.reviewer: gahllevy
   ms.service: cosmos-db
   ms.subservice: mongodb
   ms.topic: faq
   ms.date: 02/23/2024
-title: Frequently asked questions on Azure Cosmos DB for MongoDB RU
+title: Frequently asked questions on Azure Cosmos DB for MongoDB in RU architecture
 summary: |
   [!INCLUDE[MongoDB](../includes/appliesto-mongodb.md)]
 sections:
   - name: General FAQ
     questions:
       - question: |
-          Does Azure Cosmos DB for MongoDB RU support my data residency requirements?
+          Does Azure Cosmos DB for MongoDB (RU) support my data residency requirements?
         answer: |
           Yes, data residency is governed at the database account level, which is associated with one or more regions. Typically, you create a database account for each residency requirement. For example, if you have a requirement to store data in the US and EU, you would create two database accounts, one in the US and one in the EU.
       - question: |
-          Does Azure Cosmos DB for MongoDB RU support documents larger than 2 MB?
+          Does Azure Cosmos DB for MongoDB (RU) support documents larger than 2 MB?
         answer: |
           Yes, documents as large as 16 MB are fully supported.
       - question: |
-          Does Azure Cosmos DB for MongoDB RU support multi-field sort?
+          Does Azure Cosmos DB for MongoDB (RU) support multi-field sort?
         answer: |
           Yes, multi-field sort is supported. A compound index is required for the fields in the sort to ensure the operation is efficient and scalable.
       - question: |
-          Does Azure Cosmos DB for MongoDB RU scale linearly?
+          Does Azure Cosmos DB for MongoDB (RU) scale linearly?
         answer: |
           In many cases, Azure Cosmos DB's costs scale better than linear. For example, if you read a 1-KB document, this operation equates to one Request Unit (RU). But if you read a 10-KB document, this larger operation still equates to roughly one RU. The [capacity calculator](https://cosmos.azure.com/capacitycalculator/) can help you estimate your throughput needs.
       - question: |
-          How can I encrypt Azure Cosmos DB for MongoDB RU data and manage access at the field level?
+          How can I encrypt Azure Cosmos DB for MongoDB (RU) data and manage access at the field level?
         answer: |
-          Azure Cosmos DB for MongoDB RU supports Field Level Encryption.
+          Azure Cosmos DB for MongoDB (RU) supports Field Level Encryption.
       - question: |
-          How do I pay for Azure Cosmos DB for MongoDB RU Request Units (RUs)?
+          How do I pay for Azure Cosmos DB for MongoDB (RU) Request Units (RUs)?
         answer: |
-          Azure Cosmos DB for MongoDB RU offers three capacity modes: provisioned throughput, autoscale, and serverless. Autoscale instantaneously scales to meet your needs, and serverless only charges for the throughput you use.
+          Azure Cosmos DB for MongoDB (RU) offers three capacity modes: provisioned throughput, autoscale, and serverless. Autoscale instantaneously scales to meet your needs, and serverless only charges for the throughput you use.
       - question: |
-          Which features are supported in Azure Cosmos DB for MongoDB RU?
+          Which features are supported in Azure Cosmos DB for MongoDB (RU)?
         answer: |
-          Azure Cosmos DB for MongoDB RU supports a rich set of MongoDB features backed by Azure Cosmos DB's limitless scale architecture. These features include: Aggregation pipelines, Change streams, Indexes, Geospatial queries, and more. For more information, see [feature support matrix](feature-support-42.md).
+          Azure Cosmos DB for MongoDB (RU) supports a rich set of MongoDB features backed by Azure Cosmos DB's limitless scale architecture. These features include: Aggregation pipelines, Change streams, Indexes, Geospatial queries, and more. For more information, see [feature support matrix](feature-support-42.md).
       - question: |
-          Does Azure Cosmos DB for MongoDB RU run on-premises?
+          Does Azure Cosmos DB for MongoDB (RU) run on-premises?
         answer: |
-          Azure Cosmos DB for MongoDB RU is a cloud-native multitenant service and isn't available on-premises. Azure Cosmos DB offers an [emulator for local development and testing](../emulator.md).
+          Azure Cosmos DB for MongoDB (RU) is a cloud-native multitenant service and isn't available on-premises. Azure Cosmos DB offers an [emulator for local development and testing](../emulator.md).
       - question: |
-          How do I connect to my Azure Cosmos DB for MongoDB RU database?
+          How do I connect to my Azure Cosmos DB for MongoDB (RU) database?
         answer: |
-          The quickest way to connect to an Azure Cosmos DB for MongoDB RU database is to use the **Quick Start** feature within the resource's page in the [Azure portal](https://portal.azure.com). The Quick Start includes code snippets preconfigured to connect to your database.
+          The quickest way to connect to an Azure Cosmos DB for MongoDB (RU) database is to use the **Quick Start** feature within the resource's page in the [Azure portal](https://portal.azure.com). The Quick Start includes code snippets preconfigured to connect to your database.
 
           Azure Cosmos DB enforces strict security requirements and standards. Azure Cosmos DB accounts require authentication and secure communication via transport layer security (TLS/SSL). In any examples you build, use TLS/SSL version 1.2.
 
-          For more information, see [Connect to your API for MongoDB RU database](connect-account.md).
+          For more information, see [Connect to your API for MongoDB (RU) database](connect-account.md).
       - question: |
-          What do the error codes mean while using Azure Cosmos DB for MongoDB RU?
+          What do the error codes mean while using Azure Cosmos DB for MongoDB (RU)?
         answer: |
-          Along with the common MongoDB error codes, Azure Cosmos DB for MongoDB RU has its own specific error codes. For more information, see [API for MongoDB RU troubleshooting guide](error-codes-solutions.md).
+          Along with the common MongoDB error codes, Azure Cosmos DB for MongoDB (RU) has its own specific error codes. For more information, see [API for MongoDB (RU) troubleshooting guide](error-codes-solutions.md).
       - question: |
-          Are non-Microsoft drivers for MongoDB supported for use with Azure Cosmos DB for MongoDB RU?
+          Are non-Microsoft drivers for MongoDB supported for use with Azure Cosmos DB for MongoDB (RU)?
         answer: |
-          Yes, you can use non-Microsoft MongoDB Open Database Connectivity (ODBC) drivers with Azure Cosmos DB for MongoDB RU.
+          Yes, you can use non-Microsoft MongoDB Open Database Connectivity (ODBC) drivers with Azure Cosmos DB for MongoDB (RU).
 additionalContent: |
   ## Related content
 
   - [Frequently asked questions about Azure Cosmos DB for MongoDB vCore](vcore/faq.yml)
 
-  - [Get started with Azure Cosmos DB for MongoDB RU and Node.js](quickstart-nodejs.md)
-  - [Get started with Azure Cosmos DB for MongoDB RU and Python](quickstart-python.md)
-  - [Get started with Azure Cosmos DB for MongoDB RU and Java](quickstart-java.md)
-  - [Get started with Azure Cosmos DB for MongoDB RU and .NET](quickstart-dotnet.md)
-  - [Get started with Azure Cosmos DB for MongoDB RU and Go](quickstart-go.md)
+  - [Get started with Azure Cosmos DB for MongoDB (RU) and Node.js](quickstart-nodejs.md)
+  - [Get started with Azure Cosmos DB for MongoDB (RU) and Python](quickstart-python.md)
+  - [Get started with Azure Cosmos DB for MongoDB (RU) and Java](quickstart-java.md)
+  - [Get started with Azure Cosmos DB for MongoDB (RU) and .NET](quickstart-dotnet.md)
+  - [Get started with Azure Cosmos DB for MongoDB (RU) and Go](quickstart-go.md)
 
   ## Next step
 

articles/cosmos-db/mongodb/quickstart-go.md

@@ -1,6 +1,6 @@
 ---
-title: Connect a Go application to Azure Cosmos DB's API for MongoDB
-description: This quickstart demonstrates how to connect an existing Go application to Azure Cosmos DB's API for MongoDB.
+title: Connect a Go application to Azure Cosmos DB for MongoDB
+description: This quickstart demonstrates how to connect an existing Go application to Azure Cosmos DB for MongoDB.
 author: gahl-levy
 ms.author: gahllevy
 ms.service: cosmos-db
@@ -10,7 +10,7 @@ ms.topic: quickstart
 ms.date: 04/26/2022
 ms.custom: mode-api, devx-track-azurecli, devx-track-go
 ---
-# Quickstart: Connect a Go application to Azure Cosmos DB's API for MongoDB
+# Quickstart: Connect a Go application to Azure Cosmos DB for MongoDB
 [!INCLUDE[MongoDB](../includes/appliesto-mongodb.md)]
 
 > [!div class="op_single_selector"]
@@ -69,7 +69,7 @@ The following snippets are all taken from the `todo.go` file.
 
 ### Connecting the Go app to Azure Cosmos DB
 
-[`clientOptions`](https://pkg.go.dev/go.mongodb.org/[email protected]/mongo/options?tab=doc#ClientOptions) encapsulates the connection string for Azure Cosmos DB, which is passed in using an environment variable (details in the upcoming section). The connection is initialized using [`mongo.NewClient`](https://pkg.go.dev/go.mongodb.org/[email protected]/mongo?tab=doc#NewClient) to which the `clientOptions` instance is passed. [`Ping` function](https://pkg.go.dev/go.mongodb.org/[email protected]/mongo?tab=doc#Client.Ping) is invoked to confirm successful connectivity (it is a fail-fast strategy)
+[`clientOptions`](https://pkg.go.dev/go.mongodb.org/[email protected]/mongo/options?tab=doc#ClientOptions) encapsulates the connection string for Azure Cosmos DB, which is passed in using an environment variable (details in the upcoming section). The connection is initialized using [`mongo.NewClient`](https://pkg.go.dev/go.mongodb.org/[email protected]/mongo?tab=doc#NewClient) to which the `clientOptions` instance is passed. [`Ping` function](https://pkg.go.dev/go.mongodb.org/[email protected]/mongo?tab=doc#Client.Ping) is invoked to confirm successful connectivity (it'is a fail-fast strategy).
 
 ```go
     ctx, cancel := context.WithTimeout(context.Background(), time.Second*10)
@@ -109,7 +109,7 @@ func create(desc string) {
     }
 ```
 
-We pass in a `Todo` struct that contains the description and the status (which is initially set to `pending`)
+We pass in a `Todo` struct that contains the description and the status (which is initially set to `pending`):
 
 ```go
 type Todo struct {
@@ -120,7 +120,7 @@ type Todo struct {
 ```
 ### List `todo` items
 
-We can list TODOs based on criteria. A [`bson.D`](https://pkg.go.dev/go.mongodb.org/[email protected]/bson?tab=doc#D) is created to encapsulate the filter criteria
+We can list TODOs based on criteria. A [`bson.D`](https://pkg.go.dev/go.mongodb.org/[email protected]/bson?tab=doc#D) is created to encapsulate the filter criteria:
 
 ```go
 func list(status string) {
@@ -153,7 +153,7 @@ func list(status string) {
     }
 ```
 
-Finally, the information is rendered in tabular format
+Finally, the information is rendered in tabular format:
 
 ```go
     todoTable := [][]string{}
@@ -174,7 +174,7 @@ Finally, the information is rendered in tabular format
 
 ### Update a `todo` item
 
-A `todo` can be updated based on its `_id`. A [`bson.D`](https://pkg.go.dev/go.mongodb.org/[email protected]/bson?tab=doc#D) filter is created based on the `_id` and another one is created for the updated information, which is a new status (`completed` or `pending`) in this case. Finally, the [`UpdateOne`](https://pkg.go.dev/go.mongodb.org/[email protected]/mongo?tab=doc#Collection.UpdateOne) function is invoked with the filter and the updated document
+A `todo` can be updated based on its `_id`. A [`bson.D`](https://pkg.go.dev/go.mongodb.org/[email protected]/bson?tab=doc#D) filter is created based on the `_id` and another one is created for the updated information, which is a new status (`completed` or `pending`) in this case. Finally, the [`UpdateOne`](https://pkg.go.dev/go.mongodb.org/[email protected]/mongo?tab=doc#Collection.UpdateOne) function is invoked with the filter and the updated document:
 
 ```go
 func update(todoid, newStatus string) {
@@ -194,7 +194,7 @@ func update(todoid, newStatus string) {
 
 ### Delete a `todo`
 
-A `todo` is deleted based on its `_id` and it is encapsulated in the form of a [`bson.D`](https://pkg.go.dev/go.mongodb.org/[email protected]/bson?tab=doc#D) instance. [`DeleteOne`](https://pkg.go.dev/go.mongodb.org/[email protected]/mongo?tab=doc#Collection.DeleteOne) is invoked to delete the document.
+A `todo` is deleted based on its `_id` and it'is encapsulated in the form of a [`bson.D`](https://pkg.go.dev/go.mongodb.org/[email protected]/bson?tab=doc#D) instance. [`DeleteOne`](https://pkg.go.dev/go.mongodb.org/[email protected]/mongo?tab=doc#Collection.DeleteOne) is invoked to delete the document.
 
 ```go
 func delete(todoid string) {
@@ -231,27 +231,27 @@ To confirm that the application was built properly.
 
 ### Sign in to Azure
 
-If you choose to install and use the CLI locally, this topic requires that you are running the Azure CLI version 2.0 or later. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI]. 
+If you choose to install and use the CLI locally, this topic requires that you're running the Azure CLI version 2.0 or later. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI]. 
 
-If you are using an installed Azure CLI, sign in to your Azure subscription with the [az login](/cli/azure/reference-index#az-login) command and follow the on-screen directions. You can skip this step if you're using the Azure Cloud Shell.
+If you're using an installed Azure CLI, sign in to your Azure subscription with the [az login](/cli/azure/reference-index#az-login) command and follow the on-screen directions. You can skip this step if you're using the Azure Cloud Shell.
 
 ```azurecli
 az login 
 ``` 
    
 ### Add the Azure Cosmos DB module
 
-If you are using an installed Azure CLI, check to see if the `cosmosdb` component is already installed by running the `az` command. If `cosmosdb` is in the list of base commands, proceed to the next command. You can skip this step if you're using the Azure Cloud Shell.
+If you're using an installed Azure CLI, check to see if the `cosmosdb` component is already installed by running the `az` command. If `cosmosdb` is in the list of base commands, proceed to the next command. You can skip this step if you're using the Azure Cloud Shell.
 
-If `cosmosdb` is not in the list of base commands, reinstall [Azure CLI](/cli/azure/install-azure-cli).
+If `cosmosdb` isn't in the list of base commands, reinstall [Azure CLI](/cli/azure/install-azure-cli).
 
 ### Create a resource group
 
-Create a [resource group](../../azure-resource-manager/management/overview.md) with the [az group create](/cli/azure/group#az-group-create). An Azure resource group is a logical container into which Azure resources like web apps, databases and storage accounts are deployed and managed. 
+Create a [resource group](../../azure-resource-manager/management/overview.md) with the [az group create](/cli/azure/group#az-group-create). An Azure resource group is a logical container into which Azure resources like web apps, databases, and storage accounts are deployed and managed. 
 
 The following example creates a resource group in the West Europe region. Choose a unique name for the resource group.
 
-If you are using Azure Cloud Shell, select **Try It**, follow the onscreen prompts to login, then copy the command into the command prompt.
+If you're using Azure Cloud Shell, select **Try It**, follow the onscreen prompts to log in, then copy the command into the command prompt.
 
 ```azurecli-interactive
 az group create --name myResourceGroup --location "West Europe"
@@ -323,7 +323,7 @@ The Azure CLI outputs information similar to the following example.
 ## Configure the application 
 
 <a name="devconfig"></a>
-### Export the connection string, MongoDB database and collection names as environment variables. 
+### Export the connection string, MongoDB database, and collection names as environment variables. 
 
 ```bash
 export MONGODB_CONNECTION_STRING="mongodb://<COSMOSDB_ACCOUNT_NAME>:<COSMOSDB_PASSWORD>@<COSMOSDB_ACCOUNT_NAME>.documents.azure.com:10255/?ssl=true&replicaSet=globaldb&maxIdleTimeMS=120000&appName=@<COSMOSDB_ACCOUNT_NAME>@"
@@ -371,7 +371,7 @@ List all the `todo`s
 ./todo --list all
 ```
 
-You should see the ones you just added in a tabular format as such
+You should see the ones you just added in a tabular format as such:
 
 ```bash
 +----------------------------+--------------------------------+-----------+
@@ -384,7 +384,7 @@ You should see the ones you just added in a tabular format as such
 +----------------------------+--------------------------------+-----------+
 ```
 
-To update the status of a `todo` (e.g. change it to `completed` status), use the `todo` ID
+To update the status of a `todo` (e.g. change it to `completed` status), use the `todo` ID:
 
 ```bash
 ./todo --update 5e9fd6b1bcd2fa6bd267d4c4,completed
@@ -396,7 +396,7 @@ List only the completed `todo`s
 ./todo --list completed
 ```
 
-You should see the one you just updated
+You should see the one you just updated:
 
 ```bash
 +----------------------------+--------------------------------+-----------+
@@ -418,19 +418,19 @@ In the top Search box, enter **Azure Cosmos DB**. When your Azure Cosmos DB acco
 :::image type="content" source="./media/quickstart-go/go-cosmos-db-data-explorer.png" alt-text="Data Explorer showing the newly created document":::
 
 
-Delete a `todo` using it's ID
+Delete a `todo` using its ID:
 
 ```bash
 ./todo --delete 5e9fd6b1bcd2fa6bd267d4c4,completed
 ```
 
-List the `todo`s to confirm
+List the `todo`s to confirm:
 
 ```bash
 ./todo --list all
 ```
 
-The `todo` you just deleted should not be present
+The `todo` you just deleted shouldn't be present:
 
 ```bash
 +----------------------------+--------------------------------+-----------+