From 48c38ef7475637460b9ec104aa95c1109c4303c7 Mon Sep 17 00:00:00 2001
From: "sumit shinde ( Roni )"
 <110285294+sumitshinde-84@users.noreply.github.com>
Date: Thu, 16 May 2024 21:33:49 +0530
Subject: [PATCH] Update how-to-setup-node-red-on-raspberry-pi.md

---
 src/blog/2024/05/how-to-setup-node-red-on-raspberry-pi.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/blog/2024/05/how-to-setup-node-red-on-raspberry-pi.md b/src/blog/2024/05/how-to-setup-node-red-on-raspberry-pi.md
index a8b2e57a55..3953e960e0 100644
--- a/src/blog/2024/05/how-to-setup-node-red-on-raspberry-pi.md
+++ b/src/blog/2024/05/how-to-setup-node-red-on-raspberry-pi.md
@@ -102,7 +102,7 @@ When using the Node-RED along with FlowFuse , there's no need to add security me
 
 Furthermore, accessing the audit log allows you to monitor changes made by team members to instances of your team, ensuring transparency and accountability. Additionally, FlowFuse empowers team owners to control the access of team members, enhancing security and privacy during collaboration.
 
-For more information on the audit log, refer to [Audit log](https://flowfuse.com/docs/user/logs/#audit-log).
+For more information on the audit log, refer to [Audit log](/docs/user/logs/#audit-log).
 
 For enhanced security and granular control over team access, refer to [Role-Based Access for your Node-RED applications](/blog/2024/04/role-based-access-control-rbac-for-node-red-with-flowfuse/).