Update ch10.md (#77)

Author: sirnish

ch10.md

@@ -22,7 +22,7 @@ or ISR that sent the event or data. This is depicted in Figure 10.1.
 <a name="fig10.1" title="Figure 10.1 A communication object being used to send an event from one task to another"></a>
 
 * * *
-![](media/image76.png)
+![](media/image76.png)    
 ***Figure 10.1*** *A communication object being used to send an event from one task to another*
 * * *
 
@@ -37,7 +37,7 @@ directly to the receiving task. This is depicted in Figure 10.2.
 <a name="fig10.2" title="Figure 10.2 A task notification used to send an event directly from one task to another"></a>
 
 * * *
-![](media/image77.png)
+![](media/image77.png)    
 ***Figure 10.2*** *A task notification used to send an event directly from one task to another*
 * * *
 
@@ -491,10 +491,10 @@ produced by the periodic task. Further explanation is provided in Figure 10.4.
 <a name="fig10.4" title="Figure 10.4 The sequence of execution when Example 10.1 is executed"></a>
 
 * * *
-![](media/image78.png)
+![](media/image78.png)    
 ***Figure 10.3*** *The output produced when Example 7.1 is executed*
 
-![](media/image79.png)
+![](media/image79.png)    
 ***Figure 10.4*** *The sequence of execution when Example 10.1 is executed*
 * * *
 
@@ -602,7 +602,7 @@ interrupt is generated.
 <a name="fig10.5" title="Figure 10.5 The output produced when Example 10.2 is executed"></a>
 
 * * *
-![](media/image80.jpg)
+![](media/image80.jpg)    
 ***Figure 10.5*** *The output produced when Example 10.2 is executed*
 * * *
 
@@ -1348,7 +1348,7 @@ The structure sent to the server task by the `CloudRead()` and
 <a name="fig10.6" title="Figure 10.6 The communication paths from the application tasks to the cloud server, and back again"></a>
 
 * * *
-![](media/image81.png)   
+![](media/image81.png)    
 ***Figure 10.6*** *The communication paths from the application tasks to the cloud server, and back again*
 * * *