tree-wide: fix a couple of typos

As reported by Fossies.org.

src/basic/time-util.c

@@ -1703,7 +1703,7 @@ TimestampStyle timestamp_style_from_string(const char *s) {
         t = (TimestampStyle) string_table_lookup(timestamp_style_table, ELEMENTSOF(timestamp_style_table), s);
         if (t >= 0)
                 return t;
-        if (STRPTR_IN_SET(s, "µs", "μs")) /* acccept both µ symbols in unicode, i.e. micro symbol + greek small letter mu. */
+        if (STRPTR_IN_SET(s, "µs", "μs")) /* accept both µ symbols in unicode, i.e. micro symbol + Greek small letter mu. */
                 return TIMESTAMP_US;
         if (STRPTR_IN_SET(s, "µs+utc", "μs+utc"))
                 return TIMESTAMP_US_UTC;

src/basic/xattr-util.c

@@ -152,9 +152,9 @@ int fd_getcrtime_at(
         /* So here's the deal: the creation/birth time (crtime/btime) of a file is a relatively newly supported concept
          * on Linux (or more strictly speaking: a concept that only recently got supported in the API, it was
          * implemented on various file systems on the lower level since a while, but never was accessible). However, we
-         * needed a concept like that for vaccuuming algorithms and such, hence we emulated it via a user xattr for a
+         * needed a concept like that for vacuuming algorithms and such, hence we emulated it via a user xattr for a
          * long time. Starting with Linux 4.11 there's statx() which exposes the timestamp to userspace for the first
-         * time, where it is available. Thius function will read it, but it tries to keep some compatibility with older
+         * time, where it is available. This function will read it, but it tries to keep some compatibility with older
          * systems: we try to read both the crtime/btime and the xattr, and then use whatever is older. After all the
          * concept is useful for determining how "old" a file really is, and hence using the older of the two makes
          * most sense. */