Shorten some sentences and make other sentences more natural

README.md

@@ -31,9 +31,9 @@ Enable the layer with the environment variable.
 
 ### Lutris
 Follow these steps with Lutris:
-1. Right-click on a game and click on `Configure`.
+1. Right-click a game and click on `Configure`.
 2. Go to the `System options` tab and scroll down to `Environment variables`.
-3. Click on `Add` and add `ENABLE_VKBASALT` under `Key` and `1` under `Value`.
+3. Click `Add` and add `ENABLE_VKBASALT` under `Key` and `1` under `Value`.
 
 ### Standard
 When using the terminal or an application (.desktop) file, run:
@@ -62,7 +62,7 @@ The config file will be searched for in the locations:
 You can create a file named `vkBasalt.conf` in the game's working directory and change the values there if you want to make changes for only one game.
 
 ### ReShade FX shaders
-You need to set `reshadeTexturePath` and `reshadeIncludePath` to the matching directories from the repository to run ReShade FX shaders, e.g., shaders from the [ReShade repository](https://github.com/crosire/reshade-shaders). You need to set a custom effect name to the shader path then add that effect name to `effects` like every other effect to use a specific shader.
+You must set `reshadeTexturePath` and `reshadeIncludePath` to the matching directories from the repository to run ReShade FX shaders, like shaders from the [ReShade repository](https://github.com/crosire/reshade-shaders). You must set a custom effect name to the shader path then add that effect name to `effects` like every other effect to use a specific shader.
 ```ini
 effects = colorfulness:denoise
 
@@ -73,12 +73,12 @@ reshadeIncludePath = /home/user/reshade-shaders/Shaders
 ```
 
 ### Ingame input
-The [Home key](https://en.wikipedia.org/wiki/Home_key) can be used to disable and re-enable the applied effects. The key can also be changed in the config file. It will not work on pure Wayland; it is based on X11. But it **should** not crash without X11.
+The [Home key](https://en.wikipedia.org/wiki/Home_key) can be used to toggle the applied effects on and off. The key can also be changed in the config file. It will not work on pure Wayland; it is based on X11. But it **should** not crash without X11.
 
 ### Debug output
-The amount of debug output can be set with the `VKBASALT_LOG_LEVEL` env var, e.g., `VKBASALT_LOG_LEVEL=debug`. Valid values are: `trace, debug, info, warn, error, none`.
+The amount of debug output can be set with the `VKBASALT_LOG_LEVEL` environment variable, like `VKBASALT_LOG_LEVEL=debug`. Valid values are: `trace, debug, info, warn, error, none`.
 
-The logger outputs to stderr by default. A file as output location can be set with the `VKBASALT_LOG_FILE` env var, e.g., `VKBASALT_LOG_FILE="vkBasalt.log"`.
+The logger outputs to stderr by default. A file as output location can be set with the `VKBASALT_LOG_FILE` environment variable, like `VKBASALT_LOG_FILE="vkBasalt.log"`.
 
 ## Building from source
 
@@ -91,16 +91,16 @@ Before building, you will need:
 - X11 development files
 
 ### Building
-These instructions use `--prefix=/usr` that is generally not recommended; vkBasalt will be installed in directories that are meant for the package manager. An alternative is not setting the prefix, so it will be installed in `/usr/local`. But you need to ensure the `ld` finds the library; /usr/local is probably not in the default path.
+These instructions use `--prefix=/usr`, that is not recommended in general; vkBasalt will be installed in directories that are meant for the package manager. An alternative is not setting the prefix, so it will be installed in `/usr/local`. But you musto ensure the `ld` finds the library; /usr/local is probably not in the default path.
 
-Prefer to use distro-provided packages generally.
+Prefer to use distro-provided packages in general.
 ```
 git clone https://github.com/DadSchoorse/vkBasalt.git
 cd vkBasalt
 ```
 
 #### 32-bit
-Ensure the `PKG_CONFIG_PATH=/usr/lib32/pkgconfig` and `--libdir=lib32` are right for your distro and change them if needed. E.g., You need to replace `lib32` by `lib/i386-linux-gnu` on Debian-based distros.
+Ensure the `PKG_CONFIG_PATH=/usr/lib32/pkgconfig` and `--libdir=lib32` are right for your distro and change them if needed. E.g., you must replace `lib32` by `lib/i386-linux-gnu` on Debian-based distros.
 ```
 ASFLAGS=--32 CFLAGS=-m32 CXXFLAGS=-m32 PKG_CONFIG_PATH=/usr/lib32/pkgconfig meson setup --prefix=/usr --buildtype=release --libdir=lib32 -Dwith_json=false builddir.32
 ninja -C builddir.32 install