Spelling fixes.

NEWS

@@ -233,7 +233,7 @@ CHANGES WITH 183:
           to be used as drop-in files.
 
         * systemd and logind now handle system sleep states, in
-          particulary suspending and hibernating.
+          particular suspending and hibernating.
 
         * logind now implements a sleep/shutdown/idle inhibiting logic
           suitable for a variety of uses. Soonishly Lennart will blog

README

@@ -71,7 +71,7 @@ REQUIREMENTS:
         includes systemd-hostnamed.
 
         Note that D-Bus can link against libsystemd-login.so, which
-        results in a cyclic build dependency. To accomodate for this
+        results in a cyclic build dependency. To accommodate for this
         please build D-Bus without systemd first, then build systemd,
         then rebuild D-Bus with systemd support.
 

TODO

@@ -47,7 +47,7 @@ Features:
 
 * man: clarify that time-sync.target is not only sysv compat but also useful otherwise. Same for similar targets
 
-* journalctl should complain if run with uid != 0 and no persistant logs exist
+* journalctl should complain if run with uid != 0 and no persistent logs exist
 
 * .device aliases need to be implemented with the "following" logic, probably.
 

man/bootup.xml

@@ -53,7 +53,7 @@
                 <para>A number of different components are involved in the
                 system boot. Immediately after power-up, the system
                 BIOS will do minimal hardware initialization, and hand
-                control over to a boot loader stored on a persistant
+                control over to a boot loader stored on a persistent
                 storage device. This boot loader will then invoke an
                 OS kernel from disk (or the network). In the Linux
                 case this kernel now (optionally) extracts and

man/journalctl.xml

@@ -141,7 +141,7 @@
                                 <term><option>-f</option></term>
 
                                 <listitem><para>Show only most recent
-                                journal entries, and continously print
+                                journal entries, and continuously print
                                 new entries as they are appended to
                                 the journal.</para></listitem>
                         </varlistentry>
@@ -189,9 +189,9 @@
                                 is very similar but shows monotonic
                                 timestamps instead of wallclock
                                 timestamps. <literal>verbose</literal>
-                                shows the full structered entry items
+                                shows the full structured entry items
                                 with all
-                                fiels. <literal>export</literal>
+                                fields. <literal>export</literal>
                                 serializes the journal into a binary
                                 (but mostly text-based) stream
                                 suitable for backups and network
@@ -209,7 +209,7 @@
                                 <term><option>-q</option></term>
 
                                 <listitem><para>Suppresses any warning
-                                message regarding inaccessable system
+                                message regarding inaccessible system
                                 journals when run as normal
                                 user.</para></listitem>
                         </varlistentry>

man/journald.conf.xml

@@ -174,7 +174,7 @@
                                 influences the granularity in which
                                 disk space is made available through
                                 rotation, i.e. deletion of historic
-                                data. Defaults to one eigth of the
+                                data. Defaults to one eighth of the
                                 values configured with
                                 <varname>SystemMaxUse=</varname> and
                                 <varname>RuntimeMaxUse=</varname>, so
@@ -317,7 +317,7 @@
                                 directory
                                 <filename>/var/log/journal</filename>
                                 is not created if needed, so that its
-                                existance controls where log data
+                                existence controls where log data
                                 goes. <literal>none</literal> turns
                                 off all storage, all log data received
                                 will be dropped. Forwarding to other

man/sd_journal_open.xml

@@ -92,7 +92,7 @@
                 only journal files generated on the local machine will
                 be opened. <literal>SD_JOURNAL_RUNTIME_ONLY</literal>
                 makes sure only volatile journal files will be opened,
-                excluding those which are stored on persistant
+                excluding those which are stored on persistent
                 storage. <literal>SD_JOURNAL_SYSTEM_ONLY</literal>
                 will ensure that only journal files of system services
                 and the kernel (in opposition to user session processes) will

man/sd_journal_print.xml

