diff --git a/community_extensions/faq.md b/community_extensions/faq.md
index fddb548896..23691981e8 100644
--- a/community_extensions/faq.md
+++ b/community_extensions/faq.md
@@ -48,7 +48,7 @@ For details on securing your DuckDB setup, please refer to the [Securing Extensi
 
 <div class="answer" markdown="1">
 
-Writing a DuckDB extension as a collection of SQL macro is already done be a few extensions. The [pivot_table]{% link community_extensions/extensions/pivot_table.md %} and [chsql]{% link community_extensions/extensions/chsql.md %} extensions for example follow this pattern.
+Writing a DuckDB extension as a collection of SQL macro is already done be a few extensions. The [`pivot_table`]({% link community_extensions/extensions/pivot_table.md %}) and [`chsql`]({% link community_extensions/extensions/chsql.md %}) extensions for example follow this pattern.
 
 Currently some C++ wrapper code is required, but this is possibly the simplest way to build a community extension *and* the best way to package a set of utility macros to be safely distributed.