[pango/gi-docs] Add some more links

[Matthias Clasen <matthiasc src gnome org>]

commit fdbc5bb901acb09c98e9fafebbe61ef74bc4be57
Author: Matthias Clasen <mclasen redhat com>
Date:   Fri Feb 12 21:01:37 2021 -0500

    Add some more links

 docs/pango_bidi.md | 56 +++++++++++++++++++++++++++---------------------------
 1 file changed, 28 insertions(+), 28 deletions(-)
---
diff --git a/docs/pango_bidi.md b/docs/pango_bidi.md
index b8e76183..876f2054 100644
--- a/docs/pango_bidi.md
+++ b/docs/pango_bidi.md
@@ -7,12 +7,12 @@ Title: Bidirectional and Vertical Text
 Pango supports bidirectional text (like Arabic and Hebrew) automatically.
 Some applications however, need some help to correctly handle bidirectional text.
 
-The [enum@Pango.Direction] type can be used with pango_context_set_base_dir() to
-instruct Pango about direction of text, though in most cases Pango detects
+The [enum@Pango.Direction] type can be used with [method@Pango.Context.set_base_dir]
+to instruct Pango about direction of text, though in most cases Pango detects
 that correctly and automatically. For application that need more direct
 control over bidirectional setting of text, Pango provides APIs such as
-pango_unichar_direction(), pango_find_base_dir(), pango_get_mirror_char()
-or pango_bidi_type_for_unichar().
+[func@unichar_direction], [func@find_base_dir], [func@get_mirror_char]
+or [func@bidi_type_for_unichar].
 
 # Vertical Text
 
@@ -23,36 +23,36 @@ vertical text parameters.
 The way this is implemented is through the concept of *gravity*. Gravity of
 normal Latin text is south. A gravity value of east means that glyphs will be
 rotated ninety degrees counterclockwise. So, to render vertical text one needs
-to set the gravity and rotate the layout using the matrix machinery already in
-place. This has the huge advantage that most algorithms working on a `PangoLayout`
-do not need any change as the assumption that lines run in the X direction and
-stack in the Y direction holds even for vertical text layouts.
-
-Applications should only need to set base gravity on `PangoContext` in use, and
-let Pango decide the gravity assigned to each run of text. This automatically
+to set the gravity and rotate the layout using the matrix machinery already
+in place. This has the huge advantage that most algorithms working on a
+[class@Pango.Layout] do not need any change as the assumption that lines run
+in the X direction and stack in the Y direction holds even for vertical text
+layouts.
+
+Applications should only need to set base gravity on [class@Pango.Context] in use,
+and let Pango decide the gravity assigned to each run of text. This automatically
 handles text with mixed scripts. A very common use is to set the context base
-gravity to auto using pango_context_set_base_gravity() and rotate the layout
+gravity to auto using [method@Pango.Context.set_base_gravity] and rotate the layout
 normally. Pango will make sure that Asian languages take the right form, while
 other scripts are rotated normally.
 
 The correct way to set gravity on a layout is to set it on the context associated
-with it using pango_context_set_base_gravity(). The context of a layout can be
-accessed using pango_layout_get_context(). The currently set base gravity of the
-context can be accessed using pango_context_get_base_gravity() and the *resolved*
-gravity of it using pango_context_get_gravity(). The resolved gravity is the same
-as the base gravity for the most part, except that if the base gravity is set to
-`PANGO_GRAVITY_AUTO`, the resolved gravity will depend on the current matrix
-set on context, and is derived using pango_gravity_get_for_matrix().
-
-The next thing an application may want to set on the context is the
-*gravity hint*. A `PangoGravityHint` instructs how different scripts should
-react to the set base gravity.
+with it using [method@Pango.Context.set_base_gravity]. The context of a layout can
+be accessed using [method@Pango.Layout.get_context]. The currently set base gravity
+of the context can be accessed using [method@Pango.Context.get_base_gravity] and the
+*resolved* gravity of it using [method@Pango.Context.get_gravity]. The resolved
+gravity is the same as the base gravity for the most part, except that if the base
+gravity is set to `PANGO_GRAVITY_AUTO`, the resolved gravity will depend on the
+current matrix set on context, and is derived using [func@gravity_get_for_matrix].
+
+The next thing an application may want to set on the context is the *gravity hint*.
+A [enum@Pango.GravityHint] instructs how different scripts should react to the set
+base gravity.
 
 Font descriptions have a gravity property too, that can be set using
-pango_font_description_set_gravity() and accessed using
-pango_font_description_get_gravity(). However, those are rarely useful
+[func@font_description_set_gravity] and accessed using
+[func@font_description_get_gravity]. However, those are rarely useful
 from application code and are mainly used by `PangoLayout` internally.
 
-Last but not least, one can create `PangoAttributes` for gravity
-and gravity hint using pango_attr_gravity_new() and
-pango_attr_gravity_hint_new().
+Last but not least, one can create `PangoAttributes` for gravity and gravity
+hint using [func@attr_gravity_new] and [func@attr_gravity_hint_new].