diff --git a/enforcement-case-studies.tex b/enforcement-case-studies.tex
index 3274bf4..fc29afe 100644
--- a/enforcement-case-studies.tex
+++ b/enforcement-case-studies.tex
@@ -281,16 +281,11 @@ and present as exemplars worthy of emulation.
 
 This case study therefore examines the entire life-cycle of a GPL compliance
 investigation: from product purchase, to source request, to CCS review.
-This case study does a step-by-step build and installation analysis of  one
-of the best Complete, Corresponding Source (CCS) releases we've seen.  The
-CSS release studied here was provided for the binary distribution of a
-physical product by ThinkPenguin.  The product is the model
-``TPE-NWIFIROUTER'', a wireless router.
-
-The method of
-distribution (complete source accompanying the product) and the way the source
-was laid out provide very good examples of how to make things easier for both
-the distributor and the purchaser of the hardware containing GPLed components.
+Specifically, this chapter discusses the purchase, CCS provision, and a
+step-by-step build and installation analysis of a specific, physical,
+embedded electronics product.  The product in question is
+\href{https://www.thinkpenguin.com/gnu-linux/free-software-wireless-n-broadband-router-gnu-linux-tpe-nwifirouter}{the
+  ``TPE-NWIFIROUTER'' wireless router by ThinkPenguin}.
 
 \section{Root Filesystem and Kernel Compilation}