sandboxes(chore): clean up "next steps" sections

Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>

content/manuals/ai/sandboxes/architecture.md

@@ -223,9 +223,3 @@ Sandboxes trade higher resource overhead (VM + daemon) for complete isolation.
 Use containers when you need lightweight packaging without Docker access. Use
 sandboxes when you need to give something autonomous full Docker capabilities
 without trusting it with your host environment.
-
-## Next steps
-
-- [Network policies](network-policies.md)
-- [Custom templates](templates.md)
-- [Using sandboxes effectively](workflows.md)

content/manuals/ai/sandboxes/network-policies.md

@@ -385,9 +385,3 @@ You can modify the default policy:
 Review and customize the default policy to match your security requirements
 before creating new sandboxes. Once created, the default policy file won't be
 modified by upgrades, preserving your custom configuration.
-
-## Next steps
-
-- [Architecture](architecture.md)
-- [Using sandboxes effectively](workflows.md)
-- [Custom templates](templates.md)

content/manuals/ai/sandboxes/templates.md

@@ -218,9 +218,3 @@ $ docker sandbox run -t myorg/sandbox-templates:python-v1.0 claude [PATH]
 
 Use version tags like `:v1.0` instead of `:latest` for consistency across your
 team.
-
-## Next steps
-
-- [Using sandboxes effectively](workflows.md)
-- [Architecture](architecture.md)
-- [Network policies](network-policies.md)

content/manuals/ai/sandboxes/workflows.md

@@ -284,9 +284,3 @@ List all sandboxes:
 ```console
 $ docker sandbox ls
 ```
-
-## Next steps
-
-- [Custom templates](templates.md)
-- [Architecture](architecture.md)
-- [Network policies](network-policies.md)