diff --git a/MIT b/MIT
index e9e878b..7bddbd9 100644
--- a/MIT
+++ b/MIT
@@ -1,4 +1,4 @@
-Copyright (c) 2014-2021 graysky
+Copyright (c) 2014-2022 graysky
 
 Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
 
diff --git a/arm/doc/manpage.txt b/arm/doc/manpage.txt
index aed2646..3ad3a59 100644
--- a/arm/doc/manpage.txt
+++ b/arm/doc/manpage.txt
@@ -4,13 +4,13 @@ kodi.service - Systemd service unit to run Kodi in standalone mode without the n
 DESCRIPTION
 
 NOTES ON SYSTEM SHUTDOWN/REBOOT
-Be aware that this service runs Kodi in systemd's user.slice not in the system.slice. In order to have Kodi gracefully exit, the system should be called to shutdown or to reboot using the respective Kodi actions not by a call to systemctl.
+Be aware that this service runs Kodi in systemd's system.slice not in the user.slice. In order to have Kodi gracefully exit, the system should be called to shutdown or to reboot using the respective Kodi actions not by a call to systemctl.
 
 This is NOT recommended:
 
 	# systemctl reboot
 
-If you do reboot or shutdown via a call to systemctl, this will result in systemd killing the cg too quickly and data loss to your Kodi profile will occur. When Kodi exits cleanly, it will save GUI settings, media settings, Kodi uptime etc. In principal this is no different than data loss occurring from a user doing work when a sysadmin issues a reboot command without prior warning. While it is possible to run Kodi in systemd's system.slice instead, doing so makes it difficult to use USB mounts within Kodi and to use pulseaudio for Kodi sessions.
+If you do reboot or shutdown via a call to systemctl, this will result in systemd killing the cg too quickly and data loss to your Kodi profile will occur. When Kodi exits cleanly, it will save GUI settings, media settings, Kodi uptime etc. In principal this is no different than data loss occurring from a user doing work when a sysadmin issues a reboot command without prior warning. While it is possible to run Kodi in systemd's user.slice instead, doing so makes it difficult to use USB mounts within Kodi and to use pulseaudio for Kodi sessions.
 
 RECOMMENDED METHODS TO SHUTDOWN/REBOOT
 Here are several options:
diff --git a/x86/doc/kodi.service.1 b/x86/doc/kodi.service.1
index e8ebcd7..c09e4cd 100644
--- a/x86/doc/kodi.service.1
+++ b/x86/doc/kodi.service.1
@@ -14,7 +14,7 @@ Provided services are:
 .IP \(bu 3
 /usr/lib/systemd/system/kodi-wayland.service
 .SH NOTES ON SYSTEM SHUTDOWN/REBOOT
-Be aware that these services run Kodi in systemd's user.slice not in the system.slice. In order to have Kodi gracefully exit, the system should be called to shutdown or to reboot using the respective Kodi actions not by a call to systemctl.
+Be aware that these services run Kodi in systemd's system.slice not in the user.slice. In order to have Kodi gracefully exit, the system should be called to shutdown or to reboot using the respective Kodi actions not by a call to systemctl.
 .PP
 This is NOT recommended:
 .PP
@@ -24,7 +24,7 @@ This is NOT recommended:
 
 .fam T
 .fi
-If you do reboot or shutdown via a call to systemctl, this will result in systemd killing the cg too quickly and data loss to your Kodi profile will occur. When Kodi exits cleanly, it will save GUI settings, media settings, Kodi uptime etc. In principal this is no different than data loss occurring from a user doing work when a sysadmin issues a reboot command without prior warning. While it is possible to run Kodi in systemd's system.slice instead, doing so makes it difficult to use USB mounts within Kodi and to use pulseaudio for Kodi sessions.
+If you do reboot or shutdown via a call to systemctl, this will result in systemd killing the cg too quickly and data loss to your Kodi profile will occur. When Kodi exits cleanly, it will save GUI settings, media settings, Kodi uptime etc. In principal this is no different than data loss occurring from a user doing work when a sysadmin issues a reboot command without prior warning. While it is possible to run Kodi in systemd's user.slice instead, doing so makes it difficult to use USB mounts within Kodi and to use pulseaudio for Kodi sessions.
 .SH RECOMMENDED METHODS TO SHUTDOWN/REBOOT
 Here are several options:
 .IP \(bu 3