From d270a17a94c0600d65930a99d2e451e47262c991 Mon Sep 17 00:00:00 2001
From: Warren Parad <5056218+wparad@users.noreply.github.com>
Date: Tue, 23 Jan 2024 22:13:33 +0100
Subject: [PATCH] Fix confusing note, and clarity what is being cached

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 6b2c3e8e0..8a273bf62 100644
--- a/README.md
+++ b/README.md
@@ -124,7 +124,7 @@ The action has a built-in functionality for caching and restoring dependencies.
 
 The action defaults to search for the dependency file (`package-lock.json`, `npm-shrinkwrap.json` or `yarn.lock`) in the repository root, and uses its hash as a part of the cache key. Use `cache-dependency-path` for cases when multiple dependency files are used, or they are located in different subdirectories.
 
-**Note:** The action does not cache `node_modules`
+**Note:** The action does not cache the local `node_modules` directly, but instead [caches the global cache](https://github.com/actions/setup-node/blob/main/docs/advanced-usage.md#caching-packages-data) at the machine level.
 
 See the examples of using cache for `yarn`/`pnpm` and `cache-dependency-path` input in the [Advanced usage](docs/advanced-usage.md#caching-packages-data) guide.