fatfs v0.14a December 5, 2020:

- Limited number of recursive calls in f_findnext().
- Fixed old floppy disks formatted with MS-DOS 2.x and 3.x cannot be mounted.
- Fixed some compiler warnings.

documents/doc/dstat.html

@@ -25,7 +25,7 @@ DSTATUS disk_status (
 <h4>Parameter</h4>
 <dl class="par">
 <dt>pdrv</dt>
-<dd>Physical drive number to identify the target device. Always zero at single drive system.</dd>
+<dd>Physical drive number to identify the target device. Always zero in single drive system.</dd>
 </dl>
 </div>
 
@@ -37,9 +37,9 @@ DSTATUS disk_status (
 <dt>STA_NOINIT</dt>
 <dd>Indicates that the device has not been initialized and not ready to work. This flag is set on system reset, media removal or failure of <a href="dinit.html"><tt>disk_initialize</tt></a> function. It is cleared on <tt>disk_initialize</tt> function succeeded. Any media change that occurs asynchronously must be captured and reflect it to the status flags, or auto-mount function will not work correctly. If the system does not support media change detection, application program needs to explicitly re-mount the volume with <tt>f_mount</tt> function after each media change.</dd>
 <dt>STA_NODISK</dt>
-<dd>Indicates that no medium in the drive. This is always cleared at fixed disk drive. Note that FatFs does not refer this flag.</dd>
+<dd>Indicates that no medium in the drive. This is always cleared when the drive is non-removable class. Note that FatFs does not refer this flag.</dd>
 <dt>STA_PROTECT</dt>
-<dd>Indicates that the medium is write protected. This is always cleared at the drives without write protect function. Not valid if <tt>STA_NODISK</tt> is set.</dd>
+<dd>Indicates that the medium is write protected. This is always cleared when the drive has no write protect function. Not valid if <tt>STA_NODISK</tt> is set.</dd>
 </dl>
 </div>