fix: mermaid diagrams for docsy (#2461)

Signed-off-by: Attila Mészáros <csviri@gmail.com>

Author: csviri

docsy/content/en/docs/dependent-resources/_index.md

@@ -14,7 +14,7 @@ the `Deployment` controller.
 Controllers that deal with secondary resources typically need to perform the following steps, for
 each secondary resource:
 
-<div class="mermaid" markdown="0"> 
+```mermaid
 flowchart TD
 
 compute[Compute desired secondary resource based on primary state] --> A
@@ -25,8 +25,7 @@ A -- No --> Create --> Done
 match{Matches desired state?}
 match -- Yes --> Done
 match -- No --> Update --> Done
-
-</div>
+```
 
 While these steps are not difficult in and of themselves, there are some subtleties that can lead to
 bugs or sub-optimal code if not done right. As this process is pretty much similar for each

docsy/content/en/docs/workflows/_index.md

@@ -230,15 +230,14 @@ Notation: The arrows depicts reconciliation ordering, thus following the reverse
 
 #### Reconcile Sample
 
-<div class="mermaid" markdown="0"> 
-
+```mermaid
 stateDiagram-v2
 1 --> 2
 1 --> 3
 2 --> 4
 3 --> 4
+```
 
-</div>
 
 - Root nodes (i.e. nodes that don't depend on any others) are reconciled first. In this example,
   DR `1` is reconciled first since it doesn't depend on others.
@@ -252,15 +251,15 @@ stateDiagram-v2
 
 #### Sample with Reconcile Precondition
 
-<div class="mermaid" markdown="0"> 
-
+ 
+```mermaid
 stateDiagram-v2
 1 --> 2
 1 --> 3
 3 --> 4
 3 --> 5
+```
 
-</div>
 
 - If `3` has a reconcile pre-condition that is not met, `1` and `2` would be reconciled. However,
   DR `3`,`4`,`5` would be deleted: `4` and `5` would be deleted concurrently but `3` would only
@@ -285,16 +284,14 @@ is not met, just for the whole workflow.
    `Deleter` interface, it is considered as deleted automatically.
 
 ### Sample
-
-<div class="mermaid" markdown="0"> 
-
+ 
+```mermaid
 stateDiagram-v2
 1 --> 2
 1 --> 3
 2 --> 4
 3 --> 4
-
-</div>
+```
 
 - The DRs are deleted in the following order: `4` is deleted first, then `2` and `3` are deleted
   concurrently, and, only after both are successfully deleted,  `1` is deleted.