fix API content

Author: shainaraskas

deploy-manage/security/azure-private-link-traffic-filters.md

@@ -156,8 +156,7 @@ The Private Link connection will be approved automatically after the private con
     Network security policies are bound to a single region, and can be assigned only to deployments in the same region. If you want to associate a policy with resources in multiple regions, then you have to create the same policy in all the regions you want to apply it to.
     :::
 7.  Under **Connectivity**, select **Privatelink**.
-8.  Under **VPCE filter**, enter your Private Endpoint resource ID.
-    % where does name go
+8.  Enter your private endpoint **Resource name** and **Resource ID**. When applied to a deployment, this information will be used to filter traffic.
 
     :::{tip}
     You can assign multiple policies to a single deployment. The policies can be of different types. In case of multiple policies, traffic can match any associated policy to be forwarded to the resource. If none of the policies match, the request is rejected with `403 Forbidden`.
@@ -168,7 +167,7 @@ The Private Link connection will be approved automatically after the private con
 9.  Optional: Under **Apply to resources**, associate the new private connection policy with one or more deployments. After you associate the filter with a deployment, it starts filtering traffic.
 10. To automatically attach this private connection policy to new deployments, select **Apply by default**.
 11.  Click **Create**.
-12. (Optional) You can [claim your Private Endpoint resource ID](/deploy-manage/security/claim-traffic-filter-link-id-ownership-through-api.md), so that no other organization is able to use it in a private connection policy.
+12. (Optional) You can [claim your Private Endpoint resource name and ID](/deploy-manage/security/claim-traffic-filter-link-id-ownership-through-api.md), so that no other organization is able to use it in a private connection policy.
 
 Creating the filter approves the Private Link connection.
 

deploy-manage/security/claim-traffic-filter-link-id-ownership-through-api.md

@@ -8,26 +8,26 @@ products:
   - id: cloud-hosted
 ---
 
-# Claim VCPE ID ownership [ec-claim-traffic-filter-link-id-through-the-api]
+# Claim VCPE ID or Azure resource ownership [ec-claim-traffic-filter-link-id-through-the-api]
 
-This example demonstrates how to use the {{ecloud}} RESTful API to claim different types of private link ID (AWS PrivateLink, Azure Private Link, and GCP Private Service Connect). We cover the following examples:
+This example demonstrates how to use the {{ecloud}} RESTful API to claim different types of ID (AWS PrivateLink, Azure Private Link, and GCP Private Service Connect). We cover the following examples:
 
-* [Claim a VCPE ID](#ec-claim-a-traffic-filter-link-id)
+* [Claim a VCPE ID or Azure resource](#ec-claim-a-traffic-filter-link-id)
 
     * [AWS PrivateLink](#ec-claim-aws-privatelink)
     * [Azure Private Link](#ec-claim-azure-private-link)
     * [GCP Private Service Connect](#ec-claim-gcp-private-service-connect)
 
-* [List claimed VCPE IDs](#ec-list-claimed-traffic-filter-link-id)
-* [Unclaim a VCPE ID](#ec-unclaim-a-traffic-filter-link-id)
+* [List claimed IDs](#ec-list-claimed-traffic-filter-link-id)
+* [Unclaim a VCPE ID or Azure resource](#ec-unclaim-a-traffic-filter-link-id)
 
     * [AWS PrivateLink](#ec-unclaim-aws-privatelink)
     * [Azure Private Link](#ec-unclaim-azure-private-link)
     * [GCP Private Service Connect](#ec-unclaim-gcp-private-service-connect)
 
 
 
-## Claim a VCPE ID [ec-claim-a-traffic-filter-link-id] 
+## Claim a VCPE ID or Azure resource [ec-claim-a-traffic-filter-link-id] 
 
 
 ### AWS PrivateLink [ec-claim-aws-privatelink] 
@@ -79,7 +79,7 @@ https://api.elastic-cloud.com/api/v1/deployments/traffic-filter/link-ids/_claim
 ```
 
 
-## List claimed VCPE IDs [ec-list-claimed-traffic-filter-link-id] 
+## List claimed IDs [ec-list-claimed-traffic-filter-link-id] 
 
 ```sh
 curl \
@@ -89,7 +89,7 @@ https://api.elastic-cloud.com/api/v1/deployments/traffic-filter/link-ids \
 ```
 
 
-## Unclaim a VCPE ID [ec-unclaim-a-traffic-filter-link-id] 
+## Claim a VCPE ID or Azure resource [ec-unclaim-a-traffic-filter-link-id] 
 
 
 ### AWS PrivateLink [ec-unclaim-aws-privatelink]