diff --git a/Create_NetTests.md b/Create_NetTests.md
index 70d0ba5..b29ea36 100644
--- a/Create_NetTests.md
+++ b/Create_NetTests.md
@@ -30,18 +30,32 @@ The tests are:
 
 * **SuccessfullyDHCPs** - This test succeeds when a computer successfully gets a DHCP IP address from the specified server, firewall, etc.
  
-* HelpRequest, 
-* ReadContextHelp, 
-* FailedPing,
-* DHCPServerEnabled, 
-* SuccessfullyTraceroutes,
-* LockAll, 
-* LockIP, 
-* LockRoute, 
-* LockNic, 
-* LockDHCP, 
-* LockGateway,
-* LockVLANsOnHost, 
-* LockNicVLAN, 
-* LockInterfaceVLAN, 
-* LockVLANNames
+* **HelpRequest** - This was mainly added so you can teach someone to use the built-in help system.  You specify the help level they have to choose for it to be marked complete.
+
+* **ReadContextHelp** - If you have a Tag on your puzzle (say, DHCP), it puts a button to open up the context help on DHCP.  If they click that button, then the test is marked as complete.
+
+* **FailedPing** - Use this carefully.  If a ping from one machine to another fails for any reason, then the test is marked as complete.  You are supposed to use it for things like making a firewall rule to keep VLAN1 from accessing VLAN2.  But, someone could yank a cable between the computer and the switch, and make the ping fail.  You may need to lock a lot of things to make an indestructible test.  Or, if your students are submitting the homework to you, you get to see if they yanked a wire or made the firewall rule.
+
+* **DHCPServerEnabled** - This test succeeds if they click the DHCP server enabled checkmark on a server / firewall.  You may want to have a PC that is set up to receive DHCP, which has a test that it gets an IP that is local to another PC on the network.  That way the DHCP server needs to actually serve out good IP addresses.
+
+* **SuccessfullyTraceroutes** - If you are trying to show traceroute, this test makes sure that someone successfully does a traceroute to another computer.  It means that the network routing between the two is working.
+
+* **LockAll** - Lock everything on the device that can be locked down.  Do not let people delete it, or change it.  Do this for things that are critical to the functioning of the test.
+
+* **LockIP** - Do not let the IP address on the specified network card be changed.
+
+* **LockRoute** - Do not let the specified route be altered.  It is amazing how creative people can be.  Lock this route down, just in case.
+
+* **LockNic** - Do not let the network card be changed (MAC address, IP address, multiple interfaces, etc)
+
+* **LockDHCP** - Lock the DHCP settings on the server / router.
+ 
+* **LockGateway** - Lock the gateway on this device.
+
+* **LockVLANsOnHost** - Lock all the VLANs on this host.
+
+* **LockNicVLAN** - Lock the VLANS on the one network card
+
+* **LockInterfaceVLAN** - Lock the VLANs on the one network card interface
+
+* **LockVLANNames** - Lock the VLAN names