Fixed IOT session readme.

Sessions/iot/CognitiveServicesExample/CS/README.md

@@ -19,11 +19,11 @@ You will need your device's IP address when connecting to it remotely.
 
     Note that we call the app CogntiveServicesExample. You can name it something different, but you will have to adjust sample code that references CognitiveServicesExample as well.
 
-    <img src="../../../Resources/images/CognitiveServicesExample/new_project.png">
+    <img src="../../Resources/images/CognitiveServicesExample/new_project.png">
 
     If this is the first project you create, Visual Studio will likely prompt you to enable [developer mode for Windows 10](https://msdn.microsoft.com/library/windows/apps/xaml/dn706236.aspx)
 
-    <img src="../../../Resources/images/CognitiveServicesExample/add_reference.png">
+    <img src="../../Resources/images/CognitiveServicesExample/add_reference.png">
 
 
 ## Add a reference to the Windows IoT extension SDK
@@ -93,7 +93,7 @@ To view the entire UI, change the dropdown in the top left corner from '5\" Phon
 
 In the UI mock up, double click on the "Detect Emotions" button. You will see a "Click="button_Clicked" added into the button in your XAML code. You will also be redirected to the .xaml.cs file with a new function called "button_Clicked()" created for you. This function will handle the Cognitive Services calls after a user presses the button.
 
-<img src="../../../Resources/images/CognitiveServicesExample/event_handler1.png">
+<img src="../../Resources/images/CognitiveServicesExample/event_handler1.png">
 
 ## Get the Emotion API Key
 ___
@@ -103,7 +103,7 @@ ___
 
     You should now see two API keys available for use for 30 days.
     
-    <img src="../../../Resources/images/CognitiveServicesExample/cogserv_signup.png">
+    <img src="../../Resources/images/CognitiveServicesExample/cogserv_signup.png">
 
 2.  Azure Subscription
 
@@ -112,7 +112,7 @@ ___
     After it deploys, click on the **"Show access keys..."** link under the "Essentials" window to see your access keys.
 
 
-    <img src="../../../Resources/images/CognitiveServicesExample/azure_cogserv_create.png">
+    <img src="../../Resources/images/CognitiveServicesExample/azure_cogserv_create.png">
 
 
 ## Add the C# Code
@@ -405,7 +405,7 @@ The fourth method places a rectangle around each face detected in the image. Sin
 
 Download the face rectangle and add it to your Assets folder within your project
 
-<img src="../../../Resources/images/CognitiveServicesExample/add_rectangle.png">
+<img src="../../Resources/images/CognitiveServicesExample/add_rectangle.png">
 
 ## Build and Test your app locally
 ___
@@ -415,7 +415,7 @@ ___
 
 Change the URL for a different image, or just click "Detect Emotion" to run the Emotion Recognizer with the default image. After a few seconds, the results should appear in your app window as expected: the image with rectangles on it on the left and more detailed emotion output for each face on the right.
 
-<img src="../../../Resources/images/CognitiveServicesExample/running_app.png">
+<img src="../../Resources/images/CognitiveServicesExample/running_app.png">
 
 
 In this case, the order is based on depth: **faces closer to the front will be first, and faces farther away will be last in the list.**
@@ -432,7 +432,7 @@ ___
 
 2.  At this point, Visual Studio will present the 'Remote Connections' dialog. Put the IP address or name of your IoT Core device (in this example, we're using 'my-device') and select **Universal (Unencrypted Protocol)** for Authentication Mode. Click **Select**.
 
-    <img src="../../../Resources/images/CognitiveServicesExample/remote_connection.png">
+    <img src="../../Resources/images/CognitiveServicesExample/remote_connection.png">
 
     > Couple of notes:
     >
@@ -440,7 +440,7 @@ ___
     >
     > 2. You can verify and/or modify these values navigating to the project properties (select 'Properties' in the Solution Explorer) and choose the 'Debug' tab on the left:
     >
-    > <img src="../../../Resources/images/CognitiveServicesExample/cs-debug-project-properties.png">
+    > <img src="../../Resources/images/CognitiveServicesExample/cs-debug-project-properties.png">
 
 3.  Now you're ready to deploy to the remote IoT Core device. Press F5 (or select **Debug \| Start Debugging**) to start debugging our app. You should see the app come up in IoT Core device screen, and you should be able to perform the same functions you did locally. To stop the app, press on the 'Stop Debugging' button (or select Debug \| Stop Debugging).
 

Sessions/iot/HelloBlinky/CS/README.md

@@ -22,7 +22,7 @@ You’ll need a few components:
 
 *   a breadboard and a couple of connector wires
 
-![Electrical Components](../../../Resources/images/Blinky/components.png)
+![Electrical Components](../../Resources/images/Blinky/components.png)
 
 ### For Raspberry Pi 2 or 3 (RPi2 or RPi3)
 
@@ -33,11 +33,11 @@ You’ll need a few components:
 
 And here is the pinout of the RPi2 and RPi3:
 
-![](../../../Resources/images/PinMappings/RP2_Pinout.png)
+![](../../Resources/images/PinMappings/RP2_Pinout.png)
 
 Here is an example of what your breadboard might look like with the circuit assembled:
 
-![Image made with Fritzing(http://fritzing.org/)](../../../Resources/images/Blinky/breadboard_assembled_rpi2_kit.jpg)
+![Image made with Fritzing(http://fritzing.org/)](../../Resources/images/Blinky/breadboard_assembled_rpi2_kit.jpg)
 
 ### For MinnowBoard Max (MBM)
 
@@ -45,17 +45,17 @@ We will connect the one end of the LED to GPIO 5 (pin 18 on the JP1 expansion he
 
 And here is the JP1 connector on the MBM:
 
-![](../../../Resources/images/PinMappings/MBM_Pinout.png)
+![](../../Resources/images/PinMappings/MBM_Pinout.png)
 
 Here is an example of what your breadboard might look like with the circuit assembled:
 
-![Image made with Fritzing(http://fritzing.org/)](../../../Resources/images/Blinky/breadboard_assembled.png)
+![Image made with Fritzing(http://fritzing.org/)](../../Resources/images/Blinky/breadboard_assembled.png)
 
 ### For DragonBoard 410c (DB)
 
 For reference, the functionality of the low-speed expansion connector is outlined in the following diagram
 
-![](../../../Resources/images/PinMappings/DB_Pinout.png)
+![](../../Resources/images/PinMappings/DB_Pinout.png)
 
 Perform the following steps to create the circuit:
 
@@ -66,7 +66,7 @@ Perform the following steps to create the circuit:
 
 Here is an illustration of what your breadboard might look like with the circuit assembled:
 
-![Image made with Fritzing(http://fritzing.org/)](../../../Resources/images/Blinky/breadboard_assembled_db_kit.png)
+![Image made with Fritzing(http://fritzing.org/)](../../Resources/images/Blinky/breadboard_assembled_db_kit.png)
 
 Finally, the LED_PIN variable of _MainPage.xaml.cs_ file of the sample code will need the following modification:
 
@@ -80,19 +80,19 @@ Finally, the LED_PIN variable of _MainPage.xaml.cs_ file of the sample code will
 
 2.  Next, in the Visual Studio toolbar, click on the `Local Machine` dropdown and select `Remote Machine`
 
-    ![RemoteMachine Target](../../../Resources/images/AppDeployment/cs-remote-machine-debugging.png)
+    ![RemoteMachine Target](../../Resources/images/AppDeployment/cs-remote-machine-debugging.png)
 
 3.  At this point, Visual Studio will present the **Remote Connections** dialog. If you previously used [PowerShell](https://docs.microsoft.com/en-us/windows/iot-core/connect-your-device/powershell) to set a unique name for your device, you can enter it here (in this example, we’re using **my-device**). Otherwise, use the IP address of your Windows IoT Core device. After entering the device name/IP select `Universal` for Windows Authentication, then click **Select**.
 
-    ![Remote Machine Debugging](../../../Resources/images/AppDeployment/cs-remote-connections.PNG)
+    ![Remote Machine Debugging](../../Resources/images/AppDeployment/cs-remote-connections.PNG)
 
 4.  You can verify or modify these values by navigating to the project properties (select **Properties** in the Solution Explorer) and choosing the `Debug` tab on the left:
 
-    ![Project Properties Debug Tab](../../../Resources/images/AppDeployment/cs-debug-project-properties.PNG)
+    ![Project Properties Debug Tab](../../Resources/images/AppDeployment/cs-debug-project-properties.PNG)
 
 When everything is set up, you should be able to press F5 from Visual Studio. If there are any missing packages that you did not install during setup, Visual Studio may prompt you to acquire those now. The Blinky app will deploy and start on the Windows IoT device, and you should see the LED blink in sync with the simulation on the screen.
 
-![](../../../Resources/images/Blinky/blinky-screenshot.png)
+![](../../Resources/images/Blinky/blinky-screenshot.png)
 
 Congratulations! You controlled one of the GPIO pins on your Windows IoT device.
 

Sessions/iot/HelloBlinky/Cpp/README.md

@@ -22,7 +22,7 @@ You’ll need a few components:
 
 *   a breadboard and a couple of connector wires
 
-![Electrical Components](../../../Resources/images/Blinky/components.png)
+![Electrical Components](../../Resources/images/Blinky/components.png)
 
 ### For Raspberry Pi 2 or 3 (RPi2 or RPi3)
 
@@ -33,11 +33,11 @@ You’ll need a few components:
 
 And here is the pinout of the RPi2 and RPi3:
 
-![](../../../Resources/images/PinMappings/RP2_Pinout.png)
+![](../../Resources/images/PinMappings/RP2_Pinout.png)
 
 Here is an example of what your breadboard might look like with the circuit assembled:
 
-![Image made with Fritzing(http://fritzing.org/)](../../../Resources/images/Blinky/breadboard_assembled_rpi2_kit.jpg)
+![Image made with Fritzing(http://fritzing.org/)](../../Resources/images/Blinky/breadboard_assembled_rpi2_kit.jpg)
 
 ### For MinnowBoard Max (MBM)
 
@@ -45,17 +45,17 @@ We will connect the one end of the LED to GPIO 5 (pin 18 on the JP1 expansion he
 
 And here is the JP1 connector on the MBM:
 
-![Minnowboard Max Pinout](../../../Resources/images/PinMappings/MBM_Pinout.png)
+![Minnowboard Max Pinout](../../Resources/images/PinMappings/MBM_Pinout.png)
 
 Here is an example of what your breadboard might look like with the circuit assembled:
 
-![Image made with Fritzing(http://fritzing.org/)](../../../Resources/images/Blinky/breadboard_assembled.png)
+![Image made with Fritzing(http://fritzing.org/)](../../Resources/images/Blinky/breadboard_assembled.png)
 
 ### For DragonBoard 410c (DB)
 
 For reference, the functionality of the low-speed expansion connector is outlined in the following diagram
 
-![](../../../Resources/images/PinMappings/DB_Pinout.png)
+![](../../Resources/images/PinMappings/DB_Pinout.png)
 
 Perform the following steps to create the circuit:
 
@@ -66,7 +66,7 @@ Perform the following steps to create the circuit:
 
 Here is an illustration of what your breadboard might look like with the circuit assembled:
 
-![Image made with Fritzing(http://fritzing.org/)](../../../Resources/images/Blinky/breadboard_assembled_db_kit.png)
+![Image made with Fritzing(http://fritzing.org/)](../../Resources/images/Blinky/breadboard_assembled_db_kit.png)
 
 Finally, the LED_PIN variable of _MainPage.xaml.cs_ file of the sample code will need the following modification:
 
@@ -80,19 +80,19 @@ Finally, the LED_PIN variable of _MainPage.xaml.cs_ file of the sample code will
 
 2.  Next, in the Visual Studio toolbar, click on the `Local Machine` dropdown and select `Remote Machine`
 
-    ![RemoteMachine Target](../../../Resources/images/AppDeployment/cs-remote-machine-debugging.png)
+    ![RemoteMachine Target](../../Resources/images/AppDeployment/cs-remote-machine-debugging.png)
 
 3.  At this point, Visual Studio will present the **Remote Connections** dialog. If you previously used [PowerShell](https://docs.microsoft.com/en-us/windows/iot-core/connect-your-device/powershell) to set a unique name for your device, you can enter it here (in this example, we’re using **my-device**). Otherwise, use the IP address of your Windows IoT Core device. After entering the device name/IP select `Universal` for Windows Authentication, then click **Select**.
 
-    ![Remote Machine Debugging](../../../Resources/images/AppDeployment/cs-remote-connections.PNG)
+    ![Remote Machine Debugging](../../Resources/images/AppDeployment/cs-remote-connections.PNG)
 
 4.  You can verify or modify these values by navigating to the project properties (select **Properties** in the Solution Explorer) and choosing the `Debug` tab on the left:
 
-    ![Project Properties Debug Tab](../../../Resources/images/AppDeployment/cs-debug-project-properties.PNG)
+    ![Project Properties Debug Tab](../../Resources/images/AppDeployment/cs-debug-project-properties.PNG)
 
 When everything is set up, you should be able to press F5 from Visual Studio. If there are any missing packages that you did not install during setup, Visual Studio may prompt you to acquire those now. The Blinky app will deploy and start on the Windows IoT device, and you should see the LED blink in sync with the simulation on the screen.
 
-![](../../../Resources/images/Blinky/blinky-screenshot.png)
+![](../../Resources/images/Blinky/blinky-screenshot.png)
 
 Congratulations! You controlled one of the GPIO pins on your Windows IoT device.