fixes

Author: sbernauer

modules/contributor/pages/adr/ADR030-reduce-pod-disruptions.adoc

@@ -11,12 +11,13 @@ v0.1, 2023-09-15
 == Context and Problem Statement
 
 Downtime of products is always bad.
-Kubernetes has a a concepts called https://kubernetes.io/docs/tasks/run-application/configure-pdb/[PodDisruptionBudget] (PDB) to try to reduce this to an absolute minimum.
+Kubernetes has a a concepts called https://kubernetes.io/docs/tasks/run-application/configure-pdb/[PodDisruptionBudget] (PDB) to prevent this.
+We want to use this functionary to try to reduce the downtime to an absolute minimum.
 
 *Requirements:*
 
 1. We must deploy a PDB alongside all the product StatefulSets (and Deployments in the future) to restrict pod disruptions.
-2. Also users need to ability to override the numbers we default to, as they need to make a tradeoff between availability and rollout times e.g. in rolling redeployment. Context: I have operated Trino clusters that could take more than 6 hours to rolling redeploy, as the graceful shutdown of Trino workers takes a considerable amount of time - depended on the queries getting executed.
+2. Also users need the ability to override the numbers we default to, as they need to make a tradeoff between availability and rollout times e.g. in rolling redeployment. Context: I have operated Trino clusters that could take more than 6 hours to rolling redeploy, as the graceful shutdown of Trino workers takes a considerable amount of time - depended on the queries getting executed.
 
 We have the following constraints: