This is a one-line documentation correction in docs/docs/terminology.md, replacing an inaccurate claim that sandboxes use gVisor with an accurate description of the actual isolation mechanism: Linux kernel namespaces and cgroups via containerd.
The new wording — "Sandboxes are Linux containers managed by containerd, isolated using kernel namespaces and cgroups, and each has its own network namespace by default." — is both more precise and consistent with how the rest of the terminology doc describes the Miren Runtime (line 85 already calls out containerd as the foundation). The "by default" qualifier on the network namespace is a nice touch; it leaves the door open without overstating things.
Nothing to flag. The change is factually straightforward and the wording reads cleanly. Ready to merge.
Verdict: ready
{
"owner": "mirendev",
"repo": "runtime",
"number": 973,
"verdict": "ready",
"event": "approve",
"summary": "This is a one-line documentation correction in `docs/docs/terminology.md`, replacing an inaccurate claim that sandboxes use gVisor with an accurate description of the actual isolation mechanism: Linux kernel namespaces and cgroups via containerd.\n\nThe new wording — *\"Sandboxes are Linux containers managed by containerd, isolated using kernel namespaces and cgroups, and each has its own network namespace by default.\"* — is both more precise and consistent with how the rest of the terminology doc describes the Miren Runtime (line 85 already calls out containerd as the foundation). The \"by default\" qualifier on the network namespace is a nice touch; it leaves the door open without overstating things.\n\nNothing to flag. The change is factually straightforward and the wording reads cleanly. Ready to merge.",
"posted_to_pr": true
}