CVS: g2/DOCS README,1.1.1.1,1.2

Update of /cvsroot/mplayer/g2/DOCS
In directory mail:/var2/tmp/cvs-serv27225

Modified Files:
	README 
Log Message:
grammar/spelling/wording


Index: README
===================================================================
RCS file: /cvsroot/mplayer/g2/DOCS/README,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -r1.1.1.1 -r1.2
--- README	31 Jan 2004 20:16:18 -0000	1.1.1.1
+++ README	31 Jan 2004 20:53:34 -0000	1.2
@@ -8,28 +8,26 @@
 It is designed to be reentrant, so adding thread-safety is easy (just a few
 locks around the demuxer layer entry calls).
 
-NOTE: It's in early stage of development, don't compare to the 0.90 feature set.
-The goal is not (yet) to create an all-in-one player, but a clean framework
-for experimenting with new ideas and solutions for already known problems.
+NOTE: It's in an early stage of development, don't compare it to the 0.90
+feature set. The goal is not (yet) to create a complete player, but a clean
+framework for experimenting with new ideas and solutions for known problems.
 
 A long-term goal is creating a media processing library, to be usable as the
 backend of media/movie players, converters, editors, capture tools.
 
 Some of the major differences to 0.90:
-- video codecs pull the data from the demuxer, instead of the old push-method.
-- video filtering path is driven from the other end: vo, so filters can
+- Video codecs pull the data from the demuxer, instead of the old push-method.
+- The video filtering path is driven from the other end: vo, so filters can
   insert new frames without going up to the codecs.
-- video codecs and filters may modify the timing info (PTS/duration) of frames
+- Video codecs and filters may modify the timing info (PTS/duration) of frames.
 - libvo2 has been redesigned, now vo drivers do the minimal thing only:
-  controls the actual device and export its buffers to the vo core (vf_vo2.c)
+  control the actual device and export its buffers to the vo core (vf_vo2.c)
   All the rest (like draw_slice() implementation, OSD rendering, buffer
-  management is handled by the core, not the driver itself).
-- audio and video codecs/filters/path has been separated
-- the stream and demuxer code have been modularized, instead of switch-case mess
-- demuxers now handle more than one audio and video stream at the same time,
+  management) is handled by the core, not the driver itself.
+- Audio and video codecs/filters/path have been separated.
+- Stream and demuxer code has been modularized, instead of switch-case mess.
+- Demuxers now handle more than one audio and video stream at the same time,
   so runtime stream switching or playback/conversion of multiple audio/video
   tracks at the same time is now possible.
-- stream-less demuxers are not hacks any longer, they are legal using the DUMMY
+- Stream-less demuxers are not hacks any longer, they are legal using the DUMMY
   stream type, auto-created based on URL.
-  
-