From b09fbc38a3e3b9b108acfad7237976730004599d Mon Sep 17 00:00:00 2001 From: Mitja Felicijan Date: Fri, 1 Mar 2024 13:28:56 +0100 Subject: Typo fix --- _posts/posts/2024-02-28-converting-valgrind-callgrinds-to-svg-format.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/posts/2024-02-28-converting-valgrind-callgrinds-to-svg-format.md b/_posts/posts/2024-02-28-converting-valgrind-callgrinds-to-svg-format.md index ecd69e1..0475066 100644 --- a/_posts/posts/2024-02-28-converting-valgrind-callgrinds-to-svg-format.md +++ b/_posts/posts/2024-02-28-converting-valgrind-callgrinds-to-svg-format.md @@ -94,7 +94,7 @@ cat out.zig.dot | dot -Tsvg > out.zig.svg ![SVG callgrind for Zig program](/assets/posts/valgrind-callgrind-svg/out.zig.svg) Now, to be fair -[Kcachegrind](https://kcachegrind.github.io/html/Home.html) is much nices +[Kcachegrind](https://kcachegrind.github.io/html/Home.html) is much nicer for local exploration and digging deep into the callgraphs, but the SVG format can still provide valid information for documentation and things of that nature. -- cgit v1.2.3