--- a/doc/Modem-configs	Fri Jan 12 01:39:11 2018 +0000
+++ b/doc/Modem-configs	Fri Jan 12 07:22:16 2018 +0000
@@ -1,9 +1,11 @@
 Modem configurations
 ====================
 
-If you would like to build our Magnetite firmware in the AT-command-controlled
-modem configuration (not the C-Sample UI demo on the Mot C139), you have 3
-specific configurations to choose from, differing in the level of deblobbing:
+If you would like to build our Magnetite firmware for the Standard Modem
+functionality (voice, SMS, CSD, fax and GPRS services enabled, control via AT
+commands, no UI, two UARTs are expected to be available for the AT command
+interface and for the RVTMUX binary packet interface), you have 3 specific
+configurations to choose from, differing in the level of deblobbing:
 
 classic		This configuration replicates classic TCS211, just like
 		leo2moko from 2013.  Almost all of the original binary blob
@@ -43,10 +45,10 @@
 UART, then the data functions of the firmware are inaccessible and act as dead
 weight.
 
-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.
+Having fully deblobbed all of L1, we now have the ability to build our hybrid
+firmware not only for the Standard Modem functionality with all data services
+enabled as above, but also in a stripped-down "voice pseudo-modem"
+configuration - see the Voice-pseudo-modem article.
 
 The deblobbing of L1 has been done in a very meticulous manner, ensuring that
 each individual reconstructed C module compiles into a strict functional