Update private-endpoint-overview.md

Fixed typo and added escape character for `<`.

Author: ShannonLeavitt

articles/private-link/private-endpoint-overview.md

@@ -31,7 +31,7 @@ Azure Private Endpoint is a network interface that connects you privately and se
 Here are some key details about private endpoints: 
 - Private endpoint enables connectivity between the consumers from the same VNet, regionally peered VNets, globally peered VNets and on premises using [VPN](https://azure.microsoft.com/services/vpn-gateway/) or [Express Route](https://azure.microsoft.com/services/expressroute/) and services powered by Private Link.
 
-- When creating a private endpoint, a network interface is also created for the lifecycle of the resource. The interafce is assigned a private IP address from the subnet that maps to the Private Link Service.
+- When creating a private endpoint, a network interface is also created for the lifecycle of the resource. The interface is assigned a private IP address from the subnet that maps to the Private Link Service.
 
 - The private endpoint must be deployed in the same region as the virtual network. 
 
@@ -62,7 +62,7 @@ You can completely lock down your workloads from accessing public endpoints to c
 
 ## Access to a private link resource using approval workflow 
 You can connect to a private link resource using the following connection approval methods:
-- **Automatically** approved when you own or have permission on the specific private link resource. The permission required is based on the private link resource type in the following format: Microsoft.<Provider>/<resource_type>/privateEndpointConnectionApproval/action
+- **Automatically** approved when you own or have permission on the specific private link resource. The permission required is based on the private link resource type in the following format: Microsoft.\<Provider>/<resource_type>/privateEndpointConnectionApproval/action
 - **Manual** request when you don't have the permission required and would like to request access. An approval workflow will be initiated. The private endpoint and subsequent private endpoint connection will be created in a "Pending" state. The private link resource owner is responsible to approve the connection. After it's approved, the private endpoint is enabled to send traffic normally, as shown in the following approval workflow diagram.  
 
 ![workflow approval](media/private-endpoint-overview/private-link-paas-workflow.png)