X-Git-Url: http://research.m1stereo.tv/gitweb?a=blobdiff_plain;f=docs%2Finigo.txt;h=d62031f4534516c8fbf912aa026533afeaf21ab5;hb=42bd0aedb6d3d65bedb98479adcdbaeb326dfee9;hp=9fa53e10f659dde9443bfd237479c63c4258176f;hpb=812170855207691a0ce6fa152cb3d917221eb66f;p=melted

diff --git a/docs/inigo.txt b/docs/inigo.txt
index 9fa53e1..d62031f 100644
--- a/docs/inigo.txt
+++ b/docs/inigo.txt
@@ -33,13 +33,15 @@ General rules:
 	available;
 
 	4. The MLT framework, from which inigo has inherited its 
-	naming convention - is very ego-centric. Producers produce 
+	naming convention, is very mlt-centric. Producers produce 
 	MLT frame objects and consumers consume MLT frame objects. 
 	The distinction is important - a DV producer does not produce 
-	DV and a DV consumer does not consume DV.
+	DV, it produces MLT frames from a DV source, and similarly a 
+	DV consumer does not consume DV, it consumes MLT frames and 
+	produces DV frames.
 
 
-Terminoligy:
+Terminology:
 
 	'Producers' typically refer to files but may also indicate
 	devices (such as dv1394 input or video4linux). Hence, the more
@@ -173,7 +175,7 @@ Introducing Tracks and Blanks:
 	It is best to visualise a track arrangement, so we'll start with
 	an example:
 	
-	$ inigo a.dv out=49 -track b.dv
+	$ inigo a.dv in=0 out=49 -track b.dv
 	
 	This can be visualised as follows: