renamed options

Author: fhennig

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

@@ -92,7 +92,7 @@ spec:
 
 NOTE: In the discussion the option of having the PDB directly in the role without a `roleConfig` was briefly discussed but not considered as an option due to being too messy, so it is not listed as an explicit option here.
 
-=== Option 2a - PDB in `config`, but only at role level
+=== Option 2 - PDB in `config`, but only at role level
 
 Instead of inventing a new `roleConfig` setting, put the PDB in the `config`. This might seem better at first, but usually settings in `config` can also be set at role group level, and in this case, that would not be true.
 
@@ -123,9 +123,9 @@ spec:
 * Still no option to configure role group level PDBs
 * Possibly complicated to implement, due to `config` usually being identical at role and role group level
 
-=== Option 2b: PDB in config with elaborate merge mechanism
+=== Option 3: PDB in config with elaborate merge mechanism
 
-Similar to Option 2a, the PDB setting is located in the `config` but it is actually possible to use it at both role and role group level.
+Similar to Option 2, the PDB setting is located in the `config` but it is actually possible to use it at both role and role group level.
 We develop a semantic merge mechanism that would prevent overlapping PDBs.
 
 .CRD Example
@@ -212,7 +212,7 @@ spec:
 * Complex merge mechanism possibly difficult to understand and therefore easy to use the wrong way
 * Complex mechanism also not trivial to implement 
 
-=== Option 2c - PDB in config with normal "shared role group config" behaviour
+=== Option 4 - PDB in config with normal "shared role group config" behaviour
 
 Again we put the PDB in the `config` section but simply use the normal "copy" behaviour for this setting.
 This would be simple and easy to understand, but does not allow for true role level PDBs.