fixes

Author: shainaraskas

deploy-manage/security/aws-privatelink-traffic-filters.md

@@ -98,7 +98,7 @@ The process of setting up a private connection with AWS PrivateLink is split bet
 | --- | --- |
 | 1. [Create a VPC endpoint using {{ecloud}} service name.](#ec-aws-vpc-dns) |  |
 | 2. [Create a DNS record pointing to the VPC endpoint.](#ec-aws-vpc-dns) |  |
-|  | 3. **Optional**: [Create a private connection policy.](ec-add-vpc-elastic)<br><br>A private connection policy is required to filter traffic using the VCP endpoint ID. |
+|  | 3. **Optional**: [Create a private connection policy.](#ec-add-vpc-elastic)<br><br>A private connection policy is required to filter traffic using the VCP endpoint ID. |
 |  | 4. **Optional**: [Associate the private connection policy with deployments](#ec-associate-traffic-filter-private-link-rule-set). |
 |  | 5. [Interact with your deployments over PrivateLink](#ec-access-the-deployment-over-private-link). |
 

deploy-manage/security/ec-traffic-filtering-through-the-api.md

@@ -236,7 +236,7 @@ https://api.elastic-cloud.com/api/v1/deployments/traffic-filter/rulesets \
 '
 ```
 
-To find the value for `azure_endpoint_name` and `azure_endpoint_guid` for type `azure_private_endpoint`, check [Find your private endpoint resource name](azure-private-link-traffic-filters.md#ec-find-your-resource-name) and [Find your private endpoint resource ID](azure-private-link-traffic-filters.md#ec-find-your-resource-id). This setting is supported only in Azure regions.
+To find the value for `azure_endpoint_name` and `azure_endpoint_guid` for type `azure_private_endpoint`, check [Find your private endpoint resource name]() and [Find your private endpoint resource ID](azure-private-link-traffic-filters.md#ec-find-your-resource-id). This setting is supported only in Azure regions.
 
 
 ### GCP Private Service Connect traffic filters [ec-gcp-private-service-connect-traffic-filters-rule-set]

deploy-manage/security/ip-traffic-filtering.md

@@ -24,7 +24,7 @@ If you use {{ech}} or {{eck}}, then other [network security](/deploy-manage/secu
 In {{serverless-full}} and {{ech}}, network security policies are created at the organization level, and then applied at the deployment level. Follow these guides to learn how to create, apply, and manage these policies using your preferred method:
 
   * [In the {{ecloud}} console](/deploy-manage/security/ip-filtering-cloud.md)
-  * [Using the {{ecloud}} API](/deploy-manage/security/ec-traffic-filtering-through-the-api)
+  * [Using the {{ecloud}} API](/deploy-manage/security/ec-traffic-filtering-through-the-api.md)
 
 To learn how multiple IP filter policies are processed, and how IP filters and [private connections](/deploy-manage/security/private-link-traffic-filters.md) work together in ECH, refer to [](/deploy-manage/security/network-security-policies.md).
 
@@ -33,9 +33,9 @@ To learn how multiple IP filter policies are processed, and how IP filters and [
 In {{ece}}, filter rules are created at the platform level, and then applied at the deployment level. Follow these guides to learn how to create, apply, and manage these policies using your preferred method:
 
   * [In the Cloud UI](/deploy-manage/security/ip-filtering-ece.md)
-  * [Using the {{ecloud}} API](/deploy-manage/security/ec-traffic-filtering-through-the-api)
+  * [Using the {{ecloud}} API](/deploy-manage/security/ec-traffic-filtering-through-the-api.md)
 
-To learn how multiple rules are processed, refer to [Traffic filter rules](/deploy-manage/security/traffic-filter-rules.md).
+To learn how multiple rules are processed, refer to [](/deploy-manage/security/ece-filter-rules.md).
 
 ## ECK and self managed