summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJinwoo Ahn <creator.ahn@gmail.com>2017-11-11 11:18:26 +0900
committerTim-Philipp Müller <tim@centricular.com>2017-11-11 11:02:23 +0000
commit7665679eb6f637c54e9474ed140385b4f96ad695 (patch)
treef9014965ab1c5d85d279385dabd0cab0afb8b28e
parentadc2740ad4df6f95cbb0696f8eb4227af3a5e2e6 (diff)
tutorials: time-management: fix typo
https://bugzilla.gnome.org/show_bug.cgi?id=790196
-rw-r--r--markdown/tutorials/basic/time-management.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/markdown/tutorials/basic/time-management.md b/markdown/tutorials/basic/time-management.md
index b6d7596..aca6316 100644
--- a/markdown/tutorials/basic/time-management.md
+++ b/markdown/tutorials/basic/time-management.md
@@ -252,7 +252,7 @@ in nanoseconds. Numbers expressing different time units then, should be
multiplied by macros like `GST_SECOND` or `GST_MSECOND`. This also makes
your code more readable.
-If we got a message, we process it in the `handle_message`` `function
+If we got a message, we process it in the `handle_message` function
(next subsection), otherwise:
### User interface refreshing
@@ -268,7 +268,7 @@ most queries would fail.
We get here approximately 10 times per second, a good enough refresh
rate for our UI. We are going to print on screen the current media
-position, which we can learn be querying the pipeline. This involves a
+position, which we can learn by querying the pipeline. This involves a
few steps that will be shown in the next subsection, but, since position
and duration are common enough queries, `GstElement` offers easier,
ready-made alternatives: