fixing links

Author: Blackmist

articles/machine-learning/concept-network-isolation-configurations.md

@@ -61,7 +61,7 @@ The following table provides a comparison of the benefits and limitations of man
 ### Custom virtual network limitations
 
 - __New features support might be delayed__: Efforts for improving our network isolation offerings are focused on managed instead of custom virtual network. Therefore, new feature asks are prioritized on managed over custom virtual network.
-- __Managed online endpoints isn't supported__: Managed online endpoints don't support custom virtual network. Workspace managed virtual network must be enabled to secure your managed online endpoints. You can secure managed online endpoints with legacy network isolation method. But, we strongly recommend that you use workspace managed network isolation. For more information, visit [Managed online endpoints](concept-online-endpoints.md).
+- __Managed online endpoints isn't supported__: Managed online endpoints don't support custom virtual network. Workspace managed virtual network must be enabled to secure your managed online endpoints. You can secure managed online endpoints with legacy network isolation method. But, we strongly recommend that you use workspace managed network isolation. For more information, visit [Managed online endpoints](concept-endpoints-online.md).
 - __Serverless spark compute isn't supported__: Serverless Spark computes aren't supported in a custom virtual network. Workspace managed virtual network supports Serverless Spark because Azure Synapse only uses managed virtual network set-up. For more information, visit [Configured Serverless Spark](apache-spark-azure-ml-concepts.md#serverless-spark-compute).
 - __Implementation complexity and maintenance overhead__: With custom virtual network set-up, all the complexity of setting up a virtual network, subnet, private endpoints, and more falls on the user. Maintenance of the network and computes fall on the user.