fix: update blog authors

chaos-days/blog/2023-12-18-Dynamically-scaling-brokers/index.md

@@ -8,7 +8,7 @@ categories:
 tags:
   - availability
   - performance
-authors: ole
+authors: lena
 ---
 
 # Chaos Day Summary
@@ -322,4 +322,4 @@ Node      |Partition 1         |Partition 2         |Partition 3           |Part
 ```
 
 The operation completes in 21 minutes, longer than usual because of the restarts:
-![](scaledown-completed.png)
+![](scaledown-completed.png)

chaos-days/blog/2023-12-19-Dynamic-Scaling-with-Dataloss/index.md

@@ -7,7 +7,7 @@ categories:
   - bpmn
 tags:
   - availability
-authors: ole
+authors: lena
 ---
 
 # Chaos Day Summary
@@ -147,4 +147,4 @@ We want to improve this behavior in the future but likely can't prevent it compl
 That means that there is an increased risk of unavailable partitions during scaling.
 However, this only occurs if another broker becomes unavailable with an unfortunate timing and resolves itself automatically once the broker is available again.
 
-Zeebe issue: https://github.com/camunda/camunda/issues/15679
+Zeebe issue: https://github.com/camunda/camunda/issues/15679

chaos-days/blog/2023-12-20-Broker-scaling-performance/index.md

@@ -9,7 +9,7 @@ tags:
   - availability
   - performance
 authors:
-  - ole
+  - lena
   - deepthi
 ---
 
@@ -180,4 +180,4 @@ Job lifetime and overall processing latency is still better than before scaling
 ![](./perf_increased_load_processing_latency.png)
 
 
-Overall, this shows that scaling up can improve processing performance significantly, especially when the initial cluster setup is resource limited and vertical scaling is not possible.
+Overall, this shows that scaling up can improve processing performance significantly, especially when the initial cluster setup is resource limited and vertical scaling is not possible.