--- a/doc/Modem-configs	Fri Nov 03 20:45:12 2017 +0000
+++ b/doc/Modem-configs	Fri Nov 03 21:07:17 2017 +0000
@@ -12,12 +12,14 @@
 		of TCS211 from Sotovik.  This config can only be built for the
 		fcdev3b and gtamodem targets, not for c139 or pirelli.
 
-l1reconst	In this configuration most of L1 (GSM Layer 1) is recompiled
-		from reconstructed source, although this deblobbing of L1 is
-		not 100% complete yet: for the GPRS-specific L1 modules the
-		original binary object blobs are still used.  Some housekeeping
-		pieces are also recompiled from source that had to be
-		reconstructed.  This config can be built for all targets.
+l1reconst	In this configuration the Layer1 component of the firmware
+		(which came as a blob in our copy of TCS211) is recompiled from
+		reconstructed source, and the same is done for the system
+		initialization code in main.lib.  The entire chipsetsw division
+		of the firmware (now in src/cs) is thus recompiled from source,
+		either original or reconstructed, and the only components that
+		are used as blobs are the G23M PS, GPF and Nucleus.  This
+		config can be built for all targets.
 
 hybrid		This configuration is a TCS2/TCS3 hybrid.  Instead of using the
 		TCS211 version of the G23M protocol stack which we got only as
@@ -25,10 +27,11 @@
 		TCS3.2/LoCosto source, backported to work with L1 and the fw
 		foundation layers from TCS211.  ACI also had to be replaced with
 		the TCS3 version, and a special hybrid version of the cdginc
-		headers had to be constructed.  L1 is also deblobbed to the
-		same extent as in l1reconst.  Like l1reconst, this config can
-		be built for all targets, and it is currently the most deblobbed
-		(closest to full source) Magnetite config.
+		headers had to be constructed.  L1 and the init code are also
+		deblobbed as in l1reconst.  Like l1reconst, this config can be
+		built for all targets, and it is currently the most deblobbed
+		(closest to full source) Magnetite config: the only remaining
+		blobs are GPF and Nucleus.
 
 All 3 of the above configurations have CSD, fax and GPRS enabled; this
 functionality can only be exercised on those hardware targets on which both
@@ -40,11 +43,10 @@
 UART, then the data functions of the firmware are inaccessible and act as dead
 weight.
 
-Having deblobbed all of L1 except GPRS-specific modules, we are now in a
-position where we can build a hybrid config with GPRS excluded, optionally
-including or excluding FAX_AND_DATA, but I (Mychaela) would like to thoroughly
-exercise the hybrid config in its current everything-enabled state before making
-further changes to it.
+Having fully deblobbed all of L1, we are now in a position where we can build a
+hybrid config with GPRS and/or FAX_AND_DATA excluded, but I (Mychaela) would
+like to thoroughly exercise the hybrid config in its current everything-enabled
+state before making further changes to it.
 
 The deblobbing of L1 has been done in a very meticulous manner, ensuring that
 each individual reconstructed C module compiles into a strict functional