Changes in 5da352e: Updated racecommittee app administrator (markdown)

				wiki/racecommittee-app-administrator.md
			
          @@ -16,12 +16,14 @@ First you need to enter a device identifier. It is a good idea to label the devi

           <img src="/wiki/images/rcapp/admin_config_step_2.png" />

          -You need to assign this identifier to the target device. Click on **QR-Sync**, recheck the current identifier and ensure that the Server URL is the correct server the device should be talking to. When done with your modifications hit **Generate**.

          +You need to assign this identifier to the target device. Click on **QR-Sync**, recheck the current identifier and ensure that the Server URL is the correct server the device should be talking to.

           <img src="/wiki/images/rcapp/admin_config_step_3.png" />

           Fire up the RaceCommittee app on the target device. Go to the **settings view** by clicking on the options overflow button (top right corner) or your device's menu button. Select the preference category **General** and click on **Synchronize connection settings**. Scan the barcode shown in the AdminConsole (if you don't have a barcode app installed the RaceCommittee App should redirect you to the Google Play Store offering an app). The **Device Identifier** and **Webservice URL** preferences should reflect the changes made.

          +_Hint: if you don't have the app installed yet on the target device, use the QR-Code as an URL to download the app for the first time. This should work with any barcode scanner app._

          +

           <img src="/wiki/images/rcapp/admin_config_step_3a.png" /> <img src="/wiki/images/rcapp/admin_config_step_3b.png" />

           After the server URL has been updated the app will check the server whether it should auto-update itself or not. To ensure that your app is compatible with the server you should choose to install the APK provided by the server. Follow the instructions on the screen and reopen the newly updated app. After the update you must re-synchronize your device with the server.

...	...	@@ -16,12 +16,14 @@ First you need to enter a device identifier. It is a good idea to label the devi
16	16
17	17	<img src="/wiki/images/rcapp/admin_config_step_2.png" />
18	18
19		-You need to assign this identifier to the target device. Click on QR-Sync, recheck the current identifier and ensure that the Server URL is the correct server the device should be talking to. When done with your modifications hit Generate.
	19	+You need to assign this identifier to the target device. Click on QR-Sync, recheck the current identifier and ensure that the Server URL is the correct server the device should be talking to.
20	20
21	21	<img src="/wiki/images/rcapp/admin_config_step_3.png" />
22	22
23	23	Fire up the RaceCommittee app on the target device. Go to the settings view by clicking on the options overflow button (top right corner) or your device's menu button. Select the preference category General and click on Synchronize connection settings. Scan the barcode shown in the AdminConsole (if you don't have a barcode app installed the RaceCommittee App should redirect you to the Google Play Store offering an app). The Device Identifier and Webservice URL preferences should reflect the changes made.
24	24
	25	+_Hint: if you don't have the app installed yet on the target device, use the QR-Code as an URL to download the app for the first time. This should work with any barcode scanner app._
	26	+
25	27	<img src="/wiki/images/rcapp/admin_config_step_3a.png" /> <img src="/wiki/images/rcapp/admin_config_step_3b.png" />
26	28
27	29	After the server URL has been updated the app will check the server whether it should auto-update itself or not. To ensure that your app is compatible with the server you should choose to install the APK provided by the server. Follow the instructions on the screen and reopen the newly updated app. After the update you must re-synchronize your device with the server.