From 54d7b167adb01d699b01036b09d45df1d8f52671 Mon Sep 17 00:00:00 2001
From: Ori Shoshan <ori@otterize.com>
Date: Fri, 15 Mar 2024 00:54:42 +0100
Subject: [PATCH] fixup

---
 .../tutorials/aws-eks-cni-mini.mdx                        | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/features/network-mapping-network-policies/tutorials/aws-eks-cni-mini.mdx b/docs/features/network-mapping-network-policies/tutorials/aws-eks-cni-mini.mdx
index 07bad7f1f..00d96bb23 100644
--- a/docs/features/network-mapping-network-policies/tutorials/aws-eks-cni-mini.mdx
+++ b/docs/features/network-mapping-network-policies/tutorials/aws-eks-cni-mini.mdx
@@ -33,11 +33,11 @@ Run the following command to create your AWS cluster. [Don't have eksctl? Instal
 curl ${ABSOLUTE_URL}/code-examples/aws-eks-mini/cluster-config.yaml | eksctl create cluster -f -
 ```
 <details>
-    <summary>Inspect eks-cluster.yaml contents</summary>
+<summary>Inspect eks-cluster.yaml contents</summary>
 
-    ```yaml
-    {@include: ../../../../static/code-examples/aws-eks-mini/cluster-config}
-    ```
+```yaml
+{@include: ../../../../static/code-examples/aws-eks-mini/cluster-config.yaml}
+```
 </details>
 
 Once your AWS EKS has finished deploying the control pane and node group, the next step is deploying Otterize as well as a couple of clients and a server to see how they are affected by network policies.