X-Git-Url: https://git.gag.com/?p=fw%2Faltos;a=blobdiff_plain;f=doc%2Fsystem-operation.inc;h=888e3891c6479941bba2276c6719e1cba5d6016a;hp=1e130976bcfc38ce33d88b1dd1e3ba529fd34744;hb=3735e1eb27afb873d60164a79a9e2769dc92b3a3;hpb=6d80b89c0bd82133dd5c93df8604f562ac49c19a

diff --git a/doc/system-operation.inc b/doc/system-operation.inc
index 1e130976..888e3891 100644
--- a/doc/system-operation.inc
+++ b/doc/system-operation.inc
@@ -7,9 +7,9 @@
 		fundamental modes, “idle” and “flight”.  Which of these modes
 		the firmware operates in is determined at start up
 		time.
-		ifdef::telemetrum,telemega,easymega[]
+		ifdef::telemetrum,telemega,easymega,easytimer[]
 		For
-		TeleMetrum, TeleMega and EasyMega, which have accelerometers, the mode is
+		TeleMetrum, TeleMega, EasyMega and EasyTimer, which have accelerometers, the mode is
 		controlled by the orientation of the
 		rocket (well, actually the board, of course...) at the time
 		power is switched on.  If the rocket is “nose up”, then
@@ -17,7 +17,7 @@
 		launch, so the firmware chooses flight mode.  However, if the
 		rocket is more or less horizontal, the firmware instead enters
 		idle mode.
-		endif::telemetrum,telemega,easymega[]
+		endif::telemetrum,telemega,easymega,easytimer[]
 		Since
 		EasyMini doesn't
 		have an
@@ -295,7 +295,7 @@
 	endif::radio[]
 
 	ifdef::gps+radio[]
-	:aprsdevices: TeleMetrum v2.0 and TeleMega
+	:aprsdevices: TeleMetrum v2 and newer and TeleMega
 	:configure_section: _configure_altimeter
 	include::aprs-operation.adoc[]
 	endif::gps+radio[]