From d12392d0842c074bf4d869505214214270bc3254 Mon Sep 17 00:00:00 2001
From: Tien Dao <15717476+tiendn@users.noreply.github.com>
Date: Mon, 23 Dec 2024 13:10:17 +0700
Subject: [PATCH] docs: update https external link (#13508)

---
 book/developers/profiling.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/book/developers/profiling.md b/book/developers/profiling.md
index 956bc5633..fdae94e2d 100644
--- a/book/developers/profiling.md
+++ b/book/developers/profiling.md
@@ -126,6 +126,6 @@ If reth is not built properly, you will see this when you try to run reth:
 If this happens, jemalloc likely needs to be rebuilt with the `jemalloc-prof` feature enabled.
 
 If everything is working, this will output `jeprof.*.heap` files while reth is running.
-[The jemalloc website](http://jemalloc.net/jemalloc.3.html#opt.abort) has a helpful overview of the options available, for example `lg_prof_interval`, `lg_prof_sample`, `prof_leak`, and `prof_final`.
+[The jemalloc website](https://jemalloc.net/jemalloc.3.html#opt.abort) has a helpful overview of the options available, for example `lg_prof_interval`, `lg_prof_sample`, `prof_leak`, and `prof_final`.
 
 Now that we have the heap snapshots, we can analyze them using `jeprof`. An example of jeprof usage and output can be seen on the jemalloc github repository: https://github.com/jemalloc/jemalloc/wiki/Use-Case:-Leak-Checking