Apply suggestions from code review

Added period at the end of the alt text

Author: PMEds28

articles/azure-web-pubsub/howto-integrate-app-service.md

@@ -157,7 +157,7 @@ At any point in time, there maybe more than one client drawing. If the Web App w
         The client, built with [Vue](https://vuejs.org/), makes an HTTP request for a Client Access Token to an endpoint `/negotiate`. The backend application is an [Express app](https://expressjs.com/) and hosted as a Web App using Azure App Service.
     :::column-end:::
     :::column:::
-        :::image type="content" source="./media/howto-integrate-app-service/dataflow-1.jpg" alt-text="Screenshot of step one of app data flow" lightbox="./media/howto-integrate-app-service/dataflow-1.jpg":::
+        :::image type="content" source="./media/howto-integrate-app-service/dataflow-1.jpg" alt-text="Screenshot of step one of app data flow." lightbox="./media/howto-integrate-app-service/dataflow-1.jpg":::
     :::column-end:::
 :::row-end:::
 
@@ -166,7 +166,7 @@ At any point in time, there maybe more than one client drawing. If the Web App w
         When the backend application successfully [returns the Client Access Token](https://github.com/Azure/awps-webapp-sample/blob/main/whiteboard/server.js#L62) to the connecting client, the client uses it to establish a WebSocket connection with Azure Web PubSub.  
     :::column-end:::
     :::column:::
-        :::image type="content" source="./media/howto-integrate-app-service/dataflow-2.jpg" alt-text="Screenshot of step two of app data flow" lightbox="./media/howto-integrate-app-service/dataflow-2.jpg":::
+        :::image type="content" source="./media/howto-integrate-app-service/dataflow-2.jpg" alt-text="Screenshot of step two of app data flow." lightbox="./media/howto-integrate-app-service/dataflow-2.jpg":::
     :::column-end:::
 :::row-end:::
 
@@ -175,7 +175,7 @@ At any point in time, there maybe more than one client drawing. If the Web App w
         If the handshake with Azure Web PubSub is successful, the client is added to a group named `draw`, effectively subscribing to messages published to this group. Also, the client is given the permission to send messages to the [`draw` group](https://github.com/Azure/awps-webapp-sample/blob/main/whiteboard/server.js#L64). 
     :::column-end:::
     :::column:::
-        :::image type="content" source="./media/howto-integrate-app-service/dataflow-3.jpg" alt-text="Screenshot of step three of app data flow" lightbox="./media/howto-integrate-app-service/dataflow-3.jpg":::
+        :::image type="content" source="./media/howto-integrate-app-service/dataflow-3.jpg" alt-text="Screenshot of step three of app data flow." lightbox="./media/howto-integrate-app-service/dataflow-3.jpg":::
     :::column-end:::
 :::row-end:::
 > [!NOTE]
@@ -186,7 +186,7 @@ At any point in time, there maybe more than one client drawing. If the Web App w
         Azure Web PubSub notifies the backend application that a client has connected. The backend application handles the `onConnected` event by calling the `sendToAll()`, with a payload of the latest number of connected clients.
     :::column-end:::
     :::column:::
-        :::image type="content" source="./media/howto-integrate-app-service/dataflow-4.jpg" alt-text="Screenshot of step four of app data flow" lightbox="./media/howto-integrate-app-service/dataflow-4.jpg":::
+        :::image type="content" source="./media/howto-integrate-app-service/dataflow-4.jpg" alt-text="Screenshot of step four of app data flow." lightbox="./media/howto-integrate-app-service/dataflow-4.jpg":::
     :::column-end:::
 :::row-end:::
 > [!NOTE]
@@ -197,7 +197,7 @@ At any point in time, there maybe more than one client drawing. If the Web App w
         As soon as a client establishes a persistent connection with Web PubSub, it makes an HTTP request to the backend application to fetch the latest shape and background data at [`/diagram`](https://github.com/Azure/awps-webapp-sample/blob/main/whiteboard/server.js#L70). An HTTP service hosted on App Service can be combined with Web PubSub. App Service takes care serving HTTP endpoints, while Web PubSub takes care of managing WebSocket connections. 
     :::column-end:::
     :::column:::
-        :::image type="content" source="./media/howto-integrate-app-service/dataflow-5.jpg" alt-text="Screenshot of step five of app data flow" lightbox="./media/howto-integrate-app-service/dataflow-5.jpg":::
+        :::image type="content" source="./media/howto-integrate-app-service/dataflow-5.jpg" alt-text="Screenshot of step five of app data flow." lightbox="./media/howto-integrate-app-service/dataflow-5.jpg":::
     :::column-end:::
 :::row-end:::
 
@@ -206,7 +206,7 @@ At any point in time, there maybe more than one client drawing. If the Web App w
         Now that the clients and backend application have two ways to exchange data. One is the conventional HTTP request-response cycle and the other is the persistent, bi-directional channel through Web PubSub. The drawing actions, which originate from one user and need to be broadcasted to all users as soon as it takes place, are delivered through Web PubSub. It doesn't require involvement of the backend application.
     :::column-end:::
     :::column:::
-        :::image type="content" source="./media/howto-integrate-app-service/dataflow-6.jpg" alt-text="Screenshot of step six of app data flow" lightbox="./media/howto-integrate-app-service/dataflow-6.jpg":::
+        :::image type="content" source="./media/howto-integrate-app-service/dataflow-6.jpg" alt-text="Screenshot of step six of app data flow." lightbox="./media/howto-integrate-app-service/dataflow-6.jpg":::
     :::column-end:::
 :::row-end:::