From 473f16d290560d1262bd5677b34ddb0c0c2242b8 Mon Sep 17 00:00:00 2001
From: andrut-ds <82076528+andrut-ds@users.noreply.github.com>
Date: Fri, 13 Feb 2026 20:49:52 +0700
Subject: [PATCH] Update Secure Connection link

---
 content/tutorials/connect-remote-gui.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/tutorials/connect-remote-gui.md b/content/tutorials/connect-remote-gui.md
index 32de83d..8a27288 100644
--- a/content/tutorials/connect-remote-gui.md
+++ b/content/tutorials/connect-remote-gui.md
@@ -43,7 +43,7 @@ information you send or receive may be observed by a man-in-the-middle attacker.
 One simple way to secure the gRPC connection is to wrap it over the `https` protocol.
 This is known as [gRPC-Web](https://grpc.io/docs/platforms/web/).
 
-You can follow the [Secure Connections](./secure-connections.md) tutorial to set up your server to
+You can follow the [Secure Connections](/tutorials/secure-connections) tutorial to set up your server to
 wrap the gRPC connection over the `https` protocol. We have explained how to secure the connection there.
 This approach requires a domain name and NGINX installed on your server.