updated grammar

content/docs/pulumi-cloud/deployments/api.md

@@ -383,7 +383,7 @@ The GitHub block describes settings for Pulumi Deployments' GitHub integration.
 
 ### CacheOptions
 
-Cache Options block defines settings related to dependency caching during Deployments. Reading dependencies from cache makes deployments significantly faster. Learn more about dependency caching on the [FAQ page](/docs/pulumi-cloud/deployments/faq/#dependencycaching).
+The Cache Options block defines settings related to dependency caching during Deployments. Using dependencies from the cache makes deployments significantly faster. Learn more about dependency caching on the [FAQ page](/docs/pulumi-cloud/deployments/faq/#dependencycaching).
 
 This option is only available for Pulumi-managed deployment agents.
 

content/docs/pulumi-cloud/deployments/faq.md

@@ -25,20 +25,20 @@ Deployments run on single-use virtual machines and compute and storage are never
 
 When using Pulumi-managed deployment agents, you have the option to speed up deployments using Dependency Caching.
 
-Caching method is simple: during the first deployment, deployment agent will automatically detect downloaded dependencies using lock files, zip them up and store the archive in blob storage. During all consequent deployments, agents will pull such an archive down and unpack it, saving time it would take to redownload those dependencies. When your dependencies change, deployment agents will automatically invalidate an old cache and create a new one.
+The caching method is simple: during the first deployment, the deployment agent will automatically detect downloaded dependencies using lock files, zip them up and store the archive in blob storage. During all subsequent deployments, agents will pull such an archive down and unpack it, saving time it would normally take to redownload those dependencies. When your dependencies change, deployment agents will automatically invalidate the old cache and create a new one.
 
-Caches are shared on project level, so all stacks within a project can share the same cache. However, caches are fully isolated and never shared between customers.
+Caches are shared on the project level, so all stacks within a project can share the same cache. However, caches are fully isolated and never shared between customers.
 
 Dependency Caching is supported for the following runtimes:
 
 - `.NET`
-- `Python` - ensure that you have `requirements.txt` file in the root of your source code.
-- `Go` - ensure that you have `go.mod` and `go.sum` files in the root of your source code.
-- `NodeJS` - ensure that you have `packageManager` field specified in `package.json` file. For now, only `npm` and `yarn` are supported.
-  - For `npm`, ensure that you have `package-lock.json` file in the root of your source code.
-  - For `yarn`, ensure that you have `yarn.lock` file in the root of your source code.
+- `Python` - ensure that you have `requirements.txt` in the root of your source code.
+- `Go` - ensure that you have `go.mod` and `go.sum` in the root of your source code.
+- `NodeJS` - ensure that you have `packageManager` field specified in `package.json`. For now, only `npm` and `yarn` are supported.
+  - For `npm`, ensure that you have `package-lock.json` in the root of your source code.
+  - For `yarn`, ensure that you have `yarn.lock` in the root of your source code.
 
-To confirm Dependency Caching is working and/or to troubleshoot, check out logs of your deployments, specifically `Restore Cache` and `Save Cache` steps.
+To confirm Dependency Caching is working and/or to troubleshoot, check out logs of your deployments, specifically the `Restore Cache` and `Save Cache` steps.
 
 ## Common recipes