summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/design/part-events.txt2
-rw-r--r--docs/design/part-overview.txt4
2 files changed, 3 insertions, 3 deletions
diff --git a/docs/design/part-events.txt b/docs/design/part-events.txt
index ad2672dc95..0b5d2c0887 100644
--- a/docs/design/part-events.txt
+++ b/docs/design/part-events.txt
@@ -217,7 +217,7 @@ The general flow of executing the seek with FLUSH is as follows:
4) send a FLUSH_STOP event to all peer elements to allow streaming again.
5) create a NEWSEGMENT event to signal the new buffer timestamp base time.
- This event must be queued to be send by the streaming thread.
+ This event must be queued to be sent by the streaming thread.
6) start stopped tasks and unlock the STREAM_LOCK, dataflow will continue
now from the new position.
diff --git a/docs/design/part-overview.txt b/docs/design/part-overview.txt
index 0a3cf47db8..36c2269f2a 100644
--- a/docs/design/part-overview.txt
+++ b/docs/design/part-overview.txt
@@ -216,8 +216,8 @@ Dataflow and buffers
automatically and will call the gst_pad_set_caps() function of the element before
sending the buffer to the element.
- Both gst_pad_push() and gst_pad_pull_range() have a return value indicating wether
- the operation succeeded. An error code means that no more data should be send
+ Both gst_pad_push() and gst_pad_pull_range() have a return value indicating whether
+ the operation succeeded. An error code means that no more data should be sent
to that pad. A source element that initiates the data flow in a thread typically
pauses the producing thread when this happens.