diff --git a/exercise-book/src/nrf52-hardware.md b/exercise-book/src/nrf52-hardware.md
index c3341fe1..4d6d2b9c 100644
--- a/exercise-book/src/nrf52-hardware.md
+++ b/exercise-book/src/nrf52-hardware.md
@@ -20,11 +20,11 @@ The board has several switches to configure its behavior. The out of the box con
 
 ### Windows
 
-When the development board is connected to your pc it shows up as a removable USB flash drive (named JLINK) and also as a USB Serial Device (COM port) in the Device Manager under the Ports section.
+When the nRF52-DK is connected to your PC it shows up as a removable USB Flash Drive (named JLINK) and also as a USB Serial Device (COM port) in the Device Manager under the Ports section.
 
 ### Linux
 
-When the development board is connected to your pc it shows up as a USB device under `lsusb`. The device will have a VID of `0x1366` and a PID of `0x10??` or `0x01??` (`?` is a hex digit)  -- the `0x` prefix will be omitted in the output of `lsusb`:
+When the nRF52-DK is connected to your PC it shows up as a USB device under `lsusb`. The device will have a VID of `1366` and a PID of `10xx` or `01xx`, where `x` can vary:
 
 ```console
 $ lsusb
@@ -41,7 +41,7 @@ $ ls /dev/ttyACM*
 
 ### macOS
 
-When the development board is connected to your pc it shows up as a removable USB flash drive (named JLINK) in Finder and also a USB device named "J-Link" when executing `ioreg -p IOUSB -b -n "J-Link"`.
+When the nRF52-DK is connected to your Mac it shows up as a removable USB flash drive (named JLINK) on the Desktop, and also a USB device named "J-Link" when executing `ioreg -p IOUSB -b -n "J-Link"`.
 
 ```console
 $ ioreg -p IOUSB -b -n "J-Link"
@@ -79,7 +79,7 @@ The device shows up as a USB Serial Device (COM port) in the Device Manager unde
 
 ### Linux
 
-The device shows up as a USB device under `lsusb`. The device will have a VID of `0x1915` and a PID of `0x521f` -- the `0x` prefix will be omitted in the output of `lsusb`:
+The dongle shows up as a USB device under `lsusb`. The device will have a VID of `0x1915` and a PID of `0x521f` -- the `0x` prefix will be omitted in the output of `lsusb`:
 
 ```console
 $ lsusb
diff --git a/exercise-book/src/nrf52-tools.md b/exercise-book/src/nrf52-tools.md
index 7438cc41..88da5efc 100644
--- a/exercise-book/src/nrf52-tools.md
+++ b/exercise-book/src/nrf52-tools.md
@@ -22,7 +22,7 @@ On Debian based distributions you can use:
 sudo apt-get install libudev-dev libusb-1.0-0-dev
 ```
 
-### Configure dongle access for non-root users
+### Configure USB Device access for non-root users
 
 Connect the dongle and check its permissions with these commands:
 
@@ -71,7 +71,7 @@ To check the permissions again, first disconnect and reconnect the dongle. Then
     crw-rw-r--+ 1 root root 189, 16 May 20 12:11 /dev/bus/usb/001/017
     ```
 
-The `+` part in `crw-rw-r--+` indicates the device can be accessed without `root` permissions.
+The `+` part in `crw-rw-r--+` indicates the device can be accessed without `root` permissions. If you have permission to access them dongle, then the nRF52-DK should also work because both were listed in the udev rules file.
 
 ### Install base rust tooling
 
@@ -152,7 +152,7 @@ In Zadig's graphical user interface,
 
 Go to [https://rustup.rs](https://rustup.rs/) and follow the instructions.
 
-Be sure to select the optional "Desktop development with C++" part of the [C++ build tools package](https://visualstudio.microsoft.com/visual-cpp-build-tools/). The installation may take up to 5.7 GB of disk space.
+You will need a C compiler to use Rust on Windows. The rustup installer will suggest you install either Visual Studio, or the Build Tools for Visual Studio - either is fine. When that is installing, be sure to select the optional "Desktop development with C++" part of the [C++ build tools package](https://visualstudio.microsoft.com/visual-cpp-build-tools/). The installation may take up to 5.7 GB of disk space. Please also be aware of the license conditions attached to these products, especially in an enterprise environment.
 
 
 ### Install rust analyzer