diff --git a/man/systemd-cgtop.xml b/man/systemd-cgtop.xml
index 074eeb246b..f08304d300 100644
--- a/man/systemd-cgtop.xml
+++ b/man/systemd-cgtop.xml
@@ -47,7 +47,7 @@
 
     <para>Resource usage is only accounted for control groups with the appropriate controllers turned on:
     <literal>cpu</literal> controller for CPU usage, <literal>memory</literal> controller for memory usage,
-    and <literal>io</literal> contoller for disk I/O consumption. If resource monitoring for these resources
+    and <literal>io</literal> controller for disk I/O consumption. If resource monitoring for these resources
     is required, it is recommended to add the <varname>CPUAccounting=1</varname>,
     <varname>MemoryAccounting=1</varname> and <varname>IOAccounting=1</varname> settings in the unit files in
     question. See
diff --git a/src/libsystemd/sd-event/sd-event.c b/src/libsystemd/sd-event/sd-event.c
index 027a8dffa1..b3b3d0b4d6 100644
--- a/src/libsystemd/sd-event/sd-event.c
+++ b/src/libsystemd/sd-event/sd-event.c
@@ -4531,8 +4531,8 @@ _public_ int sd_event_source_set_ratelimit_expire_callback(sd_event_source *s, s
 _public_ int sd_event_source_get_ratelimit(sd_event_source *s, uint64_t *ret_interval, unsigned *ret_burst) {
         assert_return(s, -EINVAL);
 
-        /* Querying whether an event source has ratelimiting configured is not a loggable offsense, hence
-         * don't use assert_return(). Unlike turning on ratelimiting it's not really a programming error */
+        /* Querying whether an event source has ratelimiting configured is not a loggable offense, hence
+         * don't use assert_return(). Unlike turning on ratelimiting it's not really a programming error. */
         if (!EVENT_SOURCE_CAN_RATE_LIMIT(s->type))
                 return -EDOM;