ENGDOCS-2056 (#19763)

* ENGDOCS-2056

* Update content/compose/compose-file/05-services.md

Co-authored-by: David Karlsson <[email protected]>

* Update content/compose/compose-file/07-volumes.md

Co-authored-by: David Karlsson <[email protected]>

---------

Co-authored-by: David Karlsson <[email protected]>

Author: aevesdocker

content/compose/compose-file/05-services.md

@@ -1787,8 +1787,8 @@ expressed in the short form.
 > **Tip**
 >
 > Working with large repositories or monorepos, or with virtual file systems that are no longer scaling with your codebase? 
-> Compose now takes advantage of [Synchronized file shares](../../desktop/synchronized-file-sharing.md) and  automatically creates file shares for bind mounts. 
-> Ensure you're signed into Docker with a paid subscription and have enabled both **Access experimental features** and **Manage Synchronized file shares with Compose** in Docker Desktop's settings.
+> Compose now takes advantage of [Synchronized file shares](../../desktop/synchronized-file-sharing.md) and automatically creates file shares for bind mounts. 
+> Ensure you're signed in to Docker with a paid subscription and have enabled both **Access experimental features** and **Manage Synchronized file shares with Compose** in Docker Desktop's settings.
 { .tip }
 
 ## volumes_from

content/compose/compose-file/07-volumes.md

@@ -11,8 +11,8 @@ The top-level `volumes` declaration lets you configure named volumes that can be
 > **Tip**
 >
 > Working with large repositories or monorepos, or with virtual file systems that are no longer scaling with your codebase? 
-> Compose now takes advantage of [Synchronized file shares](../../desktop/synchronized-file-sharing.md) and  automatically creates file shares for bind mounts. 
-> Ensure you're signed into Docker with a paid subscription and have enabled both **Access experimental features** and **Manage Synchronized file shares with Compose** in Docker Desktop's settings.
+> Compose now takes advantage of [Synchronized file shares](../../desktop/synchronized-file-sharing.md) and automatically creates file shares for bind mounts. 
+> Ensure you're signed in to Docker with a paid subscription and have enabled both **Access experimental features** and **Manage Synchronized file shares with Compose** in Docker Desktop's settings.
 { .tip }
 
 ## Example

content/desktop/synchronized-file-sharing.md

@@ -54,7 +54,7 @@ When the status indicator displays **Watching for filesystem changes**, your fil
 > **Tip**
 >
 > Compose can now automatically create file shares for bind mounts. 
-> Ensure you're signed into Docker with a paid subscription and have enabled both **Access experimental features** and **Manage Synchronized file shares with Compose** in Docker Desktop's settings.
+> Ensure you're signed in to Docker with a paid subscription and have enabled both **Access experimental features** and **Manage Synchronized file shares with Compose** in Docker Desktop's settings.
 { .tip }
 
 ## Explore your file share instance
@@ -83,7 +83,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 1-1.5 million files per share. Docker plans to increase this limit to 2 million in a future release. 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 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.
 
 - 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.