X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd.slice.xml;h=b7b0622d3c3d2de6dd63cd5f91bc3067628502c2;hp=7ddef85eec8df662362cb650dd0dbe99621b58f3;hb=6577c7cea72f19185ad999c223bcf663c010dc6f;hpb=847ae0ae7f29e7bfb245d692409fc2948eab7d1d
diff --git a/man/systemd.slice.xml b/man/systemd.slice.xml
index 7ddef85ee..b7b0622d3 100644
--- a/man/systemd.slice.xml
+++ b/man/systemd.slice.xml
@@ -60,10 +60,10 @@ along with systemd; If not, see .
processes. This management is performed by creating a node in the
control group tree. Units that manage processes (primarilly scope
and service units) may be assigned to a specific slice. For each
- slice certain resource limits may the be set, that apply to all
+ slice, certain resource limits may the be set that apply to all
processes of all units contained in that slice. Slices are
organized hierarchially in a tree. The name of the slice encodes
- the location in the tree. The name consists of a "-" separated
+ the location in the tree. The name consists of a dash-separated
series of names, which describes the path to the slice from the
root slice. The root slice is named,
-.slice. Example:
@@ -72,7 +72,7 @@ along with systemd; If not, see .
the root slice -.slice.
- By default service and scope units are placed in
+ By default, service and scope units are placed in
system.slice, virtual machines and containers
registered with
systemd-machined1