Update user-shares.md

Trying to make minimum free space more clear

docs/unraid-os/manual/shares/user-shares.md

@@ -50,7 +50,7 @@ This parameter must be used when the fill-up allocation method is configured, or
 
 :::
 
-When Unraid receives a request to store a file, say for example `file.eg`, it has no idea how big the file is. Unraid will pick a spot to place it and begin to store the file data as the data is transferred over the network. Now, this may result in Unraid picking a storage disk with insufficient storage space for the complete file. Unraid is unaware there isn't enough space when it first places the file so it will only find out when the disk is full. At this point, the transfer will fail with a 'disk full' error. So, Unraid will write to a different disk if the minimum free space is set to a value larger than the biggest file size you will ever transfer.
+When Unraid receives a request to store a file, say for example `file.eg`, it has no idea how big the file is. Unraid will pick a spot to place it and begin to store the file data as the data is transferred over the network. Now, this may result in Unraid picking a storage disk with insufficient storage space for the complete file. Unraid is unaware there isn't enough space when it first places the file so it will only find out when the disk is full. At this point, the transfer will fail with a 'disk full' error. So, if the **Minimum free space** setting is appropriately set to a value larger than the biggest file size you will ever transfer, and any disk has less available space than that setting during a file transfer, Unraid will write to a different disk.
 
 We recommend setting the value to twice the size of the largest file you will ever transfer. For example, if the largest file you have is 8GB in size then set the minimum free space to 16GB. This allows you to transfer files that may vary in size somewhat and not accidentally transfer one too large.