Update readme to reflect IPv6 support

README.md

@@ -9,12 +9,12 @@ There are many very legitimate reasons to use VPNs, such as increased privacy. I
   - You are Netflix
 
 # How to use
-Feed the vpn.txt file to your firewall or application. Ignore the 'source' folder.
+Feed the vpn-ipv4.txt file and/or the vpn-ipv6.txt file to your firewall or application. Ignore the 'source' folder.
 
 For extra effectiveness, you should probably be supplementing this with blocklists for recently abusive IPs, as these invariably include many VPNs, and lists of open proxies/tor nodes. You should be able to find everything you need in that regard at http://iplists.firehol.org. At the very least, consider using _firehol_level1_, _firehol_level2_, _firehol_abusers_1d_, and _firehol_proxies_ with this list, depending on your needs.
 
 # How to contribute
-The 'vpn.txt' file is distilled from the files in the 'source' folder. I usually  do that manually every two months - being mostly datacenter IPs, these change fairly infrequently. Pull requests are welcome, but you should probably not be modifying vpn.txt directly unless there's a blatant error in it. Prefer editing files in the 'source' folder when you can.
+The vpn-ipv4.txt & vpn-ipv6.txt files are distilled from the files in the 'source' folder. I usually  do that manually every two months - being mostly datacenter IPs, these change fairly infrequently. Pull requests are welcome, but you should probably not be modifying vpn-ipv4.txt or vpn-ipv6.txt directly unless there's a blatant error in it. Prefer editing files in the 'source' folder when you can.
 
 # Caveats
 This list indiscriminately lists VPNs and datacenters. It may list your own server's IP range, or that of your DNS server, or legitimate search engines. It may eat your children and kidnap your dog. Before implementing, take a moment to make sure you really, definitely want to be doing whatever it is you're doing with this list.