From 76b66db9d8a4d38890d02411aaeb1f578abb9276 Mon Sep 17 00:00:00 2001
From: Alessandro Foresi <alefor@gmail.com>
Date: Sat, 11 Apr 2015 15:37:36 +0200
Subject: [PATCH] Fixed: typo, extra *

---
 .../development/setting-up-the-development-environment.md       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/development/setting-up-the-development-environment.md b/documentation/development/setting-up-the-development-environment.md
index 52e80a37a3..f484c59722 100644
--- a/documentation/development/setting-up-the-development-environment.md
+++ b/documentation/development/setting-up-the-development-environment.md
@@ -107,4 +107,4 @@ Files must exist in the built PBOs for filepatching to work. If you create a new
 
 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.
+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.