Merge pull request #325 from RicoSaupe/cleanupimages

Cleanupimages

Author: isaacabraham

docs/faq/faq-troubleshooting.md

@@ -25,15 +25,15 @@ You may see the following `SocketProtocolError` message in the Debug Console onc
 
 > `WebSocket connection to 'ws://localhost:8000/socketcluster/' failed: Error during WebSocket handshake: Unexpected response code: 404`
 
-<center><img src="../img/feature-debugging-5.png" style="height: 175px;"/></center>
+<center><img src="../../img/feature-debugging-5.png" style="height: 175px;"/></center>
 
 Whilst these messages can be safely ignored, you can eliminate them by installing **Redux Dev Tools** in the launched Chrome instance as described in the debugging [prerequisites](../v4-recipes/developing-and-testing/debug-safe-app.md#0-install-prerequisites) section.
 
 ### Node Process does not stop after stopping the VS Code debugger
 VS Code does not kill the Fable process when you stop the debugger, leaving it running as a "zombie". In such a case, you will have to explicitly kill the process otherwise it will hold onto
 port 8080 and prevent you starting new instances. This should be easily doable by sending Ctrl+C in the Terminal window in VS Code for `Watch Client` task. Tracked [here](https://github.com/SAFE-Stack/SAFE-template/issues/191).
 
-<center><img src="../img/faq-troubleshoot-debugging.png" style="height: 175px;"/></center>
+<center><img src="../../img/faq-troubleshoot-debugging.png" style="height: 175px;"/></center>
 
 ### Chrome opens to a blank window when debugging in VS Code