diff --git a/wiki/development/setting-up-the-development-environment.md b/wiki/development/setting-up-the-development-environment.md
index f81e06b6118..bcc04940c1c 100644
--- a/wiki/development/setting-up-the-development-environment.md
+++ b/wiki/development/setting-up-the-development-environment.md
@@ -45,18 +45,9 @@ Should the script fail, here is how you create the required links manually:
 
 First, to set up the links, create `z` folders both in your Arma 3 directory and on your P-drive. Then run the following commands as admin, replacing the text in brackets with the appropriate paths:
 
-Windows 8:
-
-```sh
-mklink /D /J "[Arma 3 installation folder]\z\ace" "[location of the ACE3 project]"
-mklink /D /J "P:\z\ace" "[location of the ACE3 project]"
-```
-
-Windows 7 and Vista:
-
 ```sh
-mklink /D "[Arma 3 installation folder]\z\ace" "[location of the ACE3 project]"
-mklink /D "P:\z\ace" "[location of the ACE3 project]"
+mklink /J "[Arma 3 installation folder]\z\ace" "[location of the ACE3 project]"
+mklink /J "P:\z\ace" "[location of the ACE3 project]"
 ```
 
 Then, copy the `cba` folder from the `tools` folder to `P:\x\cba`. Create the `x` folder if needed. That folder contains the parts of the CBA source code that are required for the macros to work.
@@ -117,6 +108,6 @@ Starting from version 1.50, Arma 3 was changed to disable file patching by defau
 
 Files must exist in the built PBOs for file patching to work. If you create a new file you must rebuild the PBO or Arma will not find it in your file paths.
 
-Configs are not patched during run time, only at load time. You do not have have to rebuild a PBO to make config changes, just restart Arma. You can get around this though if you are on the dev branch of Arma 3 and running the [diagnostic exe](https://community.bistudio.com/wiki/Arma_3_Diagnostics_Exe). That includes `diag_mergeConfigFile` which takes a full system path (as in `diag_mergeConfigFile  ["p:\z\ace\addons\my_module\config.cpp"]`) and allows you selectively reload config files.
+Configs are not patched during run time, only at load time. You do not have have to rebuild a PBO to make config changes, just restart Arma. You can get around this though if you are on the dev branch of Arma 3 and running the diagnostic exe. That includes `diag_mergeConfig` which takes a full system path (as in `p:\z\ace\addons\my_module\config.cpp`) and allows you selectivly reload config files.
 
 If you need to add/remove files, then you'll need to run build.py again without the game running, and restart. That is all that is required to add new files to then further use in testing.