Fix doc links

source/developer-guides/bindings/writing-a-vapi-manually/05-00-fundamentals-of-binding-a-c-function/05-01-out-and-reference-parameters-and-return-values.rst

@@ -72,5 +72,5 @@ To return a struct directly, the question mark operator will box it, and make it
    foo *get_foo(int x);
    int make_foo(int y, foo **f);
 
-The ownership rules in :doc:``05-02-ownership`` apply.
+The ownership rules in :doc:`05-02-ownership` apply.
 

source/developer-guides/bindings/writing-a-vapi-manually/05-00-fundamentals-of-binding-a-c-function/05-02-ownership.rst

@@ -10,4 +10,4 @@ It is often the case that a function will return one of its input values, partic
 
 Often C programmers will mark return values as const when they are unowned.
 
-See also: :doc:`10-00-awkward-situations/10-02-dependently-typed-ownership`.
+See also: :doc:`../10-00-awkward-situations/10-02-dependently-typed-ownership`.

source/tutorials/programming-language/main/07-00-tools/07-01-valac.rst

@@ -8,7 +8,7 @@ Vala has better information than the C compiler, so it knows certain things are
 
 Unfortunately we can't just add casts everywhere since there are situations where we can't generate a valid cast (and, what's more, no way to know what those situations are).
 
-For example, compiling the :doc:`Hello World program </../01-00-first-program>` will give us some warnings because ``valac`` by default generates code which is compatible with older versions of the ``GLib``.Some methods may have been deprecated in your new version of GLib so that C language compiler will warn you.
+For example, compiling the :doc:`Hello World program <../01-00-first-program>` will give us some warnings because ``valac`` by default generates code which is compatible with older versions of the ``GLib``.Some methods may have been deprecated in your new version of GLib so that C language compiler will warn you.
 
 Imagine a machine with older glib version want to run your vala program!