feat(operations): Reworded the operations section

content/en/docs/edp/operations/_index.md

@@ -6,66 +6,80 @@ description: >
   Operational guides for deploying, monitoring, and maintaining the Edge Developer Platform components.
 ---
 
-
 ## Operations Overview
 
-This section covers operational aspects of the Edge Developer Platform. In general there is no operation - it's just monitoring and fixing in an developer mode of operation.
+This section outlines some of the operational aspects of the Edge Developer
+Platform (EDP). The approach emphasizes a "developer operations" mode, primarily
+focusing on monitoring and issue resolution rather than traditional operations.
 
 ## Deployments
 
-### EDP
+### EDP Clusters
 
-EDP is running on two OTC clusters (remember: this just means that we twice run the [infra-deploy pipeline](https://edp.buildth.ing/DevFW/infra-deploy/actions?workflow=deploy.yaml&actor=0&status=0) as eyerything is code!)
+For details on deploying instances of EDP on OTC, see
+[this](/docs/edp/deployment/otc/) section.
 
-![alt text](otc-hub.png)
+#### Further Infrastructural References
 
-#### Further references for infrastructural informations
+- OTC Documentation:
-
+  - [IPCEI-CIS Confluence - OTC](https://confluence.telekom-mms.com/spaces/IPCEICIS/pages/1000105031/OTC)
-* OTC:
-  * [IPCEI-CIS Confluence](https://confluence.telekom-mms.com/spaces/IPCEICIS/pages/1000105031/OTC)
 
 ### Edge Connect
 
-The Edge and Orka clouds in Edge Connect are in the perspective of eDF just deployment targets of EDP applications. Thus we are user of them. Physically both are Gardener Kubernetes clusters.
+The `edge` and `orca` clouds within Edge Connect serve as deployment targets for
+EDP applications. These environments are [Gardener](https://gardener.cloud/)
+Kubernetes clusters.
 
+For general use, interaction with Edge Connect is intended via its web UI:
+<https://hub.apps.edge.platform.mg3.mdb.osc.live>
 
-Basically it is intended for users just to use the web ui: https://hub.apps.edge.platform.mg3.mdb.osc.live
+![Edge Hub](edge-hub.png)
 
-![alt text](edge-hub.png)
+#### Further Infrastructural References
 
-#### Further references for infrastructural informations
+![Gardener](gardener.png)
 
-![alt text](gardener.png)
+Cluster-level access is available for addressing operational issues. Details on
+obtaining access are provided in the following resources:
 
-But we also got access on the cluster level for operations issues, see picture above. How to get access is described in the following links:
+- [IPCEI-CIS Confluence - Edge Cloud](https://confluence.telekom-mms.com/spaces/IPCEICIS/pages/1122869593/Edge+Cloud)
-  * [IPCEI-CIS Confluence](https://confluence.telekom-mms.com/spaces/IPCEICIS/pages/1122869593/Edge+Cloud)
+- [IPCEI-CIS Jira - Edge Cloud Access](https://jira.telekom-mms.com/browse/IPCEICIS-6222?focusedId=3411527&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-3411527)
-  * [IPCEI-CIS Jira](https://jira.telekom-mms.com/browse/IPCEICIS-6222?focusedId=3411527&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-3411527)
+- **Hint:** To authenticate and obtain the cluster `kubectl` context, retrieve
-  * Hint: Get the kubeconfig of the `platform` in your Gardener Account Settings, then run ```gardenctl target --garden mg3 --project platform --shoot edge``` to authenticate and get the cluster kubectl context.
+  the `kubeconfig` for the `platform` from your Gardener Account Settings. Then,
+  execute:
+  ```bash
+  gardenctl target --garden mg3 --project platform --shoot edge
+  ```
 
 ## Monitoring & Observability
 
-On EDP the observability cluster is meant to monitor the platform stacks, e.g. by [Grafana](https://grafana.observability.buildth.ing).
+The `observability.buildth.ing` cluster within the Prod OTC tenant is designated
-But there is no operational monitoring lifecycle in place. we didn't define metrics or alerts as there is no operational mode yet.
+for monitoring platform stacks, with visualization primarily through
+[Grafana](https://grafana.observability.buildth.ing). Currently, a formal
+operational monitoring lifecycle with defined metrics and alerts is not fully
+established, reflecting the current developer-centric operational mode.
 
-Most monitoring and observability is done through grafana, deployed through the observability stack.
+Most monitoring and observability activities utilize Grafana, which is deployed
+as part of the
+[observability stack](/docs/edp/deployment/infrastructure/stacks/observability/).
+Login credentials can be found in the `grafana-admin-credentials` secret.
 
-Login is found in the `grafana-admin-credentials` secret.
+> NOTE: The deployed stacks are depending on the `is_observability` (Include
+> extra components for observability) flag setting in the `deploy` workflow
+> within the `infra-deploy` repository.
 
-
+![EDP Grafana Dashboard](edp-grafana.png)
-NOTE document that default deployed stacks are different depending on is_observability flag
-
-![alt text](edp-grafana.png)
 
 ## Maintenance
 
-We maintain EDP on an per issue driven strategy.
+EDP maintenance follows an issue-driven strategy.
 
 ### Updates & Upgrades
 
-We update occassionally per [component](../components/), which either can be a [platform application](../components/orchestration/stacks/) or an [orchestration pipeline](../components/forgejo/actions/actions.md).
+Updates are performed on-demand for individual components in
+[stacks](/docs/edp/deployment/infrastructure/stacks/).
 
 ### Backup & Recovery
 
-EDP Customer data is backuped, see https://jira.telekom-mms.com/browse/IPCEICIS-5017
+Customer data within EDP is regularly backed up. Refer to
-
+[IPCEICIS-5017](https://jira.telekom-mms.com/browse/IPCEICIS-5017) for details.
-