X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.special.xml;h=8ccccc2798713a4b0f6a7d1d9fdee0781d320ce0;hb=2e573fcf8754fdfe0db0a783b1631ec1679b063a;hp=2900808ef4e42c9f3475fab4cd9b39599905755d;hpb=32ce5ae22bf47969cac69abd37290539f9c189de;p=elogind.git
diff --git a/man/systemd.special.xml b/man/systemd.special.xml
index 2900808ef..8ccccc279 100644
--- a/man/systemd.special.xml
+++ b/man/systemd.special.xml
@@ -448,7 +448,7 @@
after it. Note that networking
daemons that simply provide
functionality to other hosts
- generally don't need to pull
+ generally do not need to pull
this in.
@@ -820,7 +820,7 @@
services. These targets are generally not part of the
initial boot transaction, unless they are explicitly
pulled in by one of the implementing services. Note
- specifically, that these passive
+ specifically that these passive
target units are generally not pulled in by the
consumer of a service, but by the provider of the
service. This means: a consuming service should order
@@ -939,7 +939,7 @@
Wants= type
dependency. If the unit wants
to be pulled in by the first
- remote mount showing up it
+ remote mount showing up, it
should use
network-online.target
(see above).
@@ -996,7 +996,7 @@
smartcard.target,
sound.target.
- In addition the following special unit is
+ In addition, the following special unit is
understood only when systemd runs as service instance:
@@ -1012,7 +1012,7 @@
manager should start this
unit. If systemd receives
SIGTERM or SIGINT when running
- as user service daemon it will
+ as user service daemon, it will
start this unit.
Normally, this pulls in