acro score

Author: Rami Bououni

docs/pipelines/artifacts/caching-nuget.md

@@ -20,7 +20,7 @@ With pipeline caching, you can reduce your build time by caching your dependenci
 
 ## Lock dependencies
 
-To set up the cache task, we must first lock our project's dependencies and create a **package.lock.json** file. We'll use the hash of the content of this file to generate a unique key for our cache.
+To set up the cache task, you must first lock your project's dependencies and create a **package.lock.json** file. The hash of the lock file's content will be used to generate a unique cache key.
 
 To lock your project's dependencies, set the **RestorePackagesWithLockFile** property in your *csproj* file to **true**. NuGet restore generates a lock file **packages.lock.json** at the root directory of your project. Make sure you check your **packages.lock.json** file into your source code.
 
@@ -34,7 +34,7 @@ To lock your project's dependencies, set the **RestorePackagesWithLockFile** pro
 
 We need to create a pipeline variable to point to the location of our packages on the agent running the pipeline.
 
-In this example, the content of the **packages.lock.json** will be hashed to produce a dynamic cache key. This ensures that every time the file is modified, a new cache key is generated.
+In this example, the content of the **packages.lock.json** is hashed to produce a dynamic cache key. This ensures that every time the file is modified, a new cache key is generated.
 
 :::image type="content" source="media/cache-key-hash.png" alt-text="A screenshot showing how the cache key is generated in Azure Pipelines.":::