From f3ab3abdc1ea0d9b561caa81e94d2f0cc3d9b457 Mon Sep 17 00:00:00 2001 From: damocles Date: Sat, 21 Nov 2026 15:59:08 +0100 Subject: [PATCH] docs: re-wrap the builder paragraph in services.md --- docs/2-handbook/swarm/services.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/2-handbook/swarm/services.md b/docs/2-handbook/swarm/services.md index a8d181e9f..ca2d2e314 100644 --- a/docs/2-handbook/swarm/services.md +++ b/docs/2-handbook/swarm/services.md @@ -191,11 +191,11 @@ metrics it exports and the threat model: The swarm builder, in a `swarm-builder` container on the host that sets `deploy.builder.enable`; set it to `false` to opt out. It evaluates and builds unreviewed agent config PRs, and the result shows as a `swarm-builder` commit -status on the PR. A merge needs that status to pass: a red or missing one blocks the -merge. It also -builds each agent before the swarm sends its deploy, and a failed build holds -that deploy back. The jobs show on the swarm UI's Jobs page. It builds through -its host's nix daemon, so it costs real CPU and disk. +status on the PR. A merge needs that status to pass: a red or missing one +blocks the merge. It also builds each agent before the swarm sends its +deploy, and a failed build holds that deploy back. The jobs show on the swarm +UI's Jobs page. It builds through its host's nix daemon, so it costs real CPU +and disk. [Host setup](../../4-implementation/swarm/builder.md#host-setup), and what it builds and why: [`builder.md`](../../4-implementation/swarm/builder.md).