fix: typos and links

Author: guewa

docs/concepts/Concepts.md

@@ -48,7 +48,7 @@ detail.
 **Index**:
 - [Concept](#concept)
     - [Landscaper Data Plane](#landscaper-data-plane)
-    - [Data-Flow and Installation-Unit-Decoupling](#dataflow-and-installation-unit-decoupling)
+    - [Dataflow and Installation-Unit-Decoupling](#dataflow-and-installation-unit-decoupling)
     - [Decoupling of Concrete Installations from Installation Descriptions](#decoupling-of-concrete-installations-from-installation-descriptions)
     - [Deploy Items and Deployers](#deploy-items-and-deployers)
     - [Deployers and Deploy Targets](#deployers-and-deploy-targets)

docs/guided-tour/README.md

@@ -10,7 +10,7 @@ sidebar_position: 1
 - For all examples, you need a [running Landscaper instance](../installation/install-landscaper-controller.md).
 
 - A convenient tool we will often use in the following examples is the [Landscaper
-  CLI](https://github.com/gardener/landscapercli). 
+  CLI](https://github.com/openmcp-project/landscapercli). 
 
 - For building reusable components you require the [OCM CLI](https://ocm.software/docs/getting-started/prerequisites).
 

docs/guided-tour/error-handling/delete-error/README.md

@@ -61,7 +61,7 @@ Now the installation should be gone and the deployed Helm chart should be uninst
 ### Force Delete
 
 If for some reason it is not possible to resolve the problems as described above and it is ok that the deployed Helm chart is not uninstalled automatically, 
-you could use the [landscaper-cli](https://github.com/gardener/landscapercli) to remove the installation. 
+you could use the [landscaper-cli](https://github.com/openmcp-project/landscapercli) to remove the installation. 
 This is the preferred solution if the target cluster does not exist anymore. You can achieve this with the following command:
 
 ```shell

docs/guided-tour/hello-world/README.md

@@ -44,7 +44,7 @@ and applies both on the resource cluster.
 
 ### Alternative Way to Create a Target
 
-There is an alternative way to create a Target custom resource. It requires the [Landscaper CLI](https://github.com/gardener/landscapercli):
+There is an alternative way to create a Target custom resource. It requires the [Landscaper CLI](https://github.com/openmcp-project/landscapercli):
 
 ```shell
 landscaper-cli targets create kubernetes-cluster \
@@ -86,7 +86,7 @@ status:
   phase: Succeeded
 ```
 
-If you have already installed the [Landscaper CLI](https://github.com/gardener/landscapercli), 
+If you have already installed the [Landscaper CLI](https://github.com/openmcp-project/landscapercli), 
 you can inspect the status of the installation with the following command, executed on the Landscaper resource cluster:
 
 ```shell

docs/installation/install-landscaper-controller.md

@@ -7,7 +7,7 @@ This document describes the installation of Landscaper.
 #### Option 1: Installation via the landscaper-cli tool
 The easiest way to install the landscaper with its default deployer is to use the _landscaper-cli_. The corresponding 
 documentation can be found 
-[here](https://github.com/gardener/landscapercli/blob/master/docs/commands/quickstart/install.md).
+[here](https://github.com/openmcp-project/landscapercli/blob/master/docs/commands/quickstart/install.md).
 
 #### Option 2: Installation via helm
 Alternatively, the landscaper can also be installed via [helm](https://helm.sh/) using the helm chart in 

docs/troubleshooting/troubleshooting.md

@@ -165,6 +165,6 @@ Note that the new reconciliation does not start before the Installation has reac
 
 <!-- References -->
 
-[1]: https://github.com/gardener/landscapercli/blob/master/docs/reference/landscaper-cli_installations_inspect.md
+[1]: https://github.com/openmcp-project/landscapercli/blob/master/docs/reference/landscaper-cli_installations_inspect.md
 
 [2]: https://github.com/gardener/landscaper/blob/master/docs/usage/Annotations.md#reconcile-annotation