edit pass: six-azure-managed-instance-for-apache-cassandra-articles

Author: ShawnJackson

articles/managed-instance-apache-cassandra/customer-managed-keys.md

@@ -18,7 +18,7 @@ In Azure Managed Instance for Apache Cassandra, you can use your own key to encr
 
 - Set up a secret by using Azure Key Vault. For more information, see [About Azure Key Vault secrets](../key-vault/secrets/about-secrets.md).
 - Deploy a virtual network in your resource group.
-- Apply the network contributor role with the Azure Cosmos DB service principal as a member. Use the following command:
+- Apply the Network Contributor role with the Azure Cosmos DB service principal as a member. Use the following command:
 
   ```azurecli-interactive  
       az role assignment create \
@@ -67,7 +67,7 @@ This article requires Azure CLI version 2.30.0 or later. If you're using Azure C
       }
     ```
 
-1. In the Azure portal, go to your key vault and select **Access policies**. Then select **Add Access Policy** to create an access policy for your keys:
+1. In the Azure portal, go to your key vault and select **Access policies**. Then select **Add Access Policy** to create an access policy for your keys.
 
    :::image type="content" source="./media/cmk/key-vault-access-policy-1.png" alt-text="Screenshot that shows the pane for access policies in the Azure portal." lightbox="./media/cmk/key-vault-access-policy-1.png" border="true":::
 

articles/managed-instance-apache-cassandra/jaeger.md

@@ -75,7 +75,7 @@ This article details the use of the sample application HotROD and Jaeger alongsi
 
 ## Support
 
-If you have problems running or testing Jaeger, open a support ticket. Provide the subscription ID and account name where your Jaeger test is running.
+If you have problems running or testing Jaeger, open a support ticket. Provide the subscription ID and account name where your Jaeger instance is running.
 
 ## Next steps
 

articles/managed-instance-apache-cassandra/manage-resources-cli.md

@@ -111,7 +111,7 @@ az managed-cassandra cluster list\
 List clusters by subscription ID by using the [az managed-cassandra cluster list](/cli/azure/managed-cassandra) command:
 
 ```azurecli-interactive
-# set your subscription id
+# Set your subscription ID
 az account set -s <subscriptionID>
 
 az managed-cassandra cluster list
@@ -172,7 +172,7 @@ Choose the value for `--sku` from the following available virtual machine (VM) o
 * Standard_L16as_v3
 * Standard_L32as_v3
 
-Currently, Azure Managed Instance for Apache Cassandra doesn't support transitioning across VM families. For instance, if you currently have a Standard_DS13_v2 VM and are interested in upgrading to a larger VM such as Standard_DS14_v2, this option isn't available. However, you can open a support ticket to request an upgrade to the larger VM.
+Currently, Azure Managed Instance for Apache Cassandra doesn't support transitioning across VM families. For instance, if you currently have a Standard_DS13_v2 VM and are interested in upgrading to a larger VM such as Standard_DS14_v2, this option isn't available. However, you can open a support ticket to request the upgrade.
 
 In the preceding command, `--availability-zone` is set to `false`. To enable availability zones, set this value to `true`. Availability zones increase the service-level agreement (SLA) for availability of the service. For more information, review the [full SLA details](https://azure.microsoft.com/support/legal/sla/managed-instance-apache-cassandra/v1_0/).
 

articles/managed-instance-apache-cassandra/monitor-clusters.md

@@ -22,7 +22,7 @@ You can visualize metrics for Azure Managed Instance for Apache Cassandra in the
 
 ## Diagnostic settings in Azure
 
-Azure Monitor uses diagnostic settings to collect resource logs, which are also called *data plane logs*. An Azure resource emits resource logs to provide rich, frequent data about its operation. Azure Monitor captures these logs per request. Examples of data plane operations include delete, insert, and readFeed. The content of these logs varies by resource type.
+Azure Monitor uses diagnostic settings to collect resource logs, which are also called *data plane logs*. An Azure resource emits resource logs to provide rich, frequent data about its operations. Azure Monitor captures these logs per request. Examples of data plane operations include delete, insert, and readFeed. The content of these logs varies by resource type.
 
 Platform metrics and activity logs are collected automatically, whereas you must create a diagnostic setting to collect resource logs or to forward them outside Azure Monitor. You can turn on diagnostic settings for Azure Managed Instance for Apache Cassandra cluster resources and send resource logs to the following sources:
 
@@ -33,7 +33,7 @@ Platform metrics and activity logs are collected automatically, whereas you must
 > [!NOTE]
 > We recommend creating the diagnostic setting in resource-specific mode.
 
-## <a id="create-setting-portal"></a> Create diagnostic settings via the Azure portal
+### <a id="create-setting-portal"></a> Create diagnostic settings via the Azure portal
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
@@ -60,7 +60,7 @@ Platform metrics and activity logs are collected automatically, whereas you must
 
     :::image type="content" source="./media/azure-monitor/query.png" alt-text="Screenshot that shows query logs.":::
 
-## <a id="create-setting-cli"></a> Create a diagnostic setting via Azure CLI
+### <a id="create-setting-cli"></a> Create a diagnostic setting via the Azure CLI
 
 To create a diagnostic setting by using the Azure CLI, use the [az monitor diagnostic-settings create](/cli/azure/monitor/diagnostic-settings#az-monitor-diagnostic-settings-create) command:
 
@@ -72,21 +72,21 @@ To create a diagnostic setting by using the Azure CLI, use the [az monitor diagn
     az monitor diagnostic-settings create  --name tvk-diagnostic-logs-cassandra --resource $resourceId --logs  $logs --workspace $workspace --export-to-resource-specific true
 ```
 
