docs: fix typo in filename: REATLIME -> REALTIME

diff --git a/TODO b/TODO
index 868b65ddaf0f692e6da79a77f1efc730278d8982..f36399044ec3a7b181dfca2e7abb7b3aab85120c 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1860,7 +1860,7 @@ Features:
 
 * fstab-generator: default to tmpfs-as-root if only usr= is specified on the kernel cmdline
 
-* docs: bring https://systemd.io/MY_SERVICE_CANT_GET_REATLIME up to date
+* docs: bring https://systemd.io/MY_SERVICE_CANT_GET_REALTIME up to date
 
 * add a job mode that will fail if a transaction would mean stopping
   running units. Use this in timedated to manage the NTP service

diff --git a/docs/FAQ.md b/docs/FAQ.md
index 3b03726c9decabf96fdf10ed65b00f44c23374b9..02be27fcaf25592c4bec1be78a5eea45f7637f2d 100644 (file)
--- a/docs/FAQ.md
+++ b/docs/FAQ.md
@@ -104,7 +104,7 @@ A: Use:
 
 **Q: Whenever my service tries to acquire RT scheduling for one of its threads this is refused with EPERM even though my service is running with full privileges. This works fine on my non-systemd system!**
 
-A: By default, systemd places all systemd daemons in their own cgroup in the "cpu" hierarchy. Unfortunately, due to a kernel limitation, this has the effect of disallowing RT entirely for the service. See [My Service Can't Get Realtime!](/MY_SERVICE_CANT_GET_REATLIME) for a longer discussion and what to do about this.
+A: By default, systemd places all systemd daemons in their own cgroup in the "cpu" hierarchy. Unfortunately, due to a kernel limitation, this has the effect of disallowing RT entirely for the service. See [My Service Can't Get Realtime!](/MY_SERVICE_CANT_GET_REALTIME) for a longer discussion and what to do about this.
 
 **Q: My service is ordered after `network.target` but at boot it is still called before the network is up. What's going on?**
 

diff --git a/docs/MY_SERVICE_CANT_GET_REATLIME.md b/docs/MY_SERVICE_CANT_GET_REALTIME.md
similarity index 100%
rename from docs/MY_SERVICE_CANT_GET_REATLIME.md
rename to docs/MY_SERVICE_CANT_GET_REALTIME.md