Readme docs spelling mistakes

README.md

@@ -149,7 +149,7 @@ The diagram above shows three of the Media Objects used by Flow Z and a smaller
 The `object_timerange` approach can be applied to ffmpeg by first calculating `skip = timerange.start - (object_timerange.start + ts_offset)`.
 
 - `-ss` should be set to the `skip` time in seconds.
-- `-t` should be set to the duration in seconds, derrived from the Segment timerange
+- `-t` should be set to the duration in seconds, derived from the Segment timerange
 - `-output_ts_offset` should be set to the start time of the Segment in seconds, to re-map the timestamps embedded in the output segment onto the Flow timeline
 
 Note however that for this to be frame-accurate in codecs using temporal re-ordering, the input must be transcoded.

docs/appnotes/README.md

@@ -5,7 +5,7 @@ These documents provide ancillary information about the concepts in the TAMS API
 No part of these documents are considered part of the API specification, although including specification-type language as examples, or "opt-in" extensions is allowed.
 
 There is a simple template [appnote-template.md](../templates/appnote-template.md) which describes the few restrictions there are on Application Notes.
-Select a unique number for your Applcation Note, and try to keep them at least somewhat close together.
+Select a unique number for your Application Note, and try to keep them at least somewhat close together.
 
 ## Versioning
 
@@ -17,6 +17,6 @@ For those unfamiliar with git, if you want to check if the versions you are look
 git diff <commit> <commit> -- <filename>
 ```
 
-will indicate if there are differences between the verions or not.
+will indicate if there are differences between the versions or not.
 
 If this versioning scheme presents you with problems, please raise an issue so we can investigate if another scheme would be more suitable.