Fix/documentation fixes (#13)

Fixed 
- links all over the the new installation docs
- typos
-  Replace a duplicated guide that was in one of the files 

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Documentation**
- Updated and added installation guides for SettleMint Blockchain
Transformation Platform (BTP) on Kubernetes.
    - Introduced new category labels for better organization.
- Provided support, troubleshooting guidance, and quick start examples
for trial installations.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: saeeddawod <[email protected]>

Author: SaeeDawod

docs/launch-platform/self-hosted/installing-on-an-existing-cluster/introduction.md

@@ -12,8 +12,9 @@ Welcome to the SettleMint Blockchain Transformation Platform (BTP) guide. This g
 - [Understand the installation process](#understand-the-installation-process)
 - [Quick Start & Trial installations](/docs/launch-platform/self-hosted/installing-on-an-existing-cluster/quick-start-examples-trial-installation/installation-trial-cluster/)
 - [Prerequisites](/docs/launch-platform/self-hosted/installing-on-an-existing-cluster/prerequisites/Infrastructure/)
-- [Run the Installation](#)
-- [Get Support](#) 
+
+- [Run the Installation](/docs/launch-platform/self-hosted/installing-on-an-existing-cluster/run-the-Installation/)
+- [Get Support](/docs/launch-platform/self-hosted/installing-on-an-existing-cluster/support-and-troubleshooting/) 
 
 ## Introduction
 
@@ -25,7 +26,7 @@ It also provides numerous benefits, such as enabling you to specify the high ava
 
 <!-- DIAGRAM HERE -->
 
-After finishing the installation, you will have access to a suite of services and tools designed to support you throughout your blockchain journey. To explore these tools in detail, we invite you to visit our [Developer Hub](#). 
+After finishing the installation, you will have access to a suite of services and tools designed to support you throughout your blockchain journey. To explore these tools in detail, we invite you to visit our [Developer Hub](/docs/about-settlemint/intro/). 
 
 - **Public chains**: Polygon PoS, Polygon zkevm, Ethereum, Avalanche, Arbitrum, Optimism, Binance Smart Chain *(Internet access required)*
 - **Private chains**: Hyperledger Besu, Quorum, Hyperledger Fabric
@@ -35,7 +36,7 @@ After finishing the installation, you will have access to a suite of services an
 - **Integrated IDE**: Including smart contract sets
 - **Smart contract Indexer**: The Graph Middleware 
 
-It's essential to remember that preparing your infrastructure and necessary services is a [prerequisite](link). Once this foundation is established, you'll need to populate the helm charts values file, as detailed in the subsequent "Platform installation” section.
+It's essential to remember that preparing your infrastructure and necessary services is a [prerequisite](/docs/launch-platform/self-hosted/installing-on-an-existing-cluster/prerequisites/Infrastructure/). Once this foundation is established, you'll need to populate the helm charts values file, as detailed in the subsequent "Platform installation” section.
 
 ## Understand the Installation Process
 
@@ -54,7 +55,8 @@ Should you encounter any issues or have questions during any phase of the instal
 
 
 Next: 
-- [Explore one of our trial installations](#) to get a hands-on feel for the platform
-- [Proceed to the prerequisites page](#) to prepare for a full installation
+- [Explore one of our trial installations](/docs/launch-platform/self-hosted/installing-on-an-existing-cluster/quick-start-examples-trial-installation/installation-trial-cluster/) to get a hands-on feel for the platform
+- [Proceed to the prerequisites page](/docs/launch-platform/self-hosted/installing-on-an-existing-cluster/prerequisites/Infrastructure/) to prepare for a full installation
+
 
 

docs/launch-platform/self-hosted/installing-on-an-existing-cluster/prerequisites/Infrastructure.md

@@ -7,7 +7,8 @@ Before starting the installation, ensure your environment meets the following re
 
 # Infrastructure
 
-The following components are a prerequisite to run BTP successfully. Collect the values here to use them later in the [helm chart values file](#).
+
+The following components are a prerequisite to run BTP successfully. Collect the values here to use them later in the [helm chart values file](/docs/launch-platform/self-hosted/installing-on-an-existing-cluster/run-the-Installation/).
 
 At this stage, we highly recommend taking a moment to explore our quick start examples, if you haven't already. This will give you a valuable overview of the different components involved.
 
@@ -40,7 +41,8 @@ For the successful operation of the SettleMint Blockchain Transformation Platfor
 
 - `hostname`: the hostname on which BTP will be available. This domain name needs to be routed to the public IP address of the ingress controller service.
 
- [In your values file](#)
+ [In your values file](/docs/launch-platform/self-hosted/installing-on-an-existing-cluster/run-the-Installation/)
+
 
 ```yaml
 ingress:
@@ -90,8 +92,7 @@ keycloak:
   clientSecret: ""
   issuerURL: ""
 ```
-
- [In your values file](#)
+ [In your values file](/docs/launch-platform/self-hosted/installing-on-an-existing-cluster/run-the-Installation/)
 
 ```yaml
 auth:
@@ -114,9 +115,7 @@ A typical set of parameters you should collect:
 - port: the port of the redis server
 - password: the password of the redis server
 
-
-
- [In your values file](#)
+ [In your values file](/docs/launch-platform/self-hosted/installing-on-an-existing-cluster/run-the-Installation/)
 
 ```yaml
  redis:
@@ -138,7 +137,8 @@ If you don't currently have a PostgreSQL server, you can set it up yourself by f
 - `password`: the password of the PostgreSQL server
 - `database`: the database name of the PostgreSQL server
 
- [In your values file](#)
+ [In your values file](/docs/launch-platform/self-hosted/installing-on-an-existing-cluster/run-the-Installation/)
+
 
 ```yaml
 postgresql:
@@ -162,7 +162,7 @@ The state information is always encrypted. By default, encryption is performed u
 - `accessKeyId`: This is the access key for the specified bucket.
 - `secretAccessKey`: This is the secret access key for the specified bucket.
 
- [In your values file](#)
+ [In your values file](/docs/launch-platform/self-hosted/installing-on-an-existing-cluster/run-the-Installation/)
 
 ```yaml
 state:
@@ -186,7 +186,7 @@ Additionally, an AppRole is necessary to facilitate access to these secrets.
 - `roleId`: the roleId of the AppRole
 - `secretId`: the secretId of the AppRole
 
- [In your values file](#)
+ [In your values file](/docs/launch-platform/self-hosted/installing-on-an-existing-cluster/run-the-Installation/)
 
 ```yaml
 vault:
@@ -206,7 +206,8 @@ This observability suite is optional and can be activated as described below.
 - Prometheus API URL: this is an example from Grafana cloud: `https://prometheus-prod-01-eu-west-0.grafana.net/api/prom/api/v1/`
 - Loki API URL: this is an example from Grafana cloud: `https://logs-prod-eu-west-0.grafana.net/loki/api/v1/`
 
- [In your values file](#)
+ [In your values file](/docs/launch-platform/self-hosted/installing-on-an-existing-cluster/run-the-Installation/)
+
 
 ```yaml
 features:
@@ -255,7 +256,9 @@ To facilitate this, activate **p2pLoadBalancers** and configure DNS name managem
 
 In addition, the 'mixedLoadBalancers' option facilitates the creation of TCP/UDP load balancers on the same port, which is essential for enabling discovery mechanisms.
 
- [In your values file](#)
+
+ [In your values file](/docs/launch-platform/self-hosted/installing-on-an-existing-cluster/run-the-Installation/)
+
 
 ```yaml
 targets: