diff --git a/devices/gl-ar750/default.nix b/devices/gl-ar750/default.nix
index 3ab1401..9bb40f5 100644
--- a/devices/gl-ar750/default.nix
+++ b/devices/gl-ar750/default.nix
@@ -18,7 +18,7 @@
   };
 
   description = ''
-    GL.INet GL-AR750
+    GL.iNet GL-AR750
     ****************
 
     The GL-AR750 "Creta" travel router features:
@@ -30,7 +30,7 @@
      - 16MB NOR Flash
      - supported in OpenWrt by the "ath79" SoC family
 
-    As with many GL.INet devices, the stock vendor firmware
+    As with many GL.iNet devices, the stock vendor firmware
     is a fork of OpenWrt, meaning that the plain binary
     ``firmware.bin`` that Liminix builds can be flashed using the
     vendor web UI and the U-Boot emergency "unbrick" routine
diff --git a/devices/gl-mt300a/default.nix b/devices/gl-mt300a/default.nix
index eecb8e7..73aec7d 100644
--- a/devices/gl-mt300a/default.nix
+++ b/devices/gl-mt300a/default.nix
@@ -1,4 +1,4 @@
-# GL.INet GL-MT300A
+# GL.iNet GL-MT300A
 
 {
   system = {
@@ -12,12 +12,12 @@
   };
 
   description = ''
-    GL.Inet GL-MT300A
+    GL.iNet GL-MT300A
     ********************
 
     The GL-MT300A is based on a MT7620 chipset.
 
-    The GL-Inet pocket router range makes nice cheap hardware for
+    The GL.iNet pocket router range makes nice cheap hardware for
     playing with Liminix or similar projects. The manufacturers seem
     open to the DIY market, and the devices have a reasonable amount
     of RAM and are much easier to get serial connections than many
@@ -47,6 +47,12 @@
     expects firmware to be present in the "factory" MTD partition, so
     - assuming we want to use the wireless - we need to build MTD
     support into the kernel even if we're using TFTP root.
+
+
+    Vendor web page: https://www.gl-inet.com/products/gl-mt300a/
+
+    OpenWrt web page: https://openwrt.org/toh/gl.inet/gl-mt300a
+
   '';
 
   module = { pkgs, config, lib, ...}:
diff --git a/devices/gl-mt300n-v2/default.nix b/devices/gl-mt300n-v2/default.nix
index aaa8a33..efd840e 100644
--- a/devices/gl-mt300n-v2/default.nix
+++ b/devices/gl-mt300n-v2/default.nix
@@ -1,5 +1,3 @@
-# GL.INet GL-MT300N v2
-
 {
   system = {
     crossSystem = {
@@ -12,13 +10,18 @@
   };
 
   description = ''
-    GL.Inet GL-MT300N-v2
+    GL.iNet GL-MT300N-v2
     ********************
 
     The GL-MT300N-v2 "Mango" is is very similar to the MT300A, but is
     based on MT7628 instead of MT7620.  It's also marginally cheaper
     and comes in a yellow case not a blue one.  It's different again
     to the v1, which has only half the RAM.
+
+    Vendor web page: https://www.gl-inet.com/products/gl-mt300n-v2/
+
+    OpenWrt web page: https://openwrt.org/toh/gl.inet/gl-mt300n_v2
+
   '';
 
   module = { pkgs, config, lib, ...}:
diff --git a/doc/tutorial.rst b/doc/tutorial.rst
index 546d332..2cf438b 100644
--- a/doc/tutorial.rst
+++ b/doc/tutorial.rst
@@ -123,9 +123,9 @@ Installing on hardware
 **********************
 
 For the next example, we're going to install onto an actual hardware
-device.  These steps have been tested using a GL-iNet GL-MT300A, which
+device.  These steps have been tested using a GL.iNet GL-MT300A, which
 has been chosen for the purpose because it's cheap and easy to
-unbrick if necessary
+unbrick if necessary.
 
 .. warning:: There is always a risk of rendering your device
 	     unbootable by flashing it with an image that doesn't
@@ -227,8 +227,7 @@ example, but this time for real.
 	     with some imagination could probably still do something
 	     awful using it.
 
-Congratulations Part II! You have installed your first Liminix system on
-actual hardware - albeit that it *still* has no practical use.
+Congratulations Part II! You have installed your first Liminix system on actual hardware - albeit that it *still* has no practical use.
 
 Exercise for the reader: change the default password by editing
 :file:`examples/hello-from-mt300.nix`, and then create and upload a