-## <a id="create-diagnostic-setting"></a> Create a diagnostic setting via REST API
+### <a id="create-diagnostic-setting"></a> Create a diagnostic setting via the REST API
 
 Use the [Azure Monitor REST API](/rest/api/monitor/diagnosticsettings/createorupdate) for creating a diagnostic setting via the interactive console.
 
 > [!NOTE]
 > We recommend setting the `logAnalyticsDestinationType` property to `Dedicated` for enabling resource-specific tables.
 
-### Request
+#### Request
 
 ```HTTP
 PUT
 https://management.azure.com/{resource-id}/providers/microsoft.insights/diagnosticSettings/service?api-version={api-version}
 ```
 
-### Headers
+#### Headers
 
 |Parameters/Headers  | Value/Description  |
 |---------|---------|
@@ -95,7 +95,7 @@ https://management.azure.com/{resource-id}/providers/microsoft.insights/diagnost
 |`api-version`     |    `2017-05-01-preview`     |
 |`Content-Type`     |    `application/json`     |
 
-### Body
+#### Body
 
 ```json
 {
@@ -177,7 +177,7 @@ Examples:
 
 ### Cassandra 4 and later
 
-In Cassandra 4 and later, you can configure your whitelist in the Cassandra configuration. For detailed guidance, see [Update Cassandra Configuration](create-cluster-portal.md#update-cassandra-configuration). The available options are as follows (reference: [Cassandra documentation for audit logging](https://cassandra.apache.org/doc/stable/cassandra/operating/audit_logging.html)):
+In Cassandra 4 and later, you can configure your whitelist in the Cassandra configuration. For detailed guidance, see [Update Cassandra configuration](create-cluster-portal.md#update-cassandra-configuration). The available options are as follows (reference: [Cassandra documentation for audit logging](https://cassandra.apache.org/doc/stable/cassandra/operating/audit_logging.html)):
 
 ```
 audit_logging_options:

articles/managed-instance-apache-cassandra/use-vpn.md

@@ -39,7 +39,7 @@ However, if you have internal security concerns about data exfiltration, your se
     --cluster-name "vpn-test-cluster"
     ```
 
-    From the output, make a copy of the `privateLinkResourceId` ID.
+    From the output, make a copy of the `privateLinkResourceId` value.
 
 1. In the Azure portal, [create a private endpoint](../cosmos-db/how-to-configure-private-endpoints.md) by using these details:
     1. On the **Resource** tab, select **Connect to an Azure resource by resource ID or alias** as the connection method and **Microsoft.Network/privateLinkServices** as the resource type. Enter the `privateLinkResourceId` value from the previous step.