diff --git a/README.html b/README.html
index 0738710..80fe75e 100644
--- a/README.html
+++ b/README.html
@@ -217,7 +217,7 @@ It features background tasks and interactive chats, and can serve as an interfac
 <p><strong>Never run your Bot as root, this is the most dangerous you can do!</strong> Usually the user 'nobody' has almost no rights on unix/linux systems. See <a href="doc/4_expert.md">Expert use</a> on how to run your Bot as an other user.</p>
 <h3>Secure your Bot installation</h3>
 <p><strong>Your Bot configuration must no be readable from other users.</strong> Everyone who can read your Bots token is able to act as your Bot and has access to all chats the Bot is in!</p>
-<p>Everyone with read access to your Bot files can extract your Bots data. Especially your Bot config in <code>vorconfig.jssh</code> must be protected against other users. No one except you should have write access to the Bot files. The Bot should be restricted to have write access to <code>count.jssh</code> and <code>data-bot-bash</code> only, all other files must be write protected.</p>
+<p>Everyone with read access to your Bot files can extract your Bots data. Especially your Bot config in <code>config.jssh</code> must be protected against other users. No one except you should have write access to the Bot files. The Bot should be restricted to have write access to <code>count.jssh</code> and <code>data-bot-bash</code> only, all other files must be write protected.</p>
 <p>To set access rights for your bashbot installation to a reasonable default run <code>sudo ./bashbot.sh init</code> after every update or change to your installation directory.</p>
 <h2>FAQ</h2>
 <h3>Is this Bot insecure?</h3>
@@ -269,6 +269,6 @@ It features background tasks and interactive chats, and can serve as an interfac
 <p>@Gnadelwartz</p>
 <h2>That's it!</h2>
 <p>If you feel that there's something missing or if you found a bug, feel free to submit a pull request!</p>
-<h4>$$VERSION$$ 0.99-1-g3daf84d</h4>
+<h4>$$VERSION$$ 0.99-2-gacf9d84</h4>
 </body>
 </html>
diff --git a/README.md b/README.md
index 0d17e4e..fdf91f2 100644
--- a/README.md
+++ b/README.md
@@ -178,7 +178,7 @@ For the same reason every file your Bot can read is in danger to be disclosed. R
 ### Secure your Bot installation
 **Your Bot configuration must no be readable from other users.** Everyone who can read your Bots token is able to act as your Bot and has access to all chats the Bot is in!
 
-Everyone with read access to your Bot files can extract your Bots data. Especially your Bot config in ```vorconfig.jssh``` must be protected against other users. No one except you should have write access to the Bot files. The Bot should be restricted to have write access to ```count.jssh``` and  ```data-bot-bash``` only, all other files must be write protected.
+Everyone with read access to your Bot files can extract your Bots data. Especially your Bot config in ```config.jssh``` must be protected against other users. No one except you should have write access to the Bot files. The Bot should be restricted to have write access to ```count.jssh``` and  ```data-bot-bash``` only, all other files must be write protected.
 
 To set access rights for your bashbot installation to a reasonable default run ```sudo ./bashbot.sh init``` after every update or change to your installation directory.
 
@@ -261,4 +261,4 @@ bashbotBlockRecover() {
 
 If you feel that there's something missing or if you found a bug, feel free to submit a pull request!
 
-#### $$VERSION$$ 0.99-1-g3daf84d
+#### $$VERSION$$ 0.99-2-gacf9d84
diff --git a/README.txt b/README.txt
index 80ca255..c4c1bb2 100644
--- a/README.txt
+++ b/README.txt
@@ -241,9 +241,9 @@ can read your Bots token is able to act as your Bot and has access to all chats
 the Bot is in!
 
 Everyone with read access to your Bot files can extract your Bots data. 
-Especially your Bot config in ```vorconfig.jssh``` must be protected against 
-other users. No one except you should have write access to the Bot files. The 
-Bot should be restricted to have write access to ```count.jssh``` and  
+Especially your Bot config in ```config.jssh``` must be protected against other 
+users. No one except you should have write access to the Bot files. The Bot 
+should be restricted to have write access to ```count.jssh``` and  
 ```data-bot-bash``` only, all other files must be write protected.
 
 To set access rights for your bashbot installation to a reasonable default run 
@@ -351,4 +351,4 @@ wait
 If you feel that there's something missing or if you found a bug, feel free to 
 submit a pull request!
 
-#### $$VERSION$$ 0.99-1-g3daf84d
+#### $$VERSION$$ 0.99-2-gacf9d84