Merge pull request #305568 from mbender-ms/appgw-fix-image

application gateway | Fix image

Author: prmerger-automator[bot]

articles/application-gateway/configuration-http-settings.md

@@ -173,7 +173,9 @@ For example, if *www.contoso.com* is specified in the **Host name** setting, the
 Azure Application Gateway, by default, reuses idle backend connections to optimize the resource utilization of TCP connections for both the Application Gateway and the backend server.
 To support security functions in customer data paths that necessitate unique backend connections per client, Azure Application Gateway V2 provides dedicated connections to backend servers.
 
-:::image type="content" source="media/configuration-http-settings/dedicated-backend.png" alt-text="Screenshot of network flows through Application Gateway layer 7 proxy."::: This capability establishes direct, one-to-one mapping between frontend and backend connections, ensuring persistent connectivity for each individual client.
+:::image type="content" source="media/configuration-http-settings/dedicated-backend.png" alt-text="Screenshot of network flows through Application Gateway layer 7 proxy."::: 
+
+This capability establishes direct, one-to-one mapping between frontend and backend connections, ensuring persistent connectivity for each individual client.
 
 >[!IMPORTANT]
 >Dedicated backend connection leads to an increase in the number of backend connections and hence could require more resources to support the increased concurrent connections on Application Gateway and the backend servers. On Application Gateway, you must consider increasing the number of instances or enabling auto scale.