docs: fix link

Author: LukasGentele

docs/pages/configuration/deployments/helm/chart/local.mdx

@@ -7,7 +7,7 @@ DevSpace can deploy Helm charts located on the same filesystem as the `devspace.
 
 
 ## Local Charts vs Dependencies
-If you have multiple services located in the same git repository (monorepo), you may be tempted to have a single `devspace.yaml` at the root of the git repository and then specify one deployment for each service using a local path to each service's chart folder, for example. However, ideally you want to encapsule the build, deployment and development logic for each service inside a separate devspace.yaml that is located very closely to the actual code. This allows you work on microservices independenctly and only pull in other services if they are actually needed. DevSpace provides a feature called [`dependencies`](../../dependencies/README.mdx) which allows you to define relationships between `devspace.yaml` files to allow users to start working on a service while DevSpace stands up and maintains dependent microservices if needed.
+If you have multiple services located in the same git repository (monorepo), you may be tempted to have a single `devspace.yaml` at the root of the git repository and then specify one deployment for each service using a local path to each service's chart folder, for example. However, ideally you want to encapsule the build, deployment and development logic for each service inside a separate devspace.yaml that is located very closely to the actual code. This allows you work on microservices independenctly and only pull in other services if they are actually needed. DevSpace provides a feature called [`dependencies`](../../../dependencies/README.mdx) which allows you to define relationships between `devspace.yaml` files to allow users to start working on a service while DevSpace stands up and maintains dependent microservices if needed.
 
 
 ## Local Helm Charts