validate: fix some recurring typos

diff --git a/validate/gst/validate/gst-validate-scenario.c b/validate/gst/validate/gst-validate-scenario.c
index 2dade89a1e8ea8d1b0e0487689bfef9b473245ab..c0d8390d3bbc79029d0e3f5571d5b5e3e7a62d9f 100644 (file)
--- a/validate/gst/validate/gst-validate-scenario.c
+++ b/validate/gst/validate/gst-validate-scenario.c
@@ -96,7 +96,7 @@ static GstValidateActionType *_find_action_type (const gchar * type_name);
 
 /* GstValidateScenario is not really thread safe and
  * everything should be done from the thread GstValidate
- * was inited from, unless stated otherwize.
+ * was inited from, unless stated otherwise.
  */
 struct _GstValidateScenarioPrivate
 {
@@ -449,7 +449,7 @@ _check_scenario_is_done (GstValidateScenario * scenario)
  * the 'position' and 'duration' variables. And it will always convert that
  * value to a GstClockTime.
  *
- * Returns: %TRUE if the time value could be retrieved/computed or %FALSE otherwize
+ * Returns: %TRUE if the time value could be retrieved/computed or %FALSE otherwise
  */
 gboolean
 gst_validate_action_get_clocktime (GstValidateScenario * scenario,
@@ -504,7 +504,7 @@ gst_validate_action_get_clocktime (GstValidateScenario * scenario,
  *
  * For more information you should have a look at #gst_event_new_seek
  *
- * Returns: %TRUE if the seek could be executed, %FALSE otherwize
+ * Returns: %TRUE if the seek could be executed, %FALSE otherwise
  */
 gboolean
 gst_validate_scenario_execute_seek (GstValidateScenario * scenario,
@@ -2937,7 +2937,7 @@ gst_validate_list_scenarios (gchar ** scenarios, gint num_scenarios,
 
 done:
   result = g_key_file_to_data (kf, &datalength, &err);
-  g_print ("All scenarios avalaible:\n%s", result);
+  g_print ("All scenarios available:\n%s", result);
 
   if (output_file && !err)
     g_file_set_contents (output_file, result, datalength, &err);

diff --git a/validate/gst/validate/gst-validate-utils.c b/validate/gst/validate/gst-validate-utils.c
index 2ad48b19f8b6d14e08061c0ad8bf123a955be200..f90231b02acbe79a48e0469c0d99491a94f7843a 100644 (file)
--- a/validate/gst/validate/gst-validate-utils.c
+++ b/validate/gst/validate/gst-validate-utils.c
@@ -699,7 +699,7 @@ done:
  * for the value, if it is a double, it considers the value to be in second
  * it can be a gint, gint64 a guint, a gint64.
  *
- * Return: %TRUE in case of success, %FALSE otherwize.
+ * Return: %TRUE in case of success, %FALSE otherwise.
  */
 gboolean
 gst_validate_utils_get_clocktime (GstStructure * structure, const gchar * name,

diff --git a/validate/launcher/main.py b/validate/launcher/main.py
index 6fcbaa54c3043bb9b182d38c0a85e2b52c9e9f90..be5a38d0f2c8709c2c455cd15f885ba061d1a2c3 100644 (file)
--- a/validate/launcher/main.py
+++ b/validate/launcher/main.py
@@ -74,7 +74,7 @@ you will need that tool to get started.
 ---------------------------
 
 To implement new tests, you will just need to set the media path using the
---medias-paths argument. If you want to run all avalaible scenarios on all the
+--medias-paths argument. If you want to run all available scenarios on all the
 file present in that folder, you should run the first time:
 
 .    $gst-validate-launcher --medias-paths /path/to/media/files --generate-media-info
@@ -240,7 +240,7 @@ class LauncherConfig(Loggable):
             try:
                 subprocess.check_output("gdb --help", shell=True)
             except subprocess.CalledProcessError:
-                printc("Want to use gdb, but not avalaible on the system",
+                printc("Want to use gdb, but not available on the system",
                        Colors.FAIL)
                 return False
 
@@ -303,7 +303,7 @@ class LauncherConfig(Loggable):
             try:
                 subprocess.check_output("valgrind --help", shell=True)
             except subprocess.CalledProcessError:
-                printc("Want to use valgrind, but not avalaible on the system",
+                printc("Want to use valgrind, but not available on the system",
                        Colors.FAIL)
                 return False
 
@@ -355,7 +355,7 @@ if it succeeded loading the tests, False otherwise.
 You will be able to configure the TestManager with its various methods. This
 function will be called with each TestManager usable, for example you will be
 passed the 'validate' TestManager in case the GstValidateManager launcher is
-avalaible. You should configure it using:
+available. You should configure it using:
 
    * test_manager.add_scenarios: which allows you to register a list of scenario names to be run
    * test_manager.set_default_blacklist: Lets you set a list of tuple of the form: