From 72f008c0fe6c3a8420c2d3cce83c16c91ce3eeff Mon Sep 17 00:00:00 2001
From: Sankalp Kotewar <98868223+kotewar@users.noreply.github.com>
Date: Wed, 11 Jan 2023 10:05:57 +0530
Subject: [PATCH] Update CACHING.md

Co-authored-by: Bishal Prasad <bishal-pdmsft@github.com>
---
 CACHING.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CACHING.md b/CACHING.md
index 243364c..23f5094 100644
--- a/CACHING.md
+++ b/CACHING.md
@@ -34,7 +34,7 @@ One of the most common use case is to use hash for lockfile as key. This way sam
 
 ### Using restore keys to download the closest matching cache
 
-If cache is not found matching the primary key, restore keys will be used to download the closest matching cache that was recently created. This way most of the dependencies can be downloaded from the restore key hence saving some build time.
+If cache is not found matching the primary key, restore keys can be used to download the closest matching cache that was recently created. This ensures that the build/install step will need to additionally fetch just a handful of newer dependencies, and hence saving build time.
 
 ```yaml
   - uses: actions/cache@v3