diff --git a/docs/ftldns/blockingmode.md b/docs/ftldns/blockingmode.md
index 7199fe2af..05dd17f59 100644
--- a/docs/ftldns/blockingmode.md
+++ b/docs/ftldns/blockingmode.md
@@ -9,7 +9,7 @@ Pi-hole *FTL*DNS currently supports the following modes for blocking queries:
 Each mode has their advantages and drawbacks which will be discussed in detail below.
 
 !!! note
-    In order to configure a blocking mode, you must edit the *FTL*DNS configuration file (`/etc/pihole/pihole-FTL.conf`). Once you've made any changes to the blocking mode, you must restart Pi-hole with `pihole restartdns`.
+    In order to configure a blocking mode, you must edit the *FTL*DNS configuration file (`/etc/pihole/pihole-FTL.conf`). Once you've made any changes to the blocking mode, you must restart Pi-hole FTL (e.g `sudo service pihole-FTL restart` `sudo systemctl restart pihole-FTL`).
 
 ## Pi-hole's unspecified IP or NULL blocking mode
 
diff --git a/docs/ftldns/dnsmasq_warn.md b/docs/ftldns/dnsmasq_warn.md
index b92c9abb7..4eebc9517 100644
--- a/docs/ftldns/dnsmasq_warn.md
+++ b/docs/ftldns/dnsmasq_warn.md
@@ -133,7 +133,7 @@ Warnings commonly seen in `dnsmasq`'s log file (`/var/log/pihole/pihole.log`) an
     edns-packet-max=1232
     ```
 
-    After running `pihole restartdns` your Pi-hole will not even try larger packet sizes (the default is 4096). Check out our [unbound guide](../guides/dns/unbound.md) for a comment about the particular value of `1232` or reference [this comment](https://discourse.pi-hole.net/t/dnsmasq-warn-reducing-dns-packet-size/51803/31) regarding the various allowed packet sizes for the various upstream DNS servers.
+    After restarting pihole-FTL it will not even try larger packet sizes (the default is 4096). Check out our [unbound guide](../guides/dns/unbound.md) for a comment about the particular value of `1232` or reference [this comment](https://discourse.pi-hole.net/t/dnsmasq-warn-reducing-dns-packet-size/51803/31) regarding the various allowed packet sizes for the various upstream DNS servers.
 
 !!! warning "Ignoring query from non-local network"
 
diff --git a/docs/group_management/example.md b/docs/group_management/example.md
index a7f6e6bce..017adb3fb 100644
--- a/docs/group_management/example.md
+++ b/docs/group_management/example.md
@@ -5,7 +5,7 @@ In this example, we describe how to set up a blocking rule for three specific cl
 Don't forget to run
 
 ```bash
-pihole restartdns reload-lists
+pihole reloadlists
 ```
 
 after your database modifications to have FTL flush its internal domain-blocking cache (separate from the DNS cache).
diff --git a/docs/guides/misc/tor/setup.md b/docs/guides/misc/tor/setup.md
index 36e81da62..4dc7f5524 100644
--- a/docs/guides/misc/tor/setup.md
+++ b/docs/guides/misc/tor/setup.md
@@ -28,7 +28,7 @@ If you want a recognizable hostname for the Tor DNS in your Pi-hole GUI statisti
 Restart Pi-hole DNS Server for the `/etc/hosts` changes to take effect
 
 ```bash
-sudo pihole restartdns
+sudo service pihole-FTL restart
 ```
 
 ## Testing your configuration
diff --git a/docs/regex/overview.md b/docs/regex/overview.md
index 70bc19d5f..bba89ed17 100644
--- a/docs/regex/overview.md
+++ b/docs/regex/overview.md
@@ -16,9 +16,9 @@ There are two locations where regex filters are important:
 *FTL*DNS reads in regular expression filters from the two [`regex` database views](../database/gravity/index.md).
 To tell *FTL*DNS to reload the list of regex filters, either:
 
-- Execute `pihole restartdns reload-lists` or
+- Execute `pihole reloadlists` or
 - Send `SIGHUP` to `pihole-FTL` (`sudo killall -SIGHUP pihole-FTL`) or
-- Restart the service (`sudo service pihole-FTL restart`)
+- Restart the service (`sudo service pihole-FTL restart` or `sudo systemctl restart pihole-FTL`)
 
 The first command is to be preferred as it ensures that the DNS cache itself remains intact. Hence, it is also the fastest of the available options.