diff --git a/docs/development/feature-development-guide.md b/docs/development/feature-development-guide.md
index 585de19369a..5a9ddcc75b2 100644
--- a/docs/development/feature-development-guide.md
+++ b/docs/development/feature-development-guide.md
@@ -6,7 +6,7 @@ This is a guide for developers that are implementing a new feature.
 
 As a first step it is important to determine how complex the proposed feature is. Incremental improvements on existing features are often easier to accomplish and require input from fewer people. Most minor changes can be submitted as a Pull Request. If the proposed feature would require one or more days of work it makes sense to connect on [slack](https://slack.cbioportal.org) to discuss the idea. For more complex new features that require weeks of work or more, it is best to get input from several people in the cBioPortal community, including people with a deep understanding of the cBioPortal product and its users as well as the engineers that write the software. In that case we often start out with a Request For Comments document that describes the feature in more detail, see [our list of RFCs ](../RFC-List.md)for some examples. The community can then help guide the feature development in the right direction.
 
-During this process you will most likely receive some pointers which part of the stack you will be editing (see [Architecture Overview](Architecture-Overview.md)). This will be helpful when actually starting your implementation and figuring out how to set up your development environment. For many features it is not necessary to understand all parts of the stack, so seeking out advice on this is highly recommended.
+During this process you will most likely receive some pointers which part of the stack you will be editing (see [Architecture Overview](../Architecture-Overview.md)). This will be helpful when actually starting your implementation and figuring out how to set up your development environment. For many features it is not necessary to understand all parts of the stack, so seeking out advice on this is highly recommended.
 
 Before you start implementing a more complex feature, ideally many of these things are clear: