From 296c26b671e7b3d2c3433e82a1af4eb085664aad Mon Sep 17 00:00:00 2001
From: jack <9480542+jackusm@users.noreply.github.com>
Date: Sat, 8 Mar 2025 22:40:46 +0000
Subject: [PATCH] docs: fix incorrect mentions of vfs-cache-min-free-size

---
 vfs/vfs.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/vfs/vfs.md b/vfs/vfs.md
index 3d0d5622c..dde8f9f30 100644
--- a/vfs/vfs.md
+++ b/vfs/vfs.md
@@ -95,11 +95,11 @@ seconds. If rclone is quit or dies with files that haven't been
 uploaded, these will be uploaded next time rclone is run with the same
 flags.
 
-If using `--vfs-cache-max-size` or `--vfs-cache-min-free-size` note
+If using `--vfs-cache-max-size` or `--vfs-cache-min-free-space` note
 that the cache may exceed these quotas for two reasons. Firstly
 because it is only checked every `--vfs-cache-poll-interval`. Secondly
 because open files cannot be evicted from the cache. When
-`--vfs-cache-max-size` or `--vfs-cache-min-free-size` is exceeded,
+`--vfs-cache-max-size` or `--vfs-cache-min-free-space` is exceeded,
 rclone will attempt to evict the least accessed files from the cache
 first. rclone will start with files that haven't been accessed for the
 longest. This cache flushing strategy is efficient and more relevant