man: Fix small typo: s/seperate/separate/

src/initreq.h

@@ -58,7 +58,7 @@ struct init_request_bsd {
 
 /*
  *	Because of legacy interfaces, "runlevel" and "sleeptime"
- *	aren't in a seperate struct in the union.
+ *	aren't in a separate struct in the union.
  *
  *	The weird sizes are because init expects the whole
  *	struct to be 384 bytes.

src/logger.c

@@ -514,7 +514,7 @@ static int process_event(Server *s, struct epoll_event *ev) {
         /* Yes, this is a bit ugly, we assume that that valid pointers
          * are > SD_LISTEN_FDS_START+SERVER_FD_MAX. Which is certainly
          * true on Linux (and probably most other OSes, too, since the
-         * first 4k usually are part of a seperate null pointer
+         * first 4k usually are part of a separate null pointer
          * dereference page. */
 
         if (PTR_TO_INT(ev->data.ptr) >= SD_LISTEN_FDS_START &&

src/sd-daemon.h

@@ -171,7 +171,7 @@ int sd_is_socket_unix(int fd, int type, int listening, const char *path, size_t
 
 /*
   Informs systemd about changed daemon state. This takes a number of
-  newline seperated environment-style variable assignments in a
+  newline separated environment-style variable assignments in a
   string. The following variables are known:
 
      READY=1      Tells systemd that daemon startup is finished (only

src/test-job-type.c

@@ -50,7 +50,7 @@ int main(int argc, char*argv[]) {
 
                                         /* Verify that merged entries can be
                                          * merged with the same entries they
-                                         * can be merged with seperately */
+                                         * can be merged with separately */
                                         assert(!job_type_is_mergeable(a, c) || job_type_is_mergeable(d, c));
                                         assert(!job_type_is_mergeable(b, c) || job_type_is_mergeable(d, c));
 

src/unit.h

@@ -338,7 +338,7 @@ struct UnitVTable {
         void (*shutdown)(Manager *m);
 
         /* When sending out PropertiesChanged signal, which properties
-         * shall be invalidated? This is a NUL seperated list of
+         * shall be invalidated? This is a NUL separated list of
          * strings, to minimize relocations a little. */
         const char *bus_invalidating_properties;