diff --git a/sdk-android-tutorial-media-player.md b/sdk-android-tutorial-media-player.md
index dbe3736a70..1bf8d9feda 100644
--- a/sdk-android-tutorial-media-player.md
+++ b/sdk-android-tutorial-media-player.md
@@ -1192,11 +1192,10 @@ static gboolean refresh_ui (CustomData *data) {
 }
 ```
 
-If it is unknown, the clip duration is retrieved, as explained in [Basic
-tutorial 4: Time
-management](Basic%2Btutorial%2B4%253A%2BTime%2Bmanagement.html). The
-current position is retrieved next, and the UI is informed of both
-through its `setCurrentPosition()` callback.
+If it is unknown, the clip duration is retrieved, as explained in
+[](sdk-basic-tutorial-time-management.md). The current position is
+retrieved next, and the UI is informed of both through its
+`setCurrentPosition()` callback.
 
 Bear in mind that all time-related measures returned by GStreamer are in
 nanoseconds, whereas, for simplicity, we decided to make the UI code
diff --git a/sdk-basic-tutorial-platform-specific-elements.md b/sdk-basic-tutorial-platform-specific-elements.md
index 9d61ba0cef..ea2258bebb 100644
--- a/sdk-basic-tutorial-platform-specific-elements.md
+++ b/sdk-basic-tutorial-platform-specific-elements.md
@@ -117,8 +117,7 @@ that their pipelines cannot be interconnected. However, through this
 element, GStreamer can benefit from the decoding elements present in
 Direct Show. `dshowdecwrapper` wraps multiple Direct Show decoders so
 they can be embedded in a GStreamer pipeline. Use the `gst-inspect-1.0` tool
-(see [Basic tutorial 10: GStreamer
-tools](Basic%2Btutorial%2B10%253A%2BGStreamer%2Btools.html)) to see the
+(see [](sdk-basic-tutorial-gstreamer-tools.md)) to see the
 available decoders.
 
 ## Android