<refsect1>
- <title>Unpriviliged Write Access</title>
+ <title>Unprivileged Write Access</title>
- <para>Unpriviliged processes generally lack
+ <para>Unprivileged processes generally lack
write access to most of the hierarchy.</para>
<para>The exceptions for normal users are
below <filename>/run/user</filename>) of the
user, which are all writable.</para>
- <para>For unpriviliged system processes only
+ <para>For unprivileged system processes only
<filename>/tmp</filename>,
<filename>/var/tmp</filename> and
<filename>/dev/shm</filename> are writable. If an
- unpriviliged system process needs a private, writable
+ unprivileged system process needs a private, writable
directory in <filename>/var</filename> or
<filename>/run</filename>, it is recommended to either
- create it before dropping priviliges in the daemon
+ create it before dropping privileges in the daemon
code, to create it via
<citerefentry><refentrytitle>tmpfiles.d</refentrytitle><manvolnum>5</manvolnum></citerefentry>
fragments during boot, or via the
</row>
<row>
<entry><filename>/usr/lib/<replaceable>arch-id</replaceable>/<replaceable>package</replaceable></filename></entry>
- <entry>Private other vendor resources of the package that are architecture-specific and cannot be shared between architectures. Note that this generally does not include private exectuables since binaries of a specific architecture may be freely invoked from any other supported system architecture.</entry>
+ <entry>Private other vendor resources of the package that are architecture-specific and cannot be shared between architectures. Note that this generally does not include private executables since binaries of a specific architecture may be freely invoked from any other supported system architecture.</entry>
</row>
<row>
<entry><filename>/usr/include/<replaceable>package</replaceable></filename></entry>