Fixed iamges issue

Author: Sreekanth Iyer (Ushta Te Consultancy Services)

articles/hdinsight/spark/what-is-speculative-execution-in-spark.md

@@ -15,7 +15,7 @@ This is how Spark completes the job as soon as possible. If either of the tasks
 
 You can monitor this from the spark UI, where a task ID shown Speculative as true.
 
-:::image type="content" source="./media/what-is-speculative-execution-in-spark/how-to-monitor.png" alt-text="How to monitor Spark job." lightbox="./media/media/what-is-speculative-execution-in-spark/how-to-monitor.png":::
+:::image type="content" source="./media/what-is-speculative-execution-in-spark/how-to-monitor.png" alt-text="How to monitor Spark job." lightbox="./media/what-is-speculative-execution-in-spark/how-to-monitor.png":::
 
 ## Configurations that affect this speculative behavior
 
@@ -34,7 +34,7 @@ In the below chart, lets consider total 10 tasks in a stage but task 5 takes mor
 When the `spark.speculation.minTaskRuntime` is set to 5 seconds, it starts a new task `SP-task5` on a new node. 
 When job the finished, the original task 5 is killed by the driver.
 
-:::image type="content" source="./media/what-is-speculative-execution-in-spark/runtime-chart.png" alt-text="How to view runtime chart?" lightbox="./media/media/what-is-speculative-execution-in-spark/runtime-shart.png":::
+:::image type="content" source="./media/what-is-speculative-execution-in-spark/runtime-chart.png" alt-text="How to view runtime chart?" lightbox="./media/what-is-speculative-execution-in-spark/runtime-shart.png":::
 
 ## When not to run a speculative execution?