diff --git a/docs/ftldns/configfile.md b/docs/ftldns/configfile.md
index a23e97f..0671902 100755
--- a/docs/ftldns/configfile.md
+++ b/docs/ftldns/configfile.md
@@ -123,15 +123,15 @@ Specify the path and filename of FTL's SQLite3 long-term database. Setting this
 
 The location of FTL's log file. If you want to move the log file to a different place, also consider [this FAQ article](https://discourse.pi-hole.net/t/moving-the-pi-hole-log-to-another-location-device/2041).
 
-#### `PIDFILE=/var/run/pihole-FTL.pid` {#file_PIDFILE data-toc-label='Process identifier file'}
+#### `PIDFILE=/run/pihole-FTL.pid` {#file_PIDFILE data-toc-label='Process identifier file'}
 
 The file which contains the PID of FTL's main process.
 
-#### `PORTFILE=/var/run/pihole-FTL.port` {#file_PORTFILE data-toc-label='Port file'}
+#### `PORTFILE=/run/pihole-FTL.port` {#file_PORTFILE data-toc-label='Port file'}
 
 The file containing the port FTL's API is listening on.
 
-#### `SOCKETFILE=/var/run/pihole/FTL.sock` {#file_SOCKETFILE data-toc-label='Socket file'}
+#### `SOCKETFILE=/run/pihole/FTL.sock` {#file_SOCKETFILE data-toc-label='Socket file'}
 
 The file containing the socket FTL's API is listening on.
 
diff --git a/docs/ftldns/in-depth.md b/docs/ftldns/in-depth.md
index 9422f14..b7f3879 100644
--- a/docs/ftldns/in-depth.md
+++ b/docs/ftldns/in-depth.md
@@ -1,6 +1,6 @@
 ## Available interfaces
 
-Pi-hole stats can be accessed via a standard Unix socket (`var/run/pihole/FTL.sock`), a telnet-like connection (TCP socket on port `4711`) as well as indirectly via the Web API (`admin/api.php`), and the command line (`pihole -c -j`). You can out find more details below.
+Pi-hole stats can be accessed via a standard Unix socket (`/run/pihole/FTL.sock`), a telnet-like connection (TCP socket on port `4711`) as well as indirectly via the Web API (`admin/api.php`), and the command line (`pihole -c -j`). You can out find more details below.
 
 ## Command-line arguments
 
@@ -19,9 +19,9 @@ Command-line arguments can be arbitrarily combined, e.g. `pihole-FTL debug test`
 ## File locations
 
 - `/var/log/pihole-FTL.log` log file
-- `/var/run/pihole-FTL.pid` PID file
-- `/var/run/pihole-FTL.port` file containing port on which `FTL` is listening
-- `/var/run/pihole/FTL.sock` Unix socket
+- `/run/pihole-FTL.pid` PID file
+- `/run/pihole-FTL.port` file containing port on which `FTL` is listening
+- `/run/pihole/FTL.sock` Unix socket
 
 ## Linux capabilities
 
diff --git a/docs/guides/vpn/dual-VPN.md b/docs/guides/vpn/dual-VPN.md
index 1bb6060..e7616bd 100644
--- a/docs/guides/vpn/dual-VPN.md
+++ b/docs/guides/vpn/dual-VPN.md
@@ -51,7 +51,7 @@ systemctl start openvpn@server2.service
 *If your distribution does not have `systemctl` you may use the command below to start an OpenVPN daemon with your second configuration:*
 
 ```bash
-/usr/sbin/openvpn --daemon --writepid /var/run/openvpn/server2.pid --cd /etc/openvpn --config server2.conf --script-security 2
+/usr/sbin/openvpn --daemon --writepid /run/openvpn/server2.pid --cd /etc/openvpn --config server2.conf --script-security 2
 ```
 
 Finally, edit the existing `.ovpn` file used for the client connection. Update the port from the previous value to the port you used for the second instance of OpenVPN.