Deploying-and-Running-the-Build.md

-After installing the required Components as described in **"[1](https://github.com/DKSR-Data-Competence-for-Cities-Regions/DKSR-Open-UrbanPulse/wiki/Software-Components-Required)"**, the next step is to configure the Payara Application Server and deploying the build from [2]. 
+After installing the required Components as described in **"[1](https://github.com/DKSR-Data-Competence-for-Cities-Regions/DKSR-Open-UrbanPulse/wiki/Software-Components-Required)"**, the next step is to configure the Payara Application Server and deploying the build from **"[2](https://github.com/DKSR-Data-Competence-for-Cities-Regions/DKSR-Open-UrbanPulse/wiki/Building-the-Code)"** . 
 
 1. In a shell, change to the Payara folder under **/bin** . That is where the start scripts of Payara (cmd and sh) are.
 2. Run **asadmin start-domain** in the shell to start Payara. If everything is ok, the output will show information regarding paths Logs, Admin Port, etc. The management console should be accessible at **http://localhost:4848/**
@@ -28,7 +28,7 @@ To avoid conflicts between library versions (e.g. Hazelcast).
 
 Insert Image here
 
-11. The project can be built with **mvn clean install** (located under  /UrbanPulse/ ausführen). As a result, a *.war Datei  file is will be created at **UrbanPulse/UrbanPulseManagement/target**.
+11. The project can be built with **mvn clean install**. As a result, a *.war Datei  file is will be created at **UrbanPulse/UrbanPulseManagement/target** as described in [2](https://github.com/DKSR-Data-Competence-for-Cities-Regions/DKSR-Open-UrbanPulse/wiki/Building-the-Code)
 
 12. The file can also be deployed to Payara in Payara‘s management page, under unter **Applications -> Deploy**.