From 55572dd1b8c73df155a9c78aea8e86c975d00a59 Mon Sep 17 00:00:00 2001 From: Hannah Cooper Date: Wed, 11 Mar 2026 22:25:52 +0000 Subject: [PATCH] GITBOOK-12: Fix broken policy link --- ...end-using-the-edge-agent-instead-of-the-traditional-agent.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/faqs/getting-started/why-do-we-recommend-using-the-edge-agent-instead-of-the-traditional-agent.md b/faqs/getting-started/why-do-we-recommend-using-the-edge-agent-instead-of-the-traditional-agent.md index d0b21c80..ace6d6ee 100644 --- a/faqs/getting-started/why-do-we-recommend-using-the-edge-agent-instead-of-the-traditional-agent.md +++ b/faqs/getting-started/why-do-we-recommend-using-the-edge-agent-instead-of-the-traditional-agent.md @@ -16,7 +16,7 @@ The Edge Agent unlocks Portainer’s full Edge Compute feature set, including: * [Edge Stacks](../../user/edge/stacks/) - deploy and manage stacks across distributed systems from one place. * [Edge Jobs](../../user/edge/jobs.md) - schedule scripts or tasks on edge hosts. * [Edge Configurations](../../user/edge/configurations.md) - pre-deploy config sets to environments. -* [Agent updates](../../admin/environments/update.md) and [policy management](/broken/pages/sVXwh5AjWlxKSXVhHQ5d) - centrally manage agent versions and policies across fleets. +* [Agent updates](../../admin/environments/update.md) and [policy management](../../admin/environments/policies/) - centrally manage agent versions and policies across fleets. These capabilities don’t exist with the traditional Agent, which is focused on basic connectivity rather than edge orchestration.