diff --git a/reference/extending/design-guidelines.md b/reference/extending/design-guidelines.md
index a37ef1e..76ef2ca 100644
--- a/reference/extending/design-guidelines.md
+++ b/reference/extending/design-guidelines.md
@@ -238,4 +238,4 @@ Don't reference your own nuget in any .vl documents that contribute to a nuget o
 Still to be defined: in what form to provide tests (patches, code,..) that can be run automated
 
 ### Help Patches
-See [Providing Help](providinghelp.md)
+See [Providing Help](providing-help.md)
diff --git a/reference/extending/writing-nodes.md b/reference/extending/writing-nodes.md
index fe4933c..cf4b6f9 100644
--- a/reference/extending/writing-nodes.md
+++ b/reference/extending/writing-nodes.md
@@ -76,7 +76,7 @@ Every static or member method of a public class you write in C# will turn into a
 Here are some simple examples and a few more details that will help you create your own nodes. Those are also available via:
  https://github.com/vvvv/VL.DemoLib
 
-For more general considerations also see: [Design Guidelines](design_guidelines.md)
+For more general considerations also see: [Design Guidelines](design-guidelines.md)
 
 ### Namespaces 
 The Namespace you specify in C# will turn into the nodes category in VL. Nested namespaces (using dot syntax) will be translated to nested categories accordingly.