edits

ktoliver · ktoliver · commit f719d9c2f493 · 2024-09-09T15:45:15.000-07:00
diff --git a/articles/azure-cache-for-redis/cache-dotnet-core-quickstart.md b/articles/azure-cache-for-redis/cache-dotnet-core-quickstart.md
@@ -31,11 +31,11 @@ If you want to go straight to the code, see the [.NET Core sample](https://githu
 
 [!INCLUDE [redis-cache-access-keys](includes/redis-cache-access-keys.md)]
 
-Make a note of the values for **HOST NAME** and the **Primary** access key. You'll use these values later to construct the `CacheConnection` secret.
+Make a note of the values for **HOST NAME** and the **Primary** access key. You ise these values later to construct the `CacheConnection` secret.
 
 ## Add a local secret for the connection string
 
-In your command window, execute the following command to store a new secret named *CacheConnection* after you replac the placeholders (including angle brackets) with your cache name (`<cache name>`) and primary access key (`<primary-access-key>`):
+In your command window, execute the following command to store a new secret named *CacheConnection* after you replace the placeholders (including angle brackets) with your cache name (`<cache name>`) and primary access key (`<primary-access-key>`):
 
 ```dos
 dotnet user-secrets set CacheConnection "<cache name>.redis.cache.windows.net,abortConnect=false,ssl=true,allowAdmin=true,password=<primary-access-key>"
@@ -50,14 +50,14 @@ The connection to your cache is managed by the `RedisConnection` class. First, y
 
 ```
 
-In *RedisConnection.cs*, the `StackExchange.Redis` namespace has been added to the code. The namespace is required for the `RedisConnection` class.
+In *RedisConnection.cs*, the `StackExchange.Redis` namespace was added to the code. The namespace is required for the `RedisConnection` class.
 
 ```csharp
 using StackExchange.Redis;
 
 ```
 
-The `RedisConnection` code ensures that there is always a healthy connection to the cache by managing the `ConnectionMultiplexer` instance from `StackExchange.Redis`. The `RedisConnection` class re-creates the connection when a connection is lost and unable to reconnect automatically.
+The `RedisConnection` code ensures that there's always a healthy connection to the cache by managing the `ConnectionMultiplexer` instance from `StackExchange.Redis`. The `RedisConnection` class re-creates the connection when a connection is lost and unable to reconnect automatically.
 
 For more information, see [StackExchange.Redis](https://stackexchange.github.io/StackExchange.Redis/) and the code in a [GitHub repo](https://github.com/StackExchange/StackExchange.Redis).
 
@@ -147,7 +147,7 @@ If you opened any files, save the files. Then, build the app by using the follow
 dotnet build
 ```
 
-Run the app with the following command to test serialization of .NET objects:
+To test serialization of .NET objects, run this command:
 
 ```dos
 dotnet run
diff --git a/articles/azure-cache-for-redis/cache-go-get-started.md b/articles/azure-cache-for-redis/cache-go-get-started.md
@@ -167,7 +167,7 @@ The HTTP server starts on port `8080`.
     curl -i localhost:8080/users/1
     ```
 
-    You should get a JSON response that is similar to this example:
+    The output is JSON response that is similar to this example:
 
     ```json
     {
@@ -178,7 +178,7 @@ The HTTP server starts on port `8080`.
     ```
 
 1. If you try to fetch a user who doesn't exist, you get an HTTP `404`.
- 
+
    For example:
 
     ```bash
diff --git a/articles/azure-cache-for-redis/cache-rust-get-started.md b/articles/azure-cache-for-redis/cache-rust-get-started.md
@@ -24,13 +24,13 @@ You'll use the [redis-rs](https://github.com/mitsuhiko/redis-rs) library for Red
 
 This article describes how to create an app by using the Azure portal and then modify the code to end up with a working sample app.
 
-If you want to skip straight to the code, see the [Rust quickstart](https://github.com/Azure-Samples/azure-redis-cache-rust-quickstart/) on GitHub.
+If you want to skip straight to the code, see the [Rust sample quickstart](https://github.com/Azure-Samples/azure-redis-cache-rust-quickstart/) on GitHub.
 
 ## Prerequisites
 
-- Azure subscription - [create one for free](https://azure.microsoft.com/free/)
-- [Rust](https://www.rust-lang.org/tools/install) (version 1.39 or above)
-- [Git](https://git-scm.com/downloads)
+* Azure subscription - [create one for free](https://azure.microsoft.com/free/)
+* [Rust](https://www.rust-lang.org/tools/install) (version 1.39 or above)
+* [Git](https://git-scm.com/downloads)
 
 ## Create a cache
 
@@ -92,7 +92,7 @@ fn basics() {
 }
 ```
 
-The below code snippet demonstrates the functionality of a Redis `HASH` data structure. [HSET](https://redis.io/commands/hset) is invoked by using the low-level API to store information (`name`, `version`, `repo`) about Redis drivers (clients). For example, details for the Rust driver (one being used in this sample code!) is captured in form of a [BTreeMap](https://doc.rust-lang.org/std/collections/struct.BTreeMap.html) and then passed on to the low-level API. It's then retrieved by using [HGETALL](https://redis.io/commands/hgetall).
+The following code snippet demonstrates the functionality of a Redis `HASH` data structure. [HSET](https://redis.io/commands/hset) is invoked by using the low-level API to store information (`name`, `version`, `repo`) about Redis drivers (clients). For example, details for the Rust driver (one being used in this sample code!) is captured in the form of a [BTreeMap](https://doc.rust-lang.org/std/collections/struct.BTreeMap.html). Then, it's passed on to the low-level API. Finally, you retrieve it by using [HGETALL](https://redis.io/commands/hgetall).
 
 `HSET` can also be executed by using a high-level API. [hset_multiple](https://docs.rs/redis/0.19.0/redis/trait.Commands.html#method.hset_multiple) accepts an array of tuples. [hget](https://docs.rs/redis/0.19.0/redis/trait.Commands.html#method.hget) is then executed to fetch the value for a single attribute (the value for `repo`, in this case).
 
diff --git a/articles/azure-cache-for-redis/cache-web-app-howto.md b/articles/azure-cache-for-redis/cache-web-app-howto.md
@@ -12,7 +12,7 @@ ms.custom: devx-track-csharp, mvc, mode-other
 
 # Quickstart: Use Azure Cache for Redis with an ASP.NET web app
 
-In this quickstart, you use Visual Studio 2019 to create an ASP.NET web application that connects to Azure Cache for Redis to store and retrieve data from the cache. You then deploy the app to Azure App Service.
+In this quickstart, you use Visual Studio 2019 to create an ASP.NET web application that connects to Azure Cache for Redis to store and gets data from the cache. Then, you deploy the app to Azure App Service.
 
 ## Skip to the code
 
@@ -31,11 +31,11 @@ Next, you create the cache for the app.
 
 [!INCLUDE [redis-cache-access-keys](includes/redis-cache-access-keys.md)]
 
-### To edit the *CacheSecrets.config* file
+### Edit the CacheSecrets.config file
 
-1. Create a file on your computer named *CacheSecrets.config*. Put it in a location where it won't be checked in with the source code of your sample application. For this quickstart, the *CacheSecrets.config* file is located at *C:\AppSecrets\CacheSecrets.config*.
+1. Create a file on your computer named *CacheSecrets.config*. Put the file in a location where it isn't checked in with the source code of your sample application. For this quickstart, the *CacheSecrets.config* file is located at *C:\AppSecrets\CacheSecrets.config*.
 
-1. Edit the *CacheSecrets.config* file. Then, add the following content:
+1. Edit the *CacheSecrets.config* file to add the following content:
 
     ```xml
     <appSettings>
@@ -55,39 +55,39 @@ Next, you create the cache for the app.
 
 ## Update the MVC application
 
-In this section, an MVC application displays a simple test against the connection to Azure Cache for Redis.
+In this section, a model-view-controller (MVC) application displays a simple test for the connection to Azure Cache for Redis.
 
 ### How the web.config file connects to the cache
 
-When you run the application locally, the information in *CacheSecrets.config* is used to connect to your Azure Cache for Redis instance. Later, you can deploy this application to Azure. At that time, you configure an app setting in Azure that the application uses to retrieve the cache connection information instead of this file.
+When you run the application locally, the information in *CacheSecrets.config* is used to connect to your Azure Cache for Redis instance. Later, you can deploy this application to Azure. At that time, you configure an app setting in Azure that the application uses to retrieve the cache connection information instead of using the config file.
 
-Because the file *CacheSecrets.config* isn't deployed to Azure with your application, you only use it while testing the application locally. Keep this information as secure as possible to prevent malicious access to your cache data.
+Because the *CacheSecrets.config* file isn't deployed to Azure with your application, you use it only when you test  the application locally. Keep this information as secure as possible to help prevent malicious access to your cache data.
 
-#### To update the *web.config* file
+### Update the web.config file
 
-1. In **Solution Explorer**, open the *web.config* file.
+1. In Solution Explorer, open the *web.config* file.
 
      :::image type="content" source="media/cache-web-app-howto/cache-web-config.png" alt-text="Web.config":::
 
-1. In the *web.config* file, you can set the `<appSettings>` element for running the application locally.
+1. In the *web.config* file, set the `<appSettings>` element to run the application locally:
 
     `<appSettings file="C:\AppSecrets\CacheSecrets.config">`
 
 The ASP.NET runtime merges the contents of the external file with the markup in the `<appSettings>` element. The runtime ignores the file attribute if the specified file can't be found. Your secrets (the connection string to your cache) aren't included as part of the source code for the application. When you deploy your web app to Azure, the *CacheSecrets.config* file isn't deployed.
 
 ## Install StackExchange.Redis
 
-Your solution needs the `StackExchange.Redis` package to run. Install it, with this procedure:
+Your solution requires the `StackExchange.Redis` package to run. Install the `StackExchange.Redis` package by completing  this procedure:
 
-1. To configure the app to use the [StackExchange.Redis](https://github.com/StackExchange/StackExchange.Redis) NuGet package for Visual Studio, select **Tools > NuGet Package Manager > Package Manager Console**.
+1. To configure the app to use the [StackExchange.Redis](https://github.com/StackExchange/StackExchange.Redis) NuGet package for Visual Studio, select **Tools** > **NuGet Package Manager** > **Package Manager Console**.
 
-1. Run the following command from the `Package Manager Console` window:
+1. In the `Package Manager Console` window, run the following command:
 
     ```powershell
     Install-Package StackExchange.Redis
     ```
 
-1. The NuGet package downloads and adds the required assembly references for your client application to access Azure Cache for Redis with the `StackExchange.Redis` client.
+1. The NuGet package downloads and adds the required assembly references for your client application to access Azure Cache for Redis by using the `StackExchange.Redis` client.
 
 <!--
 
@@ -105,9 +105,9 @@ The connection to your cache is managed by the `RedisConnection` class. The conn
 
 ```
 
-The value of the *CacheConnection* secret is accessed using the Secret Manager configuration provider and is used as the password parameter.
+The value of the *CacheConnection* secret is accessed by using the Secret Manager configuration provider and is used as the password parameter.
 
-In `RedisConnection.cs`, you see the `StackExchange.Redis` namespace has been added to the code. This is needed for the `RedisConnection` class.
+In `RedisConnection.cs`, you see the `StackExchange.Redis` namespace was added to the code. This is needed for the `RedisConnection` class.
 
 ```csharp
 using StackExchange.Redis;
@@ -212,19 +212,19 @@ To publish the app in Azure:
     | **App name** | Use the default. | The app name is the host name for the app when it's deployed to Azure. The name might have a timestamp suffix added to it to make it unique if necessary. |
     | **Subscription** | Choose your Azure subscription. | This subscription is charged for any related hosting costs. If you have multiple Azure subscriptions, verify that the subscription that you want is selected.|
     | **Resource group** | Use the same resource group where you created the cache (for example, *TestResourceGroup*). | The resource group helps you manage all resources as a group. Later, when you want to delete the app, you can just delete the group. |
-    | **App Service plan** | Select **New**, and then create a new App Service plan named *TestingPlan*. <br />Use the same **Location** you used when creating your cache. <br />Choose **Free** for the size. | An App Service plan defines a set of compute resources for a web app to run with. |
+    | **App Service plan** | Select **New**, and then create a new App Service plan named *TestingPlan*. <br />Use the same value for **Location** that you used when you created your cache. <br />For the size, select **Free**. | An App Service plan defines a set of compute resources for a web app to run with. |
 
     :::image type="content" source="media/cache-web-app-howto/cache-create-app-service-dialog.png" alt-text="App Service dialog box":::
 
-1. After you configure the App Service hosting settings, select **Create**.
+1. After you configure the App Service host settings, select **Create**.
 
 1. In the **Output** window in Visual Studio, check to see the publishing status. After the app is published, the URL for the app appears as output:
 
    :::image type="content" source="media/cache-web-app-howto/cache-publishing-output.png" alt-text="Publishing output":::
 
 ### Add the app setting for the cache
 
-After the new app is published, add a new app setting. This setting is used to store the cache connection information.
+After the new app is published, add a new app setting. This setting stores the cache connection information.
 
 To add the app setting:
 
