X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;ds=sidebyside;f=man%2Fsystemd-nspawn.xml;h=e1b33f72c50ae58dba6e540ef4f50ed5e774ddc0;hb=9f7dad774ebfad23269800b7096eaad087481deb;hp=70ebf94e0ff4ff5fc65c45921a57a9d2d63f579b;hpb=8f7a3c1402a8de36b2c63935358a53510d2fe7c1;p=elogind.git
diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml
index 70ebf94e0..e1b33f72c 100644
--- a/man/systemd-nspawn.xml
+++ b/man/systemd-nspawn.xml
@@ -61,7 +61,7 @@
container. In many ways it is similar to
chroot1,
but more powerful since it fully virtualizes the file
- system hierachy, as well as the process tree, the
+ system hierarchy, as well as the process tree, the
various IPC subsystems and the host and domain
name.
@@ -99,14 +99,14 @@
Note that systemd-nspawn will
mount file systems private to the container to
/dev,
- /dev/.run and similar. These will
+ /run and similar. These will
not be visible outside of the container, and their
contents will be lost when the container exits.
Note that running two
systemd-nspawn containers from the
same directory tree will not make processes in them
- see each other. The PID namespace seperation of the
+ see each other. The PID namespace separation of the
two containers is complete and the containers will
share very few runtime objects except for the
underlying file system.