docs: Point to the GObject reference on docs.gtk.org

Do not use the snapshot of the old developer.gnome.org website.

2 files changed, 3 insertions, 5 deletions

diff --git a/docs/website/goals.rst b/docs/website/goals.rst
index 7fb73d6b..ca1fbd1d 100644
--- a/docs/website/goals.rst
+++ b/docs/website/goals.rst
@@ -23,7 +23,7 @@ application logic such as configuration, layout, dialogs, etc.
 
   To achieve this goal you need to write your code using GObject convention.
   For more information about that, see the `GObject tutorial
-  <https://developer-old.gnome.org/gobject/stable/pt02.html>`__
+  <https://docs.gtk.org/gobject/tutorial.html>`__
 
 Thus, one of the major goals of the GObject introspection project is to be a
 convenient bridge between these two worlds, and allow you to choose the right
diff --git a/docs/website/writingbindableapis.rst b/docs/website/writingbindableapis.rst
index b9b08941..45cc6cea 100644
--- a/docs/website/writingbindableapis.rst
+++ b/docs/website/writingbindableapis.rst
@@ -9,13 +9,11 @@ Structures with custom memory management
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Avoid creating C structures with custom memory management unless they are
-registered as a `boxed type
-<https://developer-old.gnome.org/gobject/stable/gobject-Boxed-Types.html>`__.
+registered as a `boxed type <https://docs.gtk.org/gobject/boxed.html>`__.
 If you don't register them as a boxed type bindings will fall back to
 simple memory copying, which might not be what you want.
 
-Also consider using a full `GObject
-<https://developer-old.gnome.org/gobject/stable/gobject-The-Base-Object-Type.html>`__
+Also consider using a full `GObject <https://docs.gtk.org/gobject/class.Object.html>`__
 as that allows bindings to better integrate those objects with the binding
 language, like for example preserve user defined state across language
 boundaries.