Update 04-planning.md

Author: cmcclister

articles/mysql/migrate/mysql-on-premises-azure-db/04-planning.md

@@ -61,7 +61,7 @@ The migration tool location determines the network connectivity requirements. As
 
 Other networking considerations include:
 
-- DMS located in a VNET is assigned a [dynamic public IP](../../../dms/faq.yml#setup) to the service. At creation time, you can place the service inside a virtual network that has connectivity via a [ExpressRoute](../../../expressroute/expressroute-introduction.md) or over [a site to site VPN](../../../vpn-gateway/tutorial-site-to-site-portal.md).
+- DMS located in a VNET is assigned a [dynamic public IP](../../../dms/faq.yml) to the service. At creation time, you can place the service inside a virtual network that has connectivity via a [ExpressRoute](../../../expressroute/expressroute-introduction.md) or over [a site to site VPN](../../../vpn-gateway/tutorial-site-to-site-portal.md).
 
 - When using an Azure Virtual Machine to run the migration tools, assign it a public IP address and then only allow it to connect to the on-premises MySQL instance.
 
@@ -96,4 +96,4 @@ WWI originally wanted to test an online migration, but the required network setu
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Migration Methods](./05-migration-methods.md)
+> [Migration Methods](./05-migration-methods.md)