summaryrefslogtreecommitdiff
path: root/doc/developer.texi
diff options
context:
space:
mode:
authorLou Logan <lou@lrcd.com>2015-01-07 17:16:54 -0900
committerLou Logan <lou@lrcd.com>2015-01-07 17:17:33 -0900
commit919e038a95fdebefb0ec76a602c0d61758ad0d8d (patch)
tree55e33c767135b1170325bc4a01c4dd91c85f56ae /doc/developer.texi
parentbcaa9099b3648b47060e1724a97dc98b63c83702 (diff)
doc: fix typos
Signed-off-by: Lou Logan <lou@lrcd.com>
Diffstat (limited to 'doc/developer.texi')
-rw-r--r--doc/developer.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/developer.texi b/doc/developer.texi
index 8b1f150ee6..f1351a5db2 100644
--- a/doc/developer.texi
+++ b/doc/developer.texi
@@ -647,12 +647,12 @@ accordingly].
@subsection Adding files to the fate-suite dataset
When there is no muxer or encoder available to generate test media for a
-specific test then the media has to be inlcuded in the fate-suite.
+specific test then the media has to be included in the fate-suite.
First please make sure that the sample file is as small as possible to test the
respective decoder or demuxer sufficiently. Large files increase network
bandwidth and disk space requirements.
Once you have a working fate test and fate sample, provide in the commit
-message or introductionary message for the patch series that you post to
+message or introductory message for the patch series that you post to
the ffmpeg-devel mailing list, a direct link to download the sample media.