# HG changeset patch
# User Andrey Alexeev <andrew@nginx.com>
# Date 1334829295 0
# Node ID 2abd1998a0ccccc74cb701cd9bc3535cc69ccb4b
# Parent  78ab3599e1fe5e2422e64460fa7d1868cae09a52
- Added a couple of things about flushing DNS resolver cache

diff -r 78ab3599e1fe -r 2abd1998a0cc xml/en/docs/welcome_nginx_facebook.xml
--- a/xml/en/docs/welcome_nginx_facebook.xml	Fri Apr 13 12:28:23 2012 +0000
+++ b/xml/en/docs/welcome_nginx_facebook.xml	Thu Apr 19 09:54:55 2012 +0000
@@ -102,10 +102,16 @@
 </listitem>
 
 <listitem>
-Try to clear browser data (cache, cookies etc.), e.g. perform
-"Clear Browsing Data (Chrome)". Caution: you may be
-deleting saved passwords information here, so do it carefully
-and check what exact actions you are performing.
+If you change DNS settings, clear your DNS resolver cache. On
+Microsoft Windows it is done with the following command:
+Start > Run > ipconfig /flushdns
+</listitem>
+
+<listitem>
+Clear browser data (cache, cookies etc.), e.g. in Chrome
+find and click "Clear Browsing Data" (Settings > Under the Hood).
+Caution: you may be deleting saved passwords information here,
+so do it carefully and check what exact actions you are performing.
 </listitem>
 
 <listitem>
@@ -116,11 +122,11 @@
 
 <listitem>
 If cleaning "hosts" file (when applicable), changing
-DNS servers to Google Public DNS, or fixing your browser
-configuration have helped, it might be that there's a malware
-somewhere on your PC or around. It makes perfect sense then
-to run a number of checks using your preferred
-anti-virus/anti-malware tools.
+DNS servers to Google Public DNS, flushing DNS resolver cache,
+or fixing your browser configuration have helped, it might be
+that there's a malware somewhere on your PC or around.
+It makes perfect sense then to run a number of checks using
+your preferred anti-virus/anti-malware tools.
 </listitem>
 </list>
 </para>