From 4091173cceea8f2c3b0cdbc19a1adb6bd87c0a94 Mon Sep 17 00:00:00 2001 From: Javier Date: Sun, 19 Feb 2023 17:49:28 +0100 Subject: fix typos in README --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 4816e89..e51ee47 100644 --- a/README.md +++ b/README.md @@ -314,13 +314,13 @@ and a 3 letter hash of the filename. For example, `LONG FILE NAME.TXT` will become `LONG~20B.TXT`. These behave like normal files otherwise. The use of hashes allow the short file names to be consistent between reboots -of the guest OS, even if the host OS does not have support to store long these +of the guest OS, even if the host OS does not have support to persist these short file names. If your host OS does have support for storing persistent -short file names and want to use those instead of the autogenerated ones, +short file names and you want to use those instead of the autogenerated ones, consider using the option `/host` when mounting a shared folder. If you have a directory with lots of similarly names files, it may help to reduce -the chances of a hash collision by increase the number of letters dedicated to the -hash portion of the short file names. For that, use the `/hash ` option. +the chances of a hash collision by increasing the number of digits dedicated to the +hash portion of short file names. For that, use the `/hash ` option. In addition, there is support for translation of extended characters from the host filesystem into the guest DOS' codepage. -- cgit v1.2.3