From 47d96381a2f52587f8706ffa115b2379d6ca731e Mon Sep 17 00:00:00 2001 From: "Jason L. Quinn" Date: Thu, 11 Apr 2013 23:43:17 -0400 Subject: [PATCH] spelling fixes of 'runtine' and 'adresses' in cross.xml and running.xml, respectively https://bugzilla.gnome.org/show_bug.cgi?id=697849 --- docs/reference/glib/cross.xml | 2 +- docs/reference/glib/running.xml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/glib/cross.xml b/docs/reference/glib/cross.xml index 2b1661888..35d169b7a 100644 --- a/docs/reference/glib/cross.xml +++ b/docs/reference/glib/cross.xml @@ -40,7 +40,7 @@ How to cross-compile GLib As an example of using a cache file, to cross compile for - the "MingW32" Win32 runtine environment on a Linux system, + the "MingW32" Win32 runtime environment on a Linux system, create a file 'win32.cache' with the following contents: diff --git a/docs/reference/glib/running.xml b/docs/reference/glib/running.xml index bef37b3da..67699d95b 100644 --- a/docs/reference/glib/running.xml +++ b/docs/reference/glib/running.xml @@ -184,7 +184,7 @@ How to run and debug your GLib application debug-blocks Using this option (present since GLib 2.13) engages extra code which performs sanity checks on the released memory - slices. Invalid slice adresses or slice sizes will be reported and + slices. Invalid slice addresses or slice sizes will be reported and lead to a program halt. This option is for debugging scenarios. In particular, client packages sporting their own test suite should always enable this option when running tests.