diff --git a/user/troubleshooting/vpn-troubleshooting.md b/user/troubleshooting/vpn-troubleshooting.md
index 5ea4cc12..67882f7b 100644
--- a/user/troubleshooting/vpn-troubleshooting.md
+++ b/user/troubleshooting/vpn-troubleshooting.md
@@ -8,7 +8,7 @@ permalink: /doc/vpn-troubleshooting/
 
 ## Tips 
 
-* Check the VPN service's log in the VPN VM by running:
+* If using qubes-vpn, check the VPN service's log in the VPN VM by running:
     ~~~
     sudo journalctl -u qubes-vpn-handler
     ~~~
@@ -19,10 +19,13 @@ permalink: /doc/vpn-troubleshooting/
 * Use `iptables -L -v` and `iptables -L -v -t nat` to check firewall rules. The latter shows the critical PR-QBS chain that enables DNS forwarding.
 
 ## VPN does not reconnect after suspend 
-After suspend/resume, your VPN may not automatically reconnect. In order to get it to work, you must kill your VPN system and restart it. 
+
+This applies when using OpenVPN. 
+
+After suspend/resume, OpenVPN may not automatically reconnect. In order to get it to work, you must kill the OpenVPN process and restart it. 
 
 ## VPN stuck at "Ready to start link" 
 
-After setting up your VPN system and restarting the VM, you may be repeatedly getting the popup "Ready to start link", but the VPN isn't connected. 
+After setting up OpenVPN and restarting the VM, you may be repeatedly getting the popup "Ready to start link", but the VPN isn't connected. 
 
-To figure out the root of the problem, check the VPN logs in `/var/logs/syslog`. The log may reveal issues like missing libraries, which you can then install. 
+To figure out the root of the problem, check the VPN logs in `/var/logs/syslog`. The log may reveal issues like missing OpenVPN libraries, which you can then install.