diff --git a/valkey.conf b/valkey.conf
index d3073bc21..b1d180893 100644
--- a/valkey.conf
+++ b/valkey.conf
@@ -825,7 +825,7 @@ replica-priority 100
 # this is used in order to send invalidation messages to clients. Please
 # check this page to understand more about the feature:
 #
-#   https://redis.io/topics/client-side-caching
+#   https://valkey.io/topics/client-side-caching
 #
 # When tracking is enabled for a client, all the read only queries are assumed
 # to be cached: this will force the server to store information in the invalidation
@@ -1003,7 +1003,7 @@ replica-priority 100
 # * stream - Data type: streams related.
 #
 # For more information about ACL configuration please refer to
-# the Valkey web site at https://redis.io/topics/acl
+# the Valkey web site at https://valkey.io/topics/acl
 
 # ACL LOG
 #
@@ -1377,7 +1377,7 @@ disable-thp yes
 # restarting the server can lead to data loss. A conversion needs to be done
 # by setting it via CONFIG command on a live server first.
 #
-# Please check https://redis.io/topics/persistence for more information.
+# Please check https://valkey.io/topics/persistence for more information.
 
 appendonly no
 
@@ -1761,7 +1761,7 @@ aof-timestamp-enabled no
 # cluster-preferred-endpoint-type ip
 
 # In order to setup your cluster make sure to read the documentation
-# available at https://redis.io web site.
+# available at https://valkey.io web site.
 
 ########################## CLUSTER DOCKER/NAT support  ########################
 
@@ -1864,7 +1864,7 @@ latency-monitor-threshold 0
 ############################# EVENT NOTIFICATION ##############################
 
 # The server can notify Pub/Sub clients about events happening in the key space.
-# This feature is documented at https://redis.io/topics/notifications
+# This feature is documented at https://valkey.io/topics/notifications
 #
 # For instance if keyspace events notification is enabled, and a client
 # performs a DEL operation on key "foo" stored in the Database 0, two