diff --git a/docs/docs/installation/manual/index.md b/docs/docs/installation/manual/index.md
index 517335c..f8be104 100644
--- a/docs/docs/installation/manual/index.md
+++ b/docs/docs/installation/manual/index.md
@@ -14,7 +14,7 @@ The documentation of this method is being written right now. We recommend using
 
 This section will explain how to deploy the platform manually. Basically, you will have to deploy or install the different components and then connect them. The procedure explained below is the one followed to deploy them in **Kubernetes** using in most cases the **Helm** option, but any other installation in which all the components are correctly installed and there is some kind of network between them to be able to communicate can be used. 
 
-It is not necessary to deploy all components if not all functionalities are to be used. Check the [architecture](../overview/architecture.md) section to find out which ones are essential and what functionality is covered by each of them.
+It is not necessary to deploy all components if not all functionalities are to be used. Check the [architecture](../../overview/architecture.md) section to find out which ones are essential and what functionality is covered by each of them.
 
 Follow the instructions for the features you want to include in OpenTwins:
 
diff --git a/docs/docs/overview/architecture.md b/docs/docs/overview/architecture.md
index 41993f2..698b643 100644
--- a/docs/docs/overview/architecture.md
+++ b/docs/docs/overview/architecture.md
@@ -82,7 +82,7 @@ Although it may seem a secondary aspect, the representation of the digital twin
 
 :::note
 
-Although it is possible to deploy and connect the different components without containerization, this approach is not recommended due to the difficulties involved in terms of installation and management. However, it is important to note that Lightweight version of OpenTwins could be [manually connected](../installation/manual.md) to non-containerized components.
+Although it is possible to deploy and connect the different components without containerization, this approach is not recommended due to the difficulties involved in terms of installation and management. However, it is important to note that Lightweight version of OpenTwins could be [manually connected](../installation/manual/index.md) to non-containerized components.
 
 :::