fixed image link to standards and cleaned up PoSH and CLI code

Author: asudbring

articles/virtual-network/virtual-networks-udr-overview.md

@@ -117,13 +117,25 @@ The system gives preference to the route with the explicit prefix when there's a
 To use this feature, specify a Service Tag name for the address prefix parameter in route table commands. For example, in PowerShell you can create a new route to direct traffic sent to an Azure Storage IP prefix to a virtual appliance by using: </br></br>
 
 ```azurepowershell-interactive
-New-AzRouteConfig -Name "StorageRoute" -AddressPrefix "Storage" -NextHopType "VirtualAppliance" -NextHopIpAddress "10.0.100.4"
+$param = @{
+    Name = 'StorageRoute'
+    AddressPrefix = 'Storage'
+    NextHopType = 'VirtualAppliance'
+    NextHopIpAddress = '10.0.100.4'
+}
+New-AzRouteConfig @param
 ```
 
 The same command for CLI is as follows: 
 
 ```azurecli-interactive
-az network route-table route create -g MyResourceGroup --route-table-name MyRouteTable -n StorageRoute --address-prefix Storage --next-hop-type VirtualAppliance --next-hop-ip-address 10.0.100.4
+az network route-table route create \
+    --resource-group MyResourceGroup \
+    --route-table-name MyRouteTable \
+    --name StorageRoute \
+    --address-prefix Storage \
+    --next-hop-type VirtualAppliance \
+    --next-hop-ip-address 10.0.100.4
 ```
 
 ## Next hop types across Azure tools
@@ -241,7 +253,7 @@ To illustrate the concepts in this article, the sections that follow describe:
 
 The following picture shows an implementation through the Azure Resource Manager deployment model that meets the previous requirements:
 
-![Network diagram](./media/virtual-networks-udr-overview/routing-example.png)
+:::image type="content" source="./media/virtual-networks-udr-overview/routing-example.png" alt-text="Diagram of network.":::
 
 Arrows show the flow of traffic.