Merge pull request #1 from Flyspray/master

Merge master

Author: Psychokiller1888

_community/world-users.md

@@ -20,4 +20,5 @@ Here are just a few:
  * [Custom Tobacco](http://www.customtobacco.com)
  * [Smith & Walker Tools](http://www.smithandwalkertools.com)
  * [The Veloz Group](http://www.thevelozgroup.com)
+ * [DMXControl](http://www.dmxcontrol.de/flyspray/)
  * [Team Dakota - Project Spark](http://www.projectspark.com)

_devel/contribute.md

@@ -27,7 +27,9 @@ And make sure to add yourself to (/devel/team/)!
 
 #### Write documentation 
 
-Although we strive to make Flyspray easy to use, it's always helpful to have documentation available.  Unfortunately we don't always have time to write both the Flyspray code and the user manual, and we prefer to concentrate on the code.  All is not lost, as anyone can [checkout](/manual/writing_documentation) and edit the [User Manual](/manual). We would like users of the site to write in English.
+Although we strive to make Flyspray easy to use, it's always helpful to have documentation available.  Unfortunately we don't always have time to write both the Flyspray code and the user manual, and we prefer to concentrate on the code.  All is not lost, as anyone can [checkout](/manual/writing_documentation) and edit the [User Manual](/manual).
+
+We would like users of this page to write in English. No other languages for now, thank you.
 
 
 #### Talk to us 

_devel/security.md

@@ -44,6 +44,6 @@ Also, There are a few third party flyspray integrations that we are aware of :
   * active-factory
   * A modified version included with EGroupware.
 
-Please **do not** contact us about vulnerabilities in that products, **unless** the problem is present in **officially supported** Flyspray releases available in either the download section or in the **active branches** of our SVN repository. 
+Please **do not** contact us about vulnerabilities in that products, **unless** the problem is present in **officially supported** Flyspray releases available in either the download section or in the **active branches** of our Git repository. 
 
 We have no control of the code included in that tools.