Update configuration.md

documentation/builders/configuration.md

@@ -1,15 +1,15 @@
 # Jukebox Configuration
 
 The Jukebox configuration is managed by a set of files located in `shared/settings`.
-Some configuration changes can be made through the WebUI and take immediate effect.
+Some configuration changes can be made through the Web App and take immediate effect.
 
-The majority of configuration options is only available by editing the config files -
+The majority of configuration options are only available by editing the config files -
 *when the service is not running!*
 Don't fear (overly), they contain commentaries.
 
-For several aspects we have [configuration tools](../developers/coreapps.md#configuration-tools) and [detailed guides](./README.md#features).
+For several aspects, we have [configuration tools](../developers/coreapps.md#configuration-tools) and [detailed guides](./README.md#features).
 
-Even after running the tools, certain aspects can only be changed by modifying the configuration files directly.
+Even after using the tools, certain aspects can only be changed by directly modifying the configuration files.
 
 ## Best practice procedure
 
@@ -27,11 +27,10 @@ $ ./run_jukebox.sh
 # Restart the service
 $ systemctl --user start jukebox-daemon
 ```
-
-To try different configurations, you can start the Jukebox with a custom config file.
+To try different configurations, you can start the Jukebox with a custom config file. 
 This could be useful if you want your Jukebox to only allow a lower volume when started
-at night time when there is time to go to bed :-)
-The path to the custom config file must be either absolute or relativ to the folder `src/jukebox/`
+at nighttime, signaling it's time to go to bed. :-) 
+The path to the custom config file must be either absolute or relative to the folder `src/jukebox/`.
 
 ```bash
 $ ./run_jukebox.sh --conf /absolute/path/to/custom/config.yaml