diff --git a/docs/architecture.md b/docs/architecture.md index 54791fb..310b9aa 100644 --- a/docs/architecture.md +++ b/docs/architecture.md @@ -24,7 +24,7 @@ Diagram map: ## L1 context and L3 components -This diagram shows culvert as one box and what it talks to. +Clients tunnel into culvert, which routes their traffic to the site networks. ```mermaid flowchart LR @@ -53,7 +53,7 @@ flowchart LR *Figure 1. L1 Context -- Culvert. Dashed boxes are external, and dotted arrows are opt-in.* Up: top of culvert. Down: [L3 Components -- Culvert](#l1-context-and-l3-components). -This diagram shows the processes inside the container. +stunnel fronts OpenVPN and wstunnel fronts WireGuard. ```mermaid flowchart LR @@ -137,7 +137,7 @@ drops a compiler toolchain from the image at no cost to the capability. in a focused module under `scripts/lib/`, and the entrypoint's job is the order. -This diagram shows the startup steps as three stages. +Network and firewall come up before either VPN. ```mermaid flowchart TB diff --git a/docs/use-case-edge-fleet.md b/docs/use-case-edge-fleet.md index 2723248..24be083 100644 --- a/docs/use-case-edge-fleet.md +++ b/docs/use-case-edge-fleet.md @@ -53,7 +53,7 @@ It is gated: the CIDRs in `CULVERT_DOWNSTREAM_ADMIN_CIDRS` are the sources allowed to initiate inbound. Everything else unsolicited into the tunnels is dropped. -This diagram shows the two flows through culvert in an edge fleet. +In an edge fleet, data flows up from the appliances to the receiver, and admin traffic flows down from the admin networks to the appliances. ```mermaid flowchart TB