summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJavier Jardón <jjardon@gnome.org>2010-10-03 04:59:23 +0200
committerJavier Jardón <jjardon@gnome.org>2010-10-03 04:59:23 +0200
commitc4705377f4ab9e8ca1c2f8c9d70bffa0678cf88a (patch)
tree18ce4547e3ce437e4df8c82569bc3fc79e3d8440
parent2a9d299aa3419396d4c5bdcb61b746fd7b652183 (diff)
downloadgtk+-c4705377f4ab9e8ca1c2f8c9d70bffa0678cf88a.tar.gz
docs: Latest 2.x release will be 2.24, not 2.22
-rw-r--r--docs/reference/gtk/migrating-2to3.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/reference/gtk/migrating-2to3.xml b/docs/reference/gtk/migrating-2to3.xml
index 447dc17c1d..81fa827bc1 100644
--- a/docs/reference/gtk/migrating-2to3.xml
+++ b/docs/reference/gtk/migrating-2to3.xml
@@ -20,11 +20,11 @@
<para>
The steps outlined in the following sections assume that your
- application is working with GTK+ 2.22, which is the final stable
+ application is working with GTK+ 2.24, which is the final stable
release of GTK+ 2.x. It includes all the necessary APIs and tools
to help you port your application to GTK+ 3. If you are still using
an older version of GTK+ 2.x, you should first get your application
- to build and work with 2.22.
+ to build and work with 2.24.
</para>
<section>
@@ -339,7 +339,7 @@ cairo_destroy (cr);
<para>
This section outlines porting tasks that you need to tackle when
you get to the point that you actually build your application against
- GTK+ 3. Making it possible to prepare for these in GTK+ 2.22 would
+ GTK+ 3. Making it possible to prepare for these in GTK+ 2.24 would
have been either impossible or impractical.
</para>