Import fatfs R0.15

[z180-stamp.git] / fatfs / LICENSE.txt

diff --git a/fatfs/LICENSE.txt b/fatfs/LICENSE.txt
index bdce11892273005d8571be2f5b3b14a2ad87b880..25379e46fc4f4aef8782caee5db96e74d75b279e 100644 (file)
--- a/fatfs/LICENSE.txt
+++ b/fatfs/LICENSE.txt
@@ -21,4 +21,4 @@ FatFs has being developped as a personal project of the author, ChaN. It is free
 / by use of this software.\r
 /----------------------------------------------------------------------------*/\r
 \r
-Therefore FatFs license is one of the BSD-style licenses but there is a significant feature. FatFs is mainly intended for embedded systems. In order to extend the usability for commercial products, the redistributions of FatFs in binary form, such as embedded code, binary library and any forms without source code, does not need to include about FatFs in the documentations. This is equivalent to the 1-clause BSD license. Of course FatFs is compatible with the most of open source software licenses including GNU GPL. When you redistribute the FatFs source code with any changes or create a fork, the license can also be changed to GNU GPL, BSD-style license or any open source software license that not conflict with FatFs license.\r
+Therefore FatFs license is one of the BSD-style licenses, but there is a significant feature. FatFs is mainly intended for embedded systems. In order to extend the usability for commercial products, the redistributions of FatFs in binary form, such as embedded code, binary library and any forms without source code, do not need to include about FatFs in the documentations. This is equivalent to the 1-clause BSD license. Of course FatFs is compatible with the most of open source software licenses include GNU GPL. When you redistribute the FatFs source code with changes or create a fork, the license can also be changed to GNU GPL, BSD-style license or any open source software license that not conflict with FatFs license.\r