3 files changed, 22 insertions, 10 deletions
diff --git a/src/doc/src/shared/b2qt-post-install-setup.qdocinc b/src/doc/src/shared/b2qt-post-install-setup.qdocinc
index 4444dfc..900b336 100644
--- a/src/doc/src/shared/b2qt-post-install-setup.qdocinc
+++ b/src/doc/src/shared/b2qt-post-install-setup.qdocinc
@@ -33,14 +33,23 @@
         \li Connect the running device to the development host with a USB
     cable. If the device is already connected, disconnect and reconnect the USB
     cable after running the command above.
+    \endlist
+
+    The system log files \c{/var/log/udev} and \c{/var/log/syslog} may
+    provide relevant information in case of connection problems.
 
-        \li You can confirm that the connection is working by running
-    the following shell command:
+    You can confirm that the connection is working by running the following command on Linux:
 
     \code
         <INSTALL_DIR>/Tools/b2qt/adb devices -l
     \endcode
 
+    Or the following command on Windows:
+
+    \code
+        <Android-SDK-Tools-install-dir>\platform-tools\adb.exe devices -l
+    \endcode
+
     The output should be a list of connected \B2Q (and Android) devices,
     identified with a serial number and a name. If your device is missing from
     the list, or the serial number is \c{??????}, the connection is
@@ -49,10 +58,7 @@
 
     The emulator may be listed as well. Its serial number is its IP and the port
     number: \c{192.168.56.101:5555}.
-    \endlist
 
-    The system log files \c{/var/log/udev} and \c{/var/log/syslog} may
-    provide relevant information in case of connection problems.
 //! [setting up usb access]
 
 //! [configuring device kit]
diff --git a/src/doc/src/shared/common.qdocinc b/src/doc/src/shared/common.qdocinc
index 3a449c8..6d6d18e 100644
--- a/src/doc/src/shared/common.qdocinc
+++ b/src/doc/src/shared/common.qdocinc
@@ -36,7 +36,7 @@
     device for \B2Q. In Qt Creator, select \b Tools > \b {Flash \B2Q Device}
     and follow the step-by-step instructions.
 
-    Alternatively, you can install the image from the command line using
+    On Linux, you can alternatively install the image from the command line using
     the instructions below.
 
     \b {Install from the Command Line}
diff --git a/src/doc/src/shared/detect-sd-card-device-name.qdocinc b/src/doc/src/shared/detect-sd-card-device-name.qdocinc
index dbc1a64..d934c60 100644
--- a/src/doc/src/shared/detect-sd-card-device-name.qdocinc
+++ b/src/doc/src/shared/detect-sd-card-device-name.qdocinc
@@ -19,7 +19,7 @@
 /*!
 //! [instructions]
     Plug in the SD card or reader to the development host,
-    and use the following command to find out its device name:
+    and use the following command on Linux to find out its device name:
 
     \badcode
         lsblk -d
@@ -28,12 +28,18 @@
     Removable devices such as SD cards have the value '1' in
     the \e RM column.
 
-    \warning Make sure to select the correct device, because selecting
-    the wrong one can result in a wiped hard drive.
-
     Typical device names for SD cards include \c {sdb} and
     \c {mmcblk0}. The full device path is \c {/dev/} followed by
     the name.
+
+    On Windows, use the following command to get the SD cards device name:
+    \badcode
+        wmic logicaldisk where "drivetype=2 and access=0" get deviceid, volumename
+    \endcode
+
+    \warning Make sure to select the correct device, because selecting
+    the wrong one can result in a wiped hard drive.
+
 //! [instructions]
 
 //! [unmount]