Clarify PhantomJS command window problem with node's phantomjs

lib/Selenium/PhantomJS.pm

@@ -28,10 +28,18 @@ If you're curious whether your Selenium::PhantomJS instance is using a
 separate PhantomJS binary, or through the selenium server, you can check
 the C<binary_mode> attr after instantiation.
 
-N.B. If you're on Windows, we're probably going to fail at closing the
-command window that runs the PhantomJS binary. Feel free to bug us
-over at L<Github|https://github.com/gempesaw/Selenium-Remote-Driver>
-and/or tell us how to fix it if it's a blocking issue for you. Thanks!
+    my $driver = Selenium::PhantomJS->new;
+    print $driver->binary_mode;
+
+N.B. - if you're using Windows and you installed C<phantomjs> via
+C<npm install -g phantomjs>, there is a very high probability that we
+will _not_ close down your phantomjs binary correctly after your
+test. You will be able to tell if we leave around empty command
+windows that you didn't start yourself. The easiest way to fix this is
+to download PhantomJS manually from their
+L<website|http://phantomjs.org/download.html> and put it in your
+c<%PATH%>. If this is a blocking issue for you, let us know in
+L<Github|https://github.com/gempesaw/Selenium-Remote-Driver>; thanks!
 
 =cut