From e369fca10927b0a6d9223e7cbf6ce12e81280ece Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Wed, 25 Feb 2026 15:12:29 +0000
Subject: [PATCH] docs: address issue #24184 (#24216)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

## Summary
Removed time-relative language from the Synchronized file shares Known
Issues section.

## Changes
- Removed "currently" from the file share limitation statement in
`content/manuals/desktop/features/synchronized-file-sharing.md` to align
with STYLE.md guidelines about writing timelessly.

Fixes #24184

---
🤖 Generated with [cagent](https://github.com/docker/cagent)

Co-authored-by: aevesdocker <102604716+aevesdocker@users.noreply.github.com>
---
 content/manuals/desktop/features/synchronized-file-sharing.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/manuals/desktop/features/synchronized-file-sharing.md b/content/manuals/desktop/features/synchronized-file-sharing.md
index a73cf121aa..4b6eb10d76 100644
--- a/content/manuals/desktop/features/synchronized-file-sharing.md
+++ b/content/manuals/desktop/features/synchronized-file-sharing.md
@@ -82,7 +82,7 @@ In general, use your `.syncignore` file to exclude items that aren't critical to
 
 - Changes made to `.syncignore` don't lead to immediate deletions unless the file share is recreated. In other words, files that are newly ignored due to modifications in the `.syncignore` file remain in their current location, but are no longer updated during synchronization.
 
-- File share instances are currently limited to approximately 2 million files per share. For best performance, if you have a file share instance of this size, try to decompose it into multiple shares corresponding to individual bind mount locations.
+- File share instances are limited to approximately 2 million files per share. For best performance, if you have a file share instance of this size, try to decompose it into multiple shares corresponding to individual bind mount locations.
 
 - Case conflicts, due to Linux being case-sensitive and macOS/Windows only being case-preserving, display as **File exists** problems in the GUI. These can be ignored. However, if they persist, you can report the issue.