From da10bf1678133baae9085a96aeffdb9a0dbaa12f Mon Sep 17 00:00:00 2001
From: Sajiyah Salat <109643863+Sajiyah-Salat@users.noreply.github.com>
Date: Mon, 8 May 2023 07:50:59 +0530
Subject: [PATCH] Update creating-events.md

---
 docs/book/src/reference/creating-events.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/book/src/reference/creating-events.md b/docs/book/src/reference/creating-events.md
index e4554868ef3..86c5b3652f0 100644
--- a/docs/book/src/reference/creating-events.md
+++ b/docs/book/src/reference/creating-events.md
@@ -103,7 +103,7 @@ Building on the example introduced in [Controller Example](../basics/simple_cont
 Events should be raised in certain circumstances only and following this guideline acctually is not a good practice. See what the Kubernetes APIs convention describes when using them [here][Events]
 
 <aside class="note">
-It is NOT recommended to emit events for all Operations. If authors raise too many events it brings bad UX experiences for those that are consuming the solutions on the cluster and they will not have attention to what they actually must be notified.
- </aside>
+       It is NOT recommended to emit events for all Operations. If authors raise too many events it brings bad UX experiences for those that are consuming the        solutions on the cluster and they will not have attention to what they actually must be notified.
+</aside>
 
 [Events]: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#events