Improved format in readmes

RGB.NET.Devices.Asus/README.md

@@ -8,6 +8,6 @@ surface.Load(AsusDeviceProvider.Instance);
 ```
 
 # Required SDK
-This providers requires the `Interop.AuraServiceLib.dll` to be present on the system. Normally this dll is installed with ASUS Aura and registered in the GAC.
-There are some known issue with this dll missing and it's recommended to pack it with your application. You can get it from your Aura-Installation or get a copy from [https://redist.arge.be/Asus/Interop.AuraServiceLib.dll](https://redist.arge.be/Asus/Interop.AuraServiceLib.dll).
+This providers requires the `Interop.AuraServiceLib.dll` to be present on the system. Normally this dll is installed with ASUS Aura and registered in the GAC.   
+There are some known issue with this dll missing and it's recommended to pack it with your application. You can get it from your Aura-Installation or get a copy from [https://redist.arge.be/Asus/Interop.AuraServiceLib.dll](https://redist.arge.be/Asus/Interop.AuraServiceLib.dll).   
 If packed it has to be located in a spot that your application is loading runtime dlls from.

RGB.NET.Devices.CoolerMaster/README.md

@@ -8,7 +8,7 @@ surface.Load(CoolerMasterDeviceProvider.Instance);
 ```
 
 # Required SDK
-This providers requires native SDK-dlls.
+This providers requires native SDK-dlls.   
 You can get them directly from Cooler Master at [https://templates.coolermaster.com/](https://templates.coolermaster.com/) (Direct Link: [https://templates.coolermaster.com/assets/sdk/coolermaster-sdk.zip](https://templates.coolermaster.com/assets/sdk/coolermaster-sdk.zip))
 
 Since the SDK-dlls are native it's important to use the correct architecture you're building your application for. (If in doubt you can always include both.)

RGB.NET.Devices.Corsair/README.md

@@ -8,7 +8,7 @@ surface.Load(CorsairDeviceProvider.Instance);
 ```
 
 # Required SDK
-This providers requires native SDK-dlls.
+This providers requires native SDK-dlls.   
 You can get them directly from Corsair at [https://github.com/CorsairOfficial/cue-sdk/releases](https://github.com/CorsairOfficial/cue-sdk/releases)
 
 Since the SDK-dlls are native it's important to use the correct architecture you're building your application for. (If in doubt you can always include both.)

RGB.NET.Devices.Logitech/README.md

@@ -7,11 +7,11 @@ This provider follows the default pattern and does not require additional setup.
 surface.Load(LogitechDeviceProvider.Instance);
 ```
 
-Since the logitech SDK does not provide device information only known devices will work.
+Since the logitech SDK does not provide device information only known devices will work.   
 You can add detection for additional devices by adding entires for them to the respective static `DeviceDefinitions` on the `LogitechDeviceProvider`.
 
 # Required SDK
-This providers requires native SDK-dlls.
+This providers requires native SDK-dlls.   
 You can get them directly from Logitech at [https://www.logitechg.com/en-us/innovation/developer-lab.html](https://www.logitechg.com/en-us/innovation/developer-lab.html) (Direct Link: [https://www.logitechg.com/sdk/LED_SDK_9.00.zip](https://www.logitechg.com/sdk/LED_SDK_9.00.zip))
 
 Since the SDK-dlls are native it's important to use the correct architecture you're building your application for. (If in doubt you can always include both.)

RGB.NET.Devices.Msi/README.md

@@ -8,7 +8,7 @@ surface.Load(MsiDeviceProvider.Instance);
 ```
 
 # Required SDK
-This providers requires native SDK-dlls.
+This providers requires native SDK-dlls.   
 You can get them directly from Msi at [https://de.msi.com/Landing/mystic-light-rgb-gaming-pc/download](https://de.msi.com/Landing/mystic-light-rgb-gaming-pc/download) (Direct Link: [https://download.msi.com/uti_exe/Mystic_light_SDK.zip](https://download.msi.com/uti_exe/Mystic_light_SDK.zip))
 
 Since the SDK-dlls are native it's important to use the correct architecture you're building your application for. (If in doubt you can always include both.)

RGB.NET.Devices.Razer/README.md

@@ -7,7 +7,7 @@ This provider follows the default pattern and does not require additional setup.
 surface.Load(RazerDeviceProvider.Instance);
 ```
 
-Since the Razer SDK does not provide device information only known devices will work.
+Since the Razer SDK does not provide device information only known devices will work.   
 You can add detection for additional devices by adding entires for them to the respective static `DeviceDefinitions` on the `RazerDeviceProvider`.
 
 # Required SDK

RGB.NET.Devices.SteelSeries/README.md

@@ -7,7 +7,7 @@ This provider follows the default pattern and does not require additional setup.
 surface.Load(SteelSeriesDeviceProvider.Instance);
 ```
 
-Since the Steel Series SDK does not provide device information only known devices will work.
+Since the Steel Series SDK does not provide device information only known devices will work.   
 You can add detection for additional devices by adding entires for them to the respective static `DeviceDefinitions` on the `SteelSeriesDeviceProvider`.
 
 # Required SDK

RGB.NET.Devices.Wooting/README.md

@@ -8,7 +8,7 @@ surface.Load(WootingDeviceProvider.Instance);
 ```
 
 # Required SDK
-This providers requires native SDK-dlls.
+This providers requires native SDK-dlls.   
 You can get them directly from Wooting at [https://github.com/WootingKb/wooting-rgb-sdk/releases](https://github.com/WootingKb/wooting-rgb-sdk/releases)
 
 Since the SDK-dlls are native it's important to use the correct architecture you're building your application for. (If in doubt you can always include both.)