From a0d5f132b4b6c5dc25b966fc4c7801436924f12d Mon Sep 17 00:00:00 2001
From: Kamron Batman <3953314+kamronbatman@users.noreply.github.com>
Date: Thu, 2 Feb 2023 19:40:15 -0800
Subject: [PATCH] fix: Fixes identation in docs note (#1328)

---
 docs/scripting-guide/serialization.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/scripting-guide/serialization.md b/docs/scripting-guide/serialization.md
index 0cfc14891..ccca4ae62 100644
--- a/docs/scripting-guide/serialization.md
+++ b/docs/scripting-guide/serialization.md
@@ -193,6 +193,6 @@ title: Serialization
 
 
     !!! Note
-      Non-entity classes cannot be serialized by reference since that would require a reference Serial or ID. This means if the object is a serializable property on multiple objects, it will be serialized
-      multiple times and will effectively get duplicated on world load. Consider either making it an `ISerializable` type and building world load/save mechanisms, or do not serialize the nested object directly.
-      Instead opt for a global lookup, serialize with generic persistence, and then reattach to the objects using the `WorldLoad` event sink.
+        Non-entity classes cannot be serialized by reference since that would require a reference Serial or ID. This means if the object is a serializable property on multiple objects, it will be serialized
+        multiple times and will effectively get duplicated on world load. Consider either making it an `ISerializable` type and building world load/save mechanisms, or do not serialize the nested object directly.
+        Instead opt for a global lookup, serialize with generic persistence, and then reattach to the objects using the `WorldLoad` event sink.