README: use a fork (#786)

Author: plata

README.md

@@ -3,23 +3,25 @@
 [![Crowdin Badge](https://d322cqt584bo4o.cloudfront.net/phoenicis-scripts/localized.svg)](https://crowdin.com/project/phoenicis-scripts)
 
 # How to add a script
-1. Clone this repository
+1. Fork this repository, create a new branch and clone it 
     ```
-    git clone https://github.com/PhoenicisOrg/scripts.git
+    git clone https://github.com/<user>/scripts.git
+    cd scripts
+    git checkout <branch>
     ```
 
 2. Add the local checkout as a local repository in Phoenicis (see [instructions](https://phoenicisorg.github.io/phoenicis/Users/repository/#local-directory))
 
 3. Select the right category for the application
-  * Accessories
-  * Development
-  * Games
-  * Graphics
-  * Internet
-  * Multimedia
-  * Office
-  * Other
-  * Science
+    * Accessories
+    * Development
+    * Games
+    * Graphics
+    * Internet
+    * Multimedia
+    * Office
+    * Other
+    * Science
   
 4. Create a new folder for your script inside that category. The folder structure should be:
     ```
@@ -38,31 +40,31 @@
     Even if the application name contains ®, ™ or the like, you should not use it in the folder name.
 
 5. Fill the files:
-  * [script.js](https://phoenicisorg.github.io/scripts/Develop/script-js/): actual installation script
-  * [script.json](https://phoenicisorg.github.io/scripts/Develop/script-json/): describes the installation script
-  ```json
-  {
+    * [script.js](https://phoenicisorg.github.io/scripts/Develop/script-js/): actual installation script
+    * [script.json](https://phoenicisorg.github.io/scripts/Develop/script-json/): describes the installation script
+        ```json
+        {
 		"scriptName": "Online",
 		"compatibleOperatingSystems": ["MACOSX", "LINUX"],
 		"testingOperatingSystems": [],
 		"free": true,
 		"requiresPatch": false
-  }
-  ```
-  * main.png: application icon (400px x 300px)
-  * [application.json](https://phoenicisorg.github.io/scripts/Develop/application-json/): describes the application
-  ```json
-  {
+        }
+        ```
+    * main.png: application icon (400px x 300px)
+    * [application.json](https://phoenicisorg.github.io/scripts/Develop/application-json/): describes the application
+        ```json
+        {
  		"name":	"Steam",
 		"description": "Application description"
-  }
-  ```
+        }
+        ```
   
-  6. Verify changes:
-  * Ensure that the changes fulfill the code quality requirements and the files are formatted correctly (see [tools](https://phoenicisorg.github.io/scripts/General/tools/)).
+6. Verify changes:
+    * Ensure that the changes fulfill the code quality requirements and the files are formatted correctly (see [tools](https://phoenicisorg.github.io/scripts/General/tools/)).
   
-  7. Create a pull request:
-  * Please create one pull request per script if you want to commit multiple scripts.
-  * use the following naming convention  
-       * for a new script: "Add \<application name\>" (e.g. "Add 7-zip")
-       * for an updated script: "Update \<application name\> \<what changed\>" (e.g. "Update 7-zip to use Wine 2.1")
+7. Create a pull request:
+    * Please create one pull request per script if you want to commit multiple scripts.
+    * use the following naming convention  
+        * for a new script: "Add \<application name\>" (e.g. "Add 7-zip")
+        * for an updated script: "Update \<application name\> \<what changed\>" (e.g. "Update 7-zip to use Wine 2.1")