edits

Author: ktoliver

articles/azure-cache-for-redis/cache-java-get-started.md

@@ -1,6 +1,6 @@
 ---
 title: 'Quickstart: Use Azure Cache for Redis in Java'
-description: In this quickstart, you create a new Java app that uses Azure Cache for Redis
+description: In this quickstart, you create a new Java app that uses Azure Cache for Redis.
 author: KarlErickson
 ms.author: zhihaoguo
 ms.date: 01/04/2022
@@ -12,11 +12,11 @@ ms.custom: devx-track-java, devx-track-javaee, mode-api, mvc, devx-track-extende
 
 # Quickstart: Use Azure Cache for Redis in Java
 
-In this quickstart, you incorporate Azure Cache for Redis into a Java app using the [Jedis](https://github.com/xetorthio/jedis) Redis client. Your cache is a secure, dedicated cache that is accessible from any application within Azure.
+In this quickstart, you incorporate Azure Cache for Redis into a Java app by using the [Jedis](https://github.com/xetorthio/jedis) Redis client. Your cache is a secure, dedicated cache that is accessible from any application within Azure.
 
-## Skip to the code on GitHub
+## Skip to the code
 
-Clone the repo [Java quickstart](https://github.com/Azure-Samples/azure-cache-redis-samples/tree/main/quickstart/java) on GitHub.
+Clone the repo on GitHub: [Java quickstart](https://github.com/Azure-Samples/azure-cache-redis-samples/tree/main/quickstart/java)
 
 ## Prerequisites
 

articles/azure-cache-for-redis/cache-java-redisson-get-started.md

@@ -15,17 +15,17 @@ ms.custom: mvc, seo-java-january2024, seo-java-february2024, mode-api, devx-trac
 
 In this quickstart, you incorporate Azure Cache for Redis into a Java app using the [Redisson](https://redisson.org/) Redis client and JCP standard JCache API. These services give you  access to a secure, dedicated cache that is accessible from any application within Azure. This article provides two options for selecting the Azure identity to use for the Redis connection.
 
-## Skip to the code on GitHub
+## Skip to the code
 
-This quickstart uses the Maven archetype feature to generate the scaffolding for the app. The quickstart directs you to modify the generated code to arrive at the working sample app. If you want to skip straight to the completed code, see the [Java quickstart](https://github.com/Azure-Samples/azure-cache-redis-samples/tree/main/quickstart/java-redisson-jcache) on GitHub.
+This quickstart uses the Maven archetype feature to generate scaffolding for the app. The quickstart describes how to modify the generated code to end up with a working sample app. If you want to go straight to the completed code, clone the repository on GitHub: [Java quickstart](https://github.com/Azure-Samples/azure-cache-redis-samples/tree/main/quickstart/java-redisson-jcache)
 
 ## Prerequisites
 
 - Azure subscription - [create one for free](https://azure.microsoft.com/free/)
 - [Use Microsoft Entra ID for cache authentication](cache-azure-active-directory-for-authentication.md)
 - [Apache Maven](https://maven.apache.org/download.cgi)
 
-## Create an Azure Cache for Redis
+## Create a cache
 
 [!INCLUDE [redis-cache-create](~/reusable-content/ce-skilling/azure/includes/azure-cache-for-redis/includes/redis-cache-create.md)]
 

articles/azure-cache-for-redis/includes/cache-delete-resource-group.md

@@ -12,10 +12,10 @@ ms.topic: include
 
 If you want to continue to use the resources you created in this article, keep the resource group.
 
-Otherwise, if you're finished with the resources, you can delete the Azure resource group that you created to avoid charges.
+Otherwise, to avoid charges, if you're finished with the resources, you can delete the Azure resource group that you created.
 
-> [!IMPORTANT]
-> Deleting a resource group is irreversible. When you delete a resource group, all the resources in it are permanently deleted. Make sure that you do not accidentally delete the wrong resource group or resources. If you created the resources inside an existing resource group that contains resources you want to keep, you can delete each resource individually instead of deleting the resource group.
+> [!WARNING]
+> Deleting a resource group is irreversible. When you delete a resource group, all the resources in the resource group are permanently deleted. Make sure that you do not accidentally delete the wrong resource group or resources. If you created the resources inside an existing resource group that has resources you want to keep, you can delete each resource individually instead of deleting the resource group.
 
 ### To delete a resource group
 

articles/azure-cache-for-redis/includes/cache-entra-access.md

@@ -10,21 +10,23 @@ ms.topic: include
 
 ### Enable Microsoft Entra ID authentication on your cache
 
-If you have a cache already, you first want to check to see if Microsoft Entra Authentication has been enabled. If not, then enable it. We recommend using Microsoft Entra ID for your applications.
+For an existing cache, first check to see if Microsoft Entra authentication is enabled. If it's not, complete the following steps to enable Microsoft Entra authentication. We recommend that you use Microsoft Entra ID for authentication in your applications.
 
 1. In the Azure portal, select the Azure Cache for Redis instance where you'd like to use Microsoft Entra token-based authentication.
 
-1. Select **Authentication** from the Resource menu.
+1. On the service menu, under **Settings**, select **Authentication**.
 
-1. Check in the working pane to see if **Enable Microsoft Entra Authentication** is checked. If so, you can move on.
+1. On the **Authentication** pane, check to see whether the **Enable Microsoft Entra Authentication** checkbox is selected. If it is, you can move on to the next section.
 
-1. Select **Enable Microsoft Entra Authentication**, and enter the name of a valid user. The user you enter is automatically assigned _Data Owner Access Policy_ by default when you select **Save**. You can also enter a managed identity or service principal to connect to your cache instance.
+1. Otherwise, select the **Enable Microsoft Entra Authentication** checkbox. Then, enter the name of a valid user. Select **Save**. The user name that you enter is automatically assigned the Data Owner Access Policy.
 
-    :::image type="content" source="media/cache-entra-access/cache-enable-microsoft-entra.png" alt-text="Screenshot showing authentication selected in the resource menu and the enable Microsoft Entra authentication checked.":::
+   You also can enter a managed identity or a service principal to connect to your cache.
 
-1. A popup dialog box displays asking if you want to update your configuration, and informing you that it takes several minutes. Select **Yes.**
+   :::image type="content" source="media/cache-entra-access/cache-enable-microsoft-entra.png" alt-text="Screenshot that shows Authentication selected in the service menu and the Enable Microsoft Entra Authentication checkbox selected.":::
+
+1. In a dialog box, you're asked if you want to update your configuration, and you're informated that making the update takes several minutes to finish. Select **Yes.**
 
    > [!IMPORTANT]
-   > Once the enable operation is complete, the nodes in your cache instance reboots to load the new configuration. We recommend performing this operation during your maintenance window or outside your peak business hours. The operation can take up to 30 minutes.
+   > When the enable operation is finished, the nodes in your cache reboot to load the new configuration. We recommend that you complete this operation during your standard maintenance window or outside your peak business hours. The process can take up to 30 minutes.
 
-For information on using Microsoft Entra ID with Azure CLI, see the [references pages for identity](/cli/azure/redis/identity).
+For information about using Microsoft Entra ID with the Azure CLI, see the [identity reference pages](/cli/azure/redis/identity).

articles/azure-cache-for-redis/includes/redis-access-policy.md

@@ -10,17 +10,17 @@ ms.topic: include
 
 ## Add the Redis access policy
 
-You need to assign a data access policy to the identity that accesses Azure Cache for Redis. For this example, you assign a data access policy to the same Microsoft Entra ID account you use to log into the Azure CLI or Visual Studio.
+You need to assign a data access policy to the identity that accesses Azure Cache for Redis. For this example, you assign a data access policy to the same Microsoft Entra ID account you use to sign in to the Azure CLI or Visual Studio.
 
 1. Select **Settings** Resource menu on the cache and select the **Data Access Configuration**.
 
-1. On the **Data Access Configuration** page, select **Add > New Redis User** from the top navigation.
+1. On the **Data Access Configuration** pane, select **Add** > **New Redis User**.
 
     :::image type="content" source="media/redis-access-policy/assign-access-policy.png" alt-text="Screenshot showing the data access configuration screen.":::
 
 1. On the **New Redis User** page, select the **Data Contributor** policy, and select **Next: Redis Users**.
 
-1. Choose **+ Select Member** to open the flyout menu. Search for your user account and select it from the results.
+1. Choose **Select Member** to open the flyout menu. Search for your user account and select it from the results.
 
     :::image type="content" source="media/redis-access-policy/select-user.png" alt-text="Screenshot showing the Redis user tab in the working pane with select member highlighted with a red box.":::
 

articles/azure-cache-for-redis/includes/redis-cache-access-keys.md

@@ -8,14 +8,24 @@ ms.date: 08/16/2024
 ms.topic: include
 ---
 
-### Retrieve host name, ports, and access keys from the Azure portal
+### Get the host name, ports, and access key
 
-To connect your Azure Cache for Redis server, the cache client needs the host name, ports, and a key for the cache. Some clients might refer to these items by slightly different names. You can get the host name, ports, and keys from the [Azure portal](https://portal.azure.com).
+To connect to your Azure Cache for Redis server, the cache client needs the cache's host name, ports, and an access key. Some clients might refer to these items by using slightly different names. You can get the host name, ports, and keys in the [Azure portal](https://portal.azure.com).
 
-- To get the access keys, select **Authentication** from the Resource menu. Then, select the **Access keys** tab.
+- To get an access key for your cache:
+
+   1. In the Azure portal, go to your cache.
+   1. On the service menu, under **Settings**, select **Authentication**.
+   1. On the **Authentication** pane, select the **Access keys** tab.
+   1. To copy the value for an access key, select the **Copy** icon in the key field.
 
-  ![Azure Cache for Redis keys](media/redis-cache-access-keys/redis-cache-keys.png)
+  ![Screenshot that shows how to go to and copy an access key for an instance of Azure Cache for Redis.](media/redis-cache-access-keys/redis-cache-keys.png)
+
+- To get the host name and ports for your cache:
 
-- To get the host name and ports for your cache, select **Overview** from the Resource menu. The host name is of the form *\<DNS name>.redis.cache.windows.net*.
+   1. In the Azure portal, go to your cache.
+   1. On the service menu, select **Overview**.
+   1. Under **Essentials**, for **Host name**, select the **Copy** icon to copy the host name value. The host name value has the form `<DNS name>.redis.cache.windows.net`.
+   1. For **Ports**, select the **Copy** icon to copy the port values.
 
-  ![Azure Cache for Redis properties](media/redis-cache-access-keys/redis-cache-hostname-ports.png)
+  ![Screenshot that shows how to go to and copy the host name and ports for an instance of Azure Cache for Redis.](media/redis-cache-access-keys/redis-cache-hostname-ports.png)