Update: 2 typos in line 13

Author: andrePKI

articles/azure-monitor/logs/private-link-design.md

@@ -10,7 +10,7 @@ ms.date: 08/01/2021
 # Design your Private Link setup
 
 Before you set up your Azure Monitor Private Link, consider your network topology, and specifically your DNS routing topology.
-As discussed in [How it work](./private-link-security.md#how-it-works), setting up a Private Link affects traffic to all Azure Monitor resources. That's especially true for Application Insights resources. Additionally, it affects not only the network connected to the Private Endpoint but also all other networks the share the same DNS.
+As discussed in [How it works](./private-link-security.md#how-it-works), setting up a Private Link affects traffic to all Azure Monitor resources. That's especially true for Application Insights resources. Additionally, it affects not only the network connected to the Private Endpoint but also all other networks sharing the same DNS.
 
 The simplest and most secure approach would be:
 1. Create a single Private Link connection, with a single Private Endpoint and a single AMPLS. If your networks are peered, create the Private Link connection on the shared (or hub) VNet.
@@ -203,4 +203,4 @@ The [`externaldata` operator](/azure/data-explorer/kusto/query/externaldata-oper
 ## Next steps
 - Learn how to [configure your Private Link](private-link-configure.md)
 - Learn about [private storage](private-storage.md) for Custom Logs and Customer managed keys (CMK)
-- Learn about [Private Link for Automation](../../automation/how-to/private-link-security.md)
+- Learn about [Private Link for Automation](../../automation/how-to/private-link-security.md)