docs: document the new journal file format additions

[thirdparty/systemd.git] / docs / CGROUP_DELEGATION.md

diff --git a/docs/CGROUP_DELEGATION.md b/docs/CGROUP_DELEGATION.md
index ab98544c4de873afb2e0ece3ecfb74807e80501d..d05503bc97786e0f196b47b8d746f5ae44834977 100644 (file)
--- a/docs/CGROUP_DELEGATION.md
+++ b/docs/CGROUP_DELEGATION.md
@@ -1,3 +1,9 @@
+---
+title: Control Group APIs and Delegation
+category: Interfaces
+layout: default
+---
+
 # Control Group APIs and Delegation
 
 *Intended audience: hackers working on userspace subsystems that require direct
@@ -15,10 +21,10 @@ comprehensive up-to-date information about all this, particular in light of the
 poor implementations of the components interfacing with systemd of current
 container managers.
 
-Before you read on, please make sure you read the low-level [kernel
-documentation about
-cgroup v2](https://www.kernel.org/doc/Documentation/cgroup-v2.txt). This
-documentation then adds in the higher-level view from systemd.
+Before you read on, please make sure you read the low-level kernel
+documentation about the
+[unified cgroup hierarchy](https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html).
+This document then adds in the higher-level view from systemd.
 
 This document augments the existing documentation we already have:
 
@@ -226,7 +232,7 @@ guarantees:
 In unit files the `Delegate=` property is superficially exposed as
 boolean. However, since v236 it optionally takes a list of controller names
 instead. If so, delegation is requested for listed controllers
-specifically. Note hat this only encodes a request. Depending on various
+specifically. Note that this only encodes a request. Depending on various
 parameters it might happen that your service actually will get fewer
 controllers delegated (for example, because the controller is not available on
 the current kernel or was turned off) or more.  If no list is specified