From be0e8bb1d0edb4af321e6746de438c76a9bc0f3c Mon Sep 17 00:00:00 2001
From: mattjala <124107509+mattjala@users.noreply.github.com>
Date: Wed, 24 Apr 2024 11:38:21 -0500
Subject: [PATCH] Update obj_store_schema_v2.md

---
 docs/design/obj_store_schema/obj_store_schema_v2.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/design/obj_store_schema/obj_store_schema_v2.md b/docs/design/obj_store_schema/obj_store_schema_v2.md
index 5fa10454..99082e41 100644
--- a/docs/design/obj_store_schema/obj_store_schema_v2.md
+++ b/docs/design/obj_store_schema/obj_store_schema_v2.md
@@ -562,7 +562,7 @@ If the chunk is not compressed, the size of the object would be `10 * 10 * <item
 
 ### Variable Length Data
 
-For fixed length datatypes (or compound type composed of fixed length types), serialization of chunk data is straight forward. For variable
+For fixed length datatypes (or compound types composed of fixed length types), serialization of chunk data is straight forward. For variable
 length data, the data needs an additional field so the original data can be decoded again on read. This is done by adding a 4-byte element
 length in front of each element when writing to storage. The length describes the number of bytes used by that element. On read, the length
 field can be used to allocate heap memory to store the given element.