From 8661d52c53282c73919e6efd372ebff3b8fac1f0 Mon Sep 17 00:00:00 2001 From: "Reynaldo H. Verdejo Pinochet" Date: Mon, 23 Jan 2017 13:53:19 -0800 Subject: [PATCH] design: scheduling: rework some paragraphs for clarity/grammar Make () disposition congruent, avoid redundancy and other similar fixes. --- markdown/design/scheduling.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/markdown/design/scheduling.md b/markdown/design/scheduling.md index 47996122ba..ac50fb2492 100644 --- a/markdown/design/scheduling.md +++ b/markdown/design/scheduling.md @@ -1,13 +1,13 @@ # Scheduling The scheduling in GStreamer is based on pads actively pushing -(producing) data or pad pulling in data (consuming) from other pads. +(producing) data or pulling (consuming) data from other pads. ## Pushing A pad can produce data and push it to the next pad. A pad that behaves -this way exposes a loop function that will be called repeatedly until it -returns false. The loop function is allowed to block whenever it wants. +this way exposes a loop function that will be repeatedly called until it +returns false. This loop function is allowed to block whenever it wants. When the pad is deactivated the loop function should unblock though. A pad operating in the push mode can only produce data to a pad that