adjusting to shilpa sharma comments for PR #111047

Author: mblanco77

articles/private-link/media/private-endpoint-dns/hubandspoke-azure-dns.png renamed to articles/private-link/media/private-endpoint-dns/hub-and-spoke-azure-dns.png

@@ -87,13 +87,13 @@ To configure properly you would need the following resources :
 
 - Client virtual network
 
-- Private DNS zone [(privatelink.database.windows.net)](../dns/private-dns-privatednszone.md)  with [A Record](../dns/dns-zones-records.md#record-types)
+- Private DNS zone [privatelink.database.windows.net](../dns/private-dns-privatednszone.md)  with [type A Record](../dns/dns-zones-records.md#record-types)
 
 - Private endpoint information (FQDN record name and Private IP Address)
 
 The following diagram illustrates the DNS resolution sequence from virtual network workloads using private dns zone
 
-
+[!div class="mx-imgBorder"]
 ![single virtual network and azure provided dns](media/private-endpoint-dns/single-vnet-azure-dns.png)
 
 
@@ -104,6 +104,8 @@ This model can be extended to multiple peered virtual networks that are associat
 
 In this scenario there's a [hub & spoke](https://docs.microsoft.com/azure/architecture/reference-architectures/hybrid-networking/hub-spoke) networking topology with the spoke networks sharing a common private endpoint and all the spoke virtual network are linked to the same private dns zone. 
 
-![hub & spoke with azure provided dns](media/private-endpoint-dns/hubandspoke-azure-dns.png)
-
+[!div class="mx-imgBorder"]
+![hub & spoke with azure provided dns](media/private-endpoint-dns/hub-and-spoke-azure-dns.png)
 
+## Next steps
+- [Learn about Private Endpoints](private-endpoint-overview.md)