@@ -172,7 +172,7 @@ sd_journal_send("MESSAGE=Hello World, this is PID %lu!", (unsigned long) getpid(
 
                 <para><citerefentry><refentrytitle>syslog</refentrytitle><manvolnum>3</manvolnum></citerefentry>
                 and and <function>sd_journal_print()</function> may
-                largely be used interchangably
+                largely be used interchangeably
                 functionality-wise. However, note that log messages
                 logged via the former take a different path to the
                 journal server than the later, and hence global

man/sd_journal_seek_head.xml

@@ -92,7 +92,7 @@
 
                 <para><function>sd_journal_seek_head()</function>
                 seeks to the beginning of the journal, i.e. the oldest
-                avilable entry.</para>
+                available entry.</para>
 
                 <para>Similar,
                 <function>sd_journal_seek_tail()</function> may be
@@ -110,7 +110,7 @@
                 (wallclock) timestamp, i.e. CLOCK_REALTIME. Note that
                 the realtime clock is not necessary monotonic. If a
                 realtime timestamp is ambiguous it is not defined
-                which position is seeked to.</para>
+                which position is sought to.</para>
 
                 <para><function>sd_journal_seek_cursor()</function>
                 seeks to the entry located at the specified cursor
@@ -125,12 +125,12 @@
                 may be retrieved via
                 <citerefentry><refentrytitle>sd_journal_get_data</refentrytitle><manvolnum>3</manvolnum></citerefentry>. If
                 no entry exists that matches exactly the specified
-                seek address the next closest is seeked to. If
+                seek address the next closest is sought to. If
                 <citerefentry><refentrytitle>sd_journal_next</refentrytitle><manvolnum>3</manvolnum></citerefentry>
-                is used the closest following entry will be seeked to,
+                is used the closest following entry will be sought to,
                 if
                 <citerefentry><refentrytitle>sd_journal_previous</refentrytitle><manvolnum>3</manvolnum></citerefentry>
-                is used the closest preceeding entry is seeked
+                is used the closest preceding entry is sought
                 to.</para>
         </refsect1>
 

man/sd_seat_get_active.xml

@@ -118,7 +118,7 @@
                 <para><function>sd_seat_can_multi_session()</function>
                 may be used to determine whether a specific seat is
                 capable of multi-session, i.e. allows multiple login
-                sessions in parallel (whith only one being active at a
+                sessions in parallel (with only one being active at a
                 time).</para>
 
                 <para><function>sd_seat_can_tty()</function> may be

man/systemctl.xml

@@ -447,7 +447,7 @@
                                 <term><option>-f</option></term>
 
                                 <listitem><para>When used with
-                                <command>status</command> continously
+                                <command>status</command> continuously
                                 prints new journal entries as they are
                                 appended to the
                                 journal.</para></listitem>
@@ -1202,10 +1202,10 @@
                                 directory, and the path to the new
                                 system manager binary below it to
                                 execute as PID 1. If the latter is
-                                ommitted or the empty string, a
+                                omitted or the empty string, a
                                 systemd binary will automatically be
                                 searched for and used as init. If the
-                                system manager path is ommitted or
+                                system manager path is omitted or
                                 equal the empty string the state of
                                 the initrd's system manager process is
                                 passed to the main system manager,

man/systemd-inhibit.xml

@@ -110,7 +110,7 @@
                                 inhibiting
                                 reboot/power-off/halt/kexec,
                                 suspending/hibernating, resp. the
-                                automatic idle detection. If ommitted
+                                automatic idle detection. If omitted
                                 defaults to
                                 <literal>idle:sleep:shutdown</literal>,
                                 i.e. takes all possible

man/systemd-readahead-replay.service.xml

@@ -85,7 +85,7 @@
                 and
                 <filename>systemd-readahead-replay.service</filename>
                 are activated at boot so that access patterns from the
-                preceeding boot are replayed and new data collected
+                preceding boot are replayed and new data collected
                 for the subsequent boot. However, on read-only media
                 where the collected data cannot be stored it might
                 be a good idea to disable

man/systemd.conf.xml

@@ -125,7 +125,7 @@
                                 hierarchy. By default systemd will
                                 mount all controllers which are
                                 enabled in the kernel in individual
-                                hierachies, with the exception of
+                                hierarchies, with the exception of
                                 those listed in this setting. Takes a
                                 space separated list of comma
                                 separated controller names, in order

man/systemd.exec.xml

@@ -931,18 +931,18 @@
                                 <term><varname>BlockIOWriteBandwidth=</varname></term>
 
                                 <listitem><para>Set the per-device
-                                overall block IO bandwith limit for
+                                overall block IO bandwidth limit for
                                 the executed processes. Takes a space
                                 separated pair of a file path and a
-                                bandwith value (in bytes per second)
+                                bandwidth value (in bytes per second)
                                 to specify the device specific
                                 bandwidth. The file path may be
                                 specified as path to a block device
                                 node or as any other file in which
                                 case the backing block device of the
                                 file system of the file is determined.
-                                If the bandwith is suffixed with K, M,
+                                If the bandwidth is suffixed with K, M,
-                                G, or T the specified bandwith is
+                                G, or T the specified bandwidth is
                                 parsed as Kilobytes, Megabytes,
                                 Gigabytes, resp. Terabytes (Example:
                                 "/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0
@@ -951,7 +951,7 @@
                                 and
                                 <literal>blkio.write_bps_device</literal>
                                 control group attributes. Use this
-                                option multiple times to set bandwith
+                                option multiple times to set bandwidth
                                 limits for multiple devices. For
                                 details about these control group
                                 attributes see <ulink

src/core/load-fragment.c

@@ -1910,7 +1910,7 @@ int config_parse_unit_blkio_bandwidth(const char *filename, unsigned line, const
         }
 
         if (parse_bytes(l[1], &bytes) < 0 || bytes <= 0) {
-                log_error("[%s:%u] Failed to parse block IO bandwith value, ignoring: %s", filename, line, rvalue);
+                log_error("[%s:%u] Failed to parse block IO bandwidth value, ignoring: %s", filename, line, rvalue);
                 strv_free(l);
                 return 0;
         }

src/core/shutdown.c

@@ -116,7 +116,7 @@ static int pivot_to_new_root(void) {
 
         if (pivot_root(".", "oldroot") < 0) {
                 log_error("pivot failed: %m");
-                /* only chroot if pivot root succeded */
+                /* only chroot if pivot root succeeded */
                 return -errno;
         }
 

src/core/unit.h

@@ -220,7 +220,7 @@ struct Unit {
         /* Ignore this unit when snapshotting */
         bool ignore_on_snapshot;
 
-        /* Did the last condition check suceed? */
+        /* Did the last condition check succeed? */
         bool condition_result;
 
         bool in_load_queue:1;

src/journal/lookup3.c

@@ -315,7 +315,7 @@ uint32_t jenkins_hashlittle( const void *key, size_t length, uint32_t initval)
      * rest of the string.  Every machine with memory protection I've seen
      * does it on word boundaries, so is OK with this.  But VALGRIND will
      * still catch it and complain.  The masking trick does make the hash
-     * noticably faster for short strings (like English words).
+     * noticeably faster for short strings (like English words).
      */
 #ifndef VALGRIND
 
@@ -499,7 +499,7 @@ void jenkins_hashlittle2(
      * rest of the string.  Every machine with memory protection I've seen
      * does it on word boundaries, so is OK with this.  But VALGRIND will
      * still catch it and complain.  The masking trick does make the hash
-     * noticably faster for short strings (like English words).
+     * noticeably faster for short strings (like English words).
      */
 #ifndef VALGRIND
 
@@ -675,7 +675,7 @@ uint32_t jenkins_hashbig( const void *key, size_t length, uint32_t initval)
      * rest of the string.  Every machine with memory protection I've seen
      * does it on word boundaries, so is OK with this.  But VALGRIND will
      * still catch it and complain.  The masking trick does make the hash
-     * noticably faster for short strings (like English words).
+     * noticeably faster for short strings (like English words).
      */
 #ifndef VALGRIND
 

src/journal/sd-journal.c

@@ -745,7 +745,7 @@ static int next_with_matches(
                 return journal_file_next_entry(f, c, cp, direction, ret, offset);
 
         /* If we have a match then we look for the next matching entry
-         * wiht an offset at least one step larger */
+         * with an offset at least one step larger */
         return next_for_match(j, j->level0, f, direction == DIRECTION_DOWN ? cp+1 : cp-1, direction, ret, offset);
 }
 

units/syslog.target

@@ -15,5 +15,5 @@ Documentation=http://www.freedesktop.org/wiki/Software/systemd/syslog
 
 # Avoid that we conflict with shutdown.target, so that we can stay
 # until the very end and do not cancel shutdown.target if we should
-# hapen to be activated very late.
+# happen to be activated very late.
 DefaultDependencies=no