Rename parodos to rhdhorchestrator

Signed-off-by: gabriel-farache <[email protected]>

docs/README.md

@@ -11,11 +11,11 @@ The repository includes a variety of serverless workflows, such as:
 ## Usage
 
 ### Prerequisites
-To utilize the workflows contained in this repository, the Orchestrator Deployment must be installed on your OpenShift Container Platform (OCP) cluster. For detailed instructions on installing the Orchestrator, please visit the [Orchestrator Helm Based Operator Repository](https://www.parodos.dev/orchestrator-helm-operator/)
+To utilize the workflows contained in this repository, the Orchestrator Deployment must be installed on your OpenShift Container Platform (OCP) cluster. For detailed instructions on installing the Orchestrator, please visit the [Orchestrator Helm Based Operator Repository](https://www.rhdhorchestrator.io/orchestrator-helm-operator/)
 
 ## Installation
 ```bash
-helm repo add orchestrator-workflows https://parodos.dev/serverless-workflows-config
+helm repo add orchestrator-workflows https://rhdhorchestrator.io/serverless-workflows-config
 ```
 
 View available workflows on the Helm repository:
@@ -33,13 +33,13 @@ orchestrator-workflows/workflows	0.2.24       	1.16.0     	A Helm chart for serv
 ...
 ```
 
-You can [install the workflows following their respective README](https://github.com/parodos-dev/serverless-workflows-config/blob/main/docs/main/)
+You can [install the workflows following their respective README](https://github.com/rhdhorchestrator/serverless-workflows-config/blob/main/docs/main/)
 
 ## Installing workflows in additional namespaces
-When deploying a workflow in a namespace different from where Sonataflow services are running (e.g. sonataflow-infra), there are essential steps to follow. For detailed instructions, see the [Additional Workflow Namespaces section](https://github.com/parodos-dev/orchestrator-helm-operator/tree/main/docs/release-1.2?tab=readme-ov-file#additional-workflow-namespaces).
+When deploying a workflow in a namespace different from where Sonataflow services are running (e.g. sonataflow-infra), there are essential steps to follow. For detailed instructions, see the [Additional Workflow Namespaces section](https://github.com/rhdhorchestrator/orchestrator-helm-operator/tree/main/docs/release-1.2?tab=readme-ov-file#additional-workflow-namespaces).
 
 ## Version Compatability
-The workflows rely on components included in the [Orchestrator Operator](https://www.parodos.dev/orchestrator-helm-operator/). Therefore, it is crucial to match the workflow version with the corresponding Orchestrator version that supports it. 
+The workflows rely on components included in the [Orchestrator Operator](https://www.rhdhorchestrator.io/orchestrator-helm-operator/). Therefore, it is crucial to match the workflow version with the corresponding Orchestrator version that supports it. 
 The list below outlines the compatibility between the workflows and Orchestrator versions:
 | Workflows          | Chart Version | Orchestrator Operator Version |
 |--------------------|---------------|----------------------|
@@ -63,4 +63,4 @@ The list below outlines the compatibility between the workflows and Orchestrator
 
 
 ## Helm index
-[https://www.parodos.dev/serverless-workflows-config/index.yaml](https://www.parodos.dev/serverless-workflows-config/index.yaml)
+[https://www.rhdhorchestrator.io/serverless-workflows-config/index.yaml](https://www.rhdhorchestrator.io/serverless-workflows-config/index.yaml)