Update README.md

Author: Capella87

README.md

@@ -1,5 +1,5 @@
 # fnorm - FixNormalization
-Fix Unicode normalization in filenames.
+Fix Unicode normalization of filename.
 
 > [!IMPORTANT]
 > This software is in development. It may contains unknown or potential bugs and unexpected behaviors. If you find or encounter those, Open an issue at this repository and describe it.
@@ -10,14 +10,14 @@ Fix Unicode normalization in filenames.
 It is especially useful when you met <ins>a nasty messed filename</ins> including characters which can be decomposed after moving files from macOS (or Darwin based-OSes) to Windows or Linux.
 (e.g. 한글 -> ᄒ​ᅡ​ᆫᄀ​ᅳ​ᆯ). In particular in Hangul, it has been considered really notorious problem among people who need to communicate files with different OSes.
 
-This problem is derived from discrepancy in processing Unicode characters between Darwin (**macOS**, iPadOS, iOS, tvOS, watchOS, visionOS) and others, because HFS+, a filesystem that once Apple had been applied in their OSes, uses Normalization D to save filenames in UTF-16.
-Although APFS(Apple File System), a newer file system recognizes and preserves normalization types, but files or directories created in those environments still have Form-D typed filename. This is why the problem persists...
+This problem is derived from discrepancy in processing Unicode characters between Darwin (**macOS**, iPadOS, iOS, tvOS, watchOS and visionOS) and others, because HFS+, a filesystem that Apple had conducted in their OSes, uses Normalization D to save filename in UTF-16.
+Although APFS(Apple File System), a newer file system can recognize and keep filename's normalization types, but files or directories created in those environments still have Form D filename. This is why the problem persists...
 
 Other characters, such as diacritics, they seem to be shown correctly with subtly behavior in Windows anyway, but Hangul characters are NOT at all. Read [an article](https://devblogs.microsoft.com/oldnewthing/20201009-00/?p=104351) regarding this issue in detail.
 
 Although this is a file system problem and limited to only filename, so manual renaming is a solution, but it is really time-consuming when you have a lot of files.
 
-That's why I made this humble tool.
+That's why I made this simple tool with .NET.
 
 ## Installation
 
@@ -36,7 +36,7 @@ That's because Windows still uses MBCS(Multi-Byte Character Set) as a default en
 But this option can be problematic in some programs which forces or are sticked to specific encoding. (e.g. MapleStory, Fallout: New Vegas)
 You can also make a workaround by type ```chcp 65001``` to set UTF-8 encoding in the console section prior to executing this program.
 
-I recommend to run the program in Windows Terminal with PowerShell 7.
+I recommend to run this program in Windows Terminal with PowerShell 7.
 
 ### Scoop
 
@@ -77,10 +77,12 @@ It is still in development that fnorm will support recursive search in directori
 ```nfc``` or ```formc``` **[Default]**
 
 Convert filenames to follow Normalization Form C. If you don't specify ```--form``` option, it will be automatically set to ```nfc```.
+Windows and Linux normally use this form.
 
 ```nfd``` or ```formd```
 
 Convert filenames to follow Normalization Form D. In general cases you don't have to care about this option.
+macOS or any Apple's operating systems are using this form.
 
 ### ```--recursive``` or ```-r```
 
@@ -97,4 +99,4 @@ This software is distributed under MIT License. I don't have any responsibility
 
 ---
 
-Copyright (c) 2024-2025 **Capella87**. Distributed under MIT License.
+Copyright © 2024-2026 **Capella87**. Distributed under MIT License.