design: Fix typos in docs

markdown/additional/design/activation.md

@@ -43,7 +43,7 @@ mode). `activate_mode(PULL)` is then responsible for starting the task
 that pulls from fakesrc:src. Clearly, fakesrc needs to be notified that
 fakesrc is about to pull on its src pad, even though the pipeline has
 not yet changed fakesrc’s state. For this reason, GStreamer will first
-call call `activate_mode(PULL)` on fakesink:sink’s peer before calling
+call `activate_mode(PULL)` on fakesink:sink’s peer before calling
 `activate_mode(PULL)` on fakesink:sinks.
 
 In short, upstream elements operating in PULL mode must be ready to

markdown/additional/design/audiosinks.md

@@ -96,7 +96,7 @@ operation will eventually block when the ringbuffer is filled.
 When no samples arrive in time, the ringbuffer will play silence. Each
 buffer that arrives will be placed into the ringbuffer at the correct
 times. This means that dropping samples or inserting silence is done
-automatically and very accurate and independend of the play pointer.
+automatically and very accurate and independent of the play pointer.
 
 In this mode, the ringbuffer is usually kept as full as possible. When
 using a small buffer (small segsize and segtotal), the latency for audio

markdown/additional/design/gstobject.md

@@ -63,7 +63,7 @@ This policy allows for parents to iterate their children and setting
 properties on them.
 
 Whenever a nested lock needs to be taken on objects not involved in a
-parent-child relation (eg. pads), an explictic locking order has to be
+parent-child relation (eg. pads), an explicit locking order has to be
 defined.
 
 ## Path Generation

markdown/additional/design/preroll.md

@@ -24,16 +24,16 @@ When going to `PAUSED` and `PLAYING` a buffer should be queued in the pad.
 We also make this a requirement for going to `PLAYING` since a flush event
 in the `PAUSED` state could unqueue the buffer again.
 
-The state is commited in the following conditions:
+The state is committed in the following conditions:
 
 - a buffer is received on a sinkpad;
-- an GAP event is received on a sinkpad;
+- a GAP event is received on a sinkpad;
 - an EOS event is received on a sinkpad.
 
-We require the state change to be commited in EOS as well, since an EOS
+We require the state change to be committed in EOS as well, since an EOS
 , by definition, means no buffer is going to arrive anymore.
 
-After the state is commited, a blocking wait should be performed for the
+After the state is committed, a blocking wait should be performed for the
 next event. Some sinks might render the preroll buffer before starting
 this blocking wait.