diff --git a/content/00.build/90.contributing-to-documentation/30.documentation-styleguide.md b/content/00.build/90.contributing-to-documentation/30.documentation-styleguide.md
index 147721cf..427fd571 100644
--- a/content/00.build/90.contributing-to-documentation/30.documentation-styleguide.md
+++ b/content/00.build/90.contributing-to-documentation/30.documentation-styleguide.md
@@ -36,7 +36,7 @@ To minimize confusion due to global date format variations, adhere to the follow
 
 ## Kinds of zkSync Documentation
 
-Following the Diataxis framework, zkSync Docs categorizes content into:
+Following the [Diataxis](https://diataxis.fr/) framework, zkSync Docs categorizes content into:
 
 - **Tutorials**: Step-by-step instructions to teach general skills (e.g., Deploying your first contract on zkSync Era).
 - **Guides**: Task completion instructions for readers with basic knowledge (e.g., Debugging with zksync-cli).
@@ -46,7 +46,7 @@ Following the Diataxis framework, zkSync Docs categorizes content into:
 
 ### Choosing a category for writing
 
-Leverage the Diataxis system when crafting a new article for zkSync Docs.
+Leverage the [Diataxis](https://diataxis.fr/) system when crafting a new article for zkSync Docs.
 Writing without a clear category often results in unfocused content.
 A well-defined focus keeps the content streamlined and clarifies the takeaway for the reader.