README.txt in tracksperanto-1.8.1 vs README.txt in tracksperanto-1.8.2

@@ -67,11 +67,11 @@
 * Shake tracker node export (textfile with many tracks per file)
 * PFTrack 2dt files (version 4 and 5)
 * Syntheyes 2D tracking data exports
 * 3DE point exports (as output by the default script) - versions 3 and 4
 * MatchMover Pro .rz2
-* MayaLive track export (square pixel aspect only)
+* MayaLive track export (square pixel aspect only, you will need to write some extra code to convert that)
 * Flame .stabilizer file
 
 Import only:
 * Boujou feature track export
 * Shake script (Tracker, Matchmove and Stabilize nodes)
@@ -95,9 +95,14 @@
 are themselves arrays of Tracksperanto::Keyframe objects.
 
 == Exporting your own formats
 
 You can easily write an exporter. Refer to the Tracksperanto::Export::Base docs.
+
+== Ading your own processing steps
+
+You probably want to write a Middleware (consult the Tracksperanto::Middleware::Base docs). A Middleware is just like
+an exporter, except that it wraps another exporter instead (so you can intercept export calls and massage the data as it is moving through).
 
 == Limitations
 
 Information about the search area, reference area and offset is not passed along (outside
 of scope for the app and different trackers handle these differently, if at all). For some