Update ReadMe

Author: Abstractize

README.md

@@ -1,6 +1,6 @@
 # Drum MIDI Remapper
 
-A .NET tool for remapping MIDI drum notes between different standards and custom mappings. Designed to help musicians and producers adapt MIDI drum tracks for compatibility with various drum kits, DAWs, and hardware.
+A **.NET 9** cross-platform tool for remapping MIDI drum notes between different standards and custom mappings. Designed to help musicians and producers adapt MIDI drum tracks for compatibility with various drum kits, DAWs, and hardware.
 
 ![Build Status](https://img.shields.io/github/actions/workflow/status/Abstractize/drum-midi-remapper/ci.yml?branch=main)
 ![License](https://img.shields.io/github/license/Abstractize/drum-midi-remapper)
@@ -13,56 +13,65 @@ A .NET tool for remapping MIDI drum notes between different standards and custom
 git clone https://github.com/Abstractize/drum-midi-remapper.git
 cd drum-midi-remapper
 dotnet build
-dotnet run --project src/ClI -- GuitarPro StevenSlate midis/test.mid
+dotnet run --project src/CLI -- GuitarPro StevenSlate midis/test.mid
 ```
 
-- Replace `GuitarPro`, `StevenSlate`, and `midis/test.mid` with your desired mapping and MIDI file.
+- Replace `GuitarPro`, `StevenSlate`, and `midis/test.mid` with your desired mappings and MIDI file.
+
+---
 
 ## Requirements
 
 - [.NET 9.0 SDK or newer](https://dotnet.microsoft.com/download)
 - Compatible with Windows, macOS, and Linux
 
+---
+
 ## Features
 
-- Remap MIDI drum notes using customizable mapping files
-- Support for popular drum mapping standards (e.g., General MIDI, Roland, Yamaha) and custom mappings
-- Batch processing of MIDI files
-- Command-line interface for easy automation
-- Cross-platform support via .NET
+- Remap MIDI drum notes using customizable JSON mapping files  
+- Support for popular drum mapping standards (e.g., GuitarPro, StevenSlate, LogicPro, ProTools)  
+- Batch processing of MIDI files via CLI  
+- Cross-platform support powered by .NET 9  
+- Modular architecture with Dependency Injection for easy extensibility
+
+---
 
 ## Usage
 
-Run the tool with the following command:
+Run the tool with:
 
 ```bash
-dotnet run --project src/ClI -- <SourceMap> <TargetMap> <InputMidiFile>
+dotnet run --project src/CLI -- <SourceMap> <TargetMap> <InputMidiFile>
 ```
 
-- `<SourceMap>` and `<TargetMap>`: Mapping names (see **Available Mappings**)
-- `<InputMidiFile>`: Path to your MIDI file
+- `<SourceMap>` and `<TargetMap>`: Mapping names (see **Available Mappings** below)  
+- `<InputMidiFile>`: Path to the MIDI file to remap
 
-The `--project src/ClI` option tells `dotnet` to run the CLI project directly.
+The `--project src/CLI` option specifies the CLI project.
+
+---
 
 ## Available Mappings
 
-Mappings are stored in the **Services/Resources/Maps/** directory. Specify the mapping name as a command-line argument when running the tool.
+Mappings are stored as JSON files in the **Services/Resources/Maps/** directory. Specify the mapping name as a command-line argument when running the tool.
+
+Included mappings:
 
-**Included mappings:**
-- GuitarPro
-- LogicPro
-- ProTools
+- GuitarPro  
+- LogicPro  
+- ProTools  
 - StevenSlate
 
-You can use these standards or create your own custom mapping.
+You can also create custom mappings by adding JSON files to the directory.
 
-## Configuration
+---
 
-Mappings are defined as JSON files in the **Services/Resources/Maps/** directory. You can create or modify mapping files to suit your needs. See the sample files for format and usage.
+## Configuration
 
-### Example Mapping File
+Mapping files are JSON documents located in **Services/Resources/Maps/**. Edit or add files to customize drum note mappings.
 
-Example (**Services/Resources/Maps/ExampleMap.json**):
+### Example Mapping File (`ExampleMap.json`)
 
 ```json
 {
@@ -81,43 +90,53 @@ Example (**Services/Resources/Maps/ExampleMap.json**):
 }
 ```
 
-Customize the `"name"` and MIDI note numbers as needed for your drum kit or standard.
+- `"name"`: Identifier for the map  
+- Values correspond to MIDI note numbers
 
-> **Note:** The numbers correspond to MIDI note numbers as used by the [DryWetMIDI](https://melanchall.github.io/drywetmidi/) library.  
-> For a full list of MIDI note numbers and their corresponding drum sounds, refer to the [General MIDI Percussion Key Map](https://www.midi.org/specifications-old/item/gm-level-1-sound-set), your drum kit's documentation, or the [DryWetMIDI documentation](https://melanchall.github.io/drywetmidi/articles/notes.html).
+> **Note:** MIDI note numbers follow the [General MIDI Percussion Key Map](https://www.midi.org/specifications-old/item/gm-level-1-sound-set). This project uses [DryWetMIDI](https://melanchall.github.io/drywetmidi/) for MIDI handling.
+
+---
 
 ## Example
 
-**Input:** A MIDI file mapped for GuitarPro  
-**Command:**  
+**Input:** MIDI file mapped for GuitarPro  
+**Command:**
+
 ```bash
-dotnet run --project src/ClI -- GuitarPro StevenSlate midis/test.mid
+dotnet run --project src/CLI -- GuitarPro StevenSlate midis/test.mid
 ```
-**Output:** A MIDI file remapped for StevenSlate drums.
+
+**Output:** MIDI file remapped for StevenSlate drums, saved in the current working directory.
+
+---
 
 ## Troubleshooting & FAQ
 
-- **Build errors:** Ensure you have the correct .NET SDK installed.
-- **Mapping not found:** Check the spelling and existence of your mapping file in **Services/Resources/Maps/**.
-- **MIDI file issues:** Verify your input file is a valid MIDI file.
+- **Build errors:** Ensure .NET 9 SDK is installed and your environment is configured correctly.  
+- **Mapping not found:** Verify spelling and that JSON mapping files exist in **Services/Resources/Maps/**.  
+- **MIDI file issues:** Confirm your input file is a valid MIDI file and accessible.
+
+---
 
 ## Contributing
 
 Contributions are welcome! Please open issues or submit pull requests.
 
 ### Adding a New Mapping
 
-1. Create a new JSON mapping file in the **Services/Resources/Maps/** directory.
-2. Add your mapping details following the format shown above.
-3. Update the mapping enum in `Models/DrumMapType.cs` to include your new mapping.
-4. Submit a pull request with your changes.
+1. Add a JSON mapping file to **Services/Resources/Maps/**  
+2. Follow the existing file format for your mapping  
+3. Update the `DrumMapType` enum in `Models/DrumMapType.cs` to include your new map  
+4. Submit a pull request
 
-This helps keep all mappings organized and available for everyone.
+---
 
 ## Related Projects
 
-- [DryWetMIDI](https://melanchall.github.io/drywetmidi/) - MIDI processing library used by this tool
+- [DryWetMIDI](https://melanchall.github.io/drywetmidi/) — MIDI processing library used by this tool
+
+---
 
 ## License
 
-MIT License
+MIT License