summaryrefslogtreecommitdiffstats
path: root/DOCS
diff options
context:
space:
mode:
authordiego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2>2008-12-25 18:28:10 +0000
committerdiego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2>2008-12-25 18:28:10 +0000
commit2e6e799109005d1863005d0f74bd26e0352e1eb2 (patch)
treecc8222bd616f0fa9c154d34b4b69d7a4f811abe5 /DOCS
parent7f1d183b1c13823b45f01e45f7eeec0860736415 (diff)
downloadmpv-2e6e799109005d1863005d0f74bd26e0352e1eb2.tar.bz2
mpv-2e6e799109005d1863005d0f74bd26e0352e1eb2.tar.xz
grammar fix by Vineeth N, nvineeth gmail com
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@28193 b3059339-0415-0410-9bf9-f77b7e298cf2
Diffstat (limited to 'DOCS')
-rw-r--r--DOCS/tech/codec-devel.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/DOCS/tech/codec-devel.txt b/DOCS/tech/codec-devel.txt
index a9ca1ddcad..1b2c26918c 100644
--- a/DOCS/tech/codec-devel.txt
+++ b/DOCS/tech/codec-devel.txt
@@ -143,7 +143,7 @@ with the parameters passed into the decoding function (if you set it up to
take those parameters). Such data should match up. If it doesn't, issue a
warning and make an executive decision in the code about which data to
believe (personally, I always lend more weight to the data that was passed
-into the decoder function, the data that comes from the container file's
+into the decoder function, than the data that comes from the container file's
header). If there's supposed to be a magic number embedded in, or computed
from, the chunk's header, issue a warning if it isn't correct.