From: Reynaldo H. Verdejo Pinochet <reynaldo@osg.samsung.com>
Date: Tue, 28 Mar 2017 19:51:12 +0000 (-0700)
Subject: validate: scenario: fix type field in description parameter
X-Git-Tag: 1.19.3~491^2~744
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=fd796d29761c420c740dd3ed34aa4835d77f630d;p=platform%2Fupstream%2Fgstreamer.git

validate: scenario: fix type field in description parameter

Nothing wrong with Sting though :)

Additionally: Fix typo in need-clock-sync's description
---

diff --git a/validate/gst/validate/gst-validate-scenario.c b/validate/gst/validate/gst-validate-scenario.c
index 71c70df..84686fe 100644
--- a/validate/gst/validate/gst-validate-scenario.c
+++ b/validate/gst/validate/gst-validate-scenario.c
@@ -3699,7 +3699,7 @@ init_scenarios (void)
         .name = "summary",
         .description = "Whether the scenario is a config only scenario (ie. explain what it does)",
         .mandatory = FALSE,
-        .types = "sting",
+        .types = "string",
         .possible_variables = NULL,
         .def = "'Nothing'"},
       {
@@ -3737,7 +3737,7 @@ init_scenarios (void)
       },
       {
         .name = "need-clock-sync",
-        .description = "Whether the scenario needs the execution to be syncronized with the pipeline\n"
+        .description = "Whether the scenario needs the execution to be synchronized with the pipeline's\n"
                        "clock. Letting the user know if it can be used with a 'fakesink sync=false' sink",
         .mandatory = FALSE,
         .types = "boolean",