Home.md

@@ -10,7 +10,7 @@ While the VAServer can be used in its original form ([Link](http://www.virtualac
 Using the [VAServerLauncher](https://git-ce.rwth-aachen.de/vr-vis/VR-Group/vaserverlauncher) has following the advantages:
 * You don't need to (re)start the VAServer all the time manually. Even the VAServerLauncher script is (if configured correctly, see below) started automatically by Unreal.
 * The VAServerLauncher can transfer used audio files from you Unreal project to the VAServer (even in networked environments), so you don't have to do this manually. Just use audio paths relative to your Content folder. (:warning: when using packaged builds, e.g., in the CAVE, make sure to have the paths where your audio files are packed as nonUFS, so not added to the pak files, this can be configured in the project settings at ``DirectoriesToAlwaysStageAsNonUFS``).
-* This copying over is also true for VAServer ini files (e.g., having different acoustical renderers in different scenes), see [VAServerLauncher documentation](https://git-ce.rwth-aachen.de/vr-vis/VR-Group/VAServerLauncher/-/blob/master/README.md) for more information. If none is specified in the ``VAReceiverActor``, a default ini (``VARenderer.Default.ini``, in the VAServerLauncher's conf directory is used). If you want to specify your own renderer config, then copy this files into your project's content folder, rename in, adapt it accordingly and set it in the ``VAReceiverActor``
+* This copying over is also true for VAServer ini files (e.g., having different acoustical renderers in different scenes), see [VAServerLauncher documentation](https://git-ce.rwth-aachen.de/vr-vis/VR-Group/VAServerLauncher/-/blob/master/README.md) for more information. If none is specified in the ``VAReceiverActor``, a default ini (``VARenderer.Default.ini``, in the VAServerLauncher's conf directory is used). If you want to specify your own renderer config, then copy this files into your project's content folder, rename in, adapt it accordingly and set it in the ``VAReceiverActor```.
 
 If you are using the automatic VAServerLauncher either have VAServerLauncher cloned next to the folder of your project or specify the VALauncher Path in the Engine/Virtual Acoustics(VA) section of the project settings. 
 Make sure to follow the instructions which are currently in [its Readme file](https://git-ce.rwth-aachen.de/vr-vis/VR-Group/VAServerLauncher/-/blob/master/README.md).