From 39fa341c12e3b1a61053ed4d66f2cf013a6d8514 Mon Sep 17 00:00:00 2001
From: Peter Sorensen <6152801+psorensen@users.noreply.github.com>
Date: Mon, 22 Jan 2024 15:42:25 -0800
Subject: [PATCH] Update block-transforms.md

---
 reference/03-Blocks/block-transforms.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/reference/03-Blocks/block-transforms.md b/reference/03-Blocks/block-transforms.md
index 4a9ab55..4fb025b 100644
--- a/reference/03-Blocks/block-transforms.md
+++ b/reference/03-Blocks/block-transforms.md
@@ -12,7 +12,7 @@ This is super useful to allow editors to quickly switch between different types
 
 ## When to use Block Transforms
 
-In theory most blocks should have block transformations defined. They make the live of the editors much easier. With the ability to transform one block into another one this can also be leveraged in order to not build overly complex blocks with too many options. Instead it is often easier and faster to build two separate blocks and allow the user to transform between them.
+In theory most blocks should have block transformations defined. They make the lives of the editors much easier. With the ability to transform one block into another one this can also be leveraged in order to not build overly complex blocks with too many options. Instead it is often easier and faster to build two separate blocks and allow the user to transform between them.
 
 Finally one more use-case is using the transforms in order to add a controlled update path for users. Let's imagine you have a project where you build a block two different blocks that work in slightly different ways. Further down the line in the project you find that the client now has new requirements that make these two blocks obsolete. Instead they want to replace the two blocks with one that can solve for both use-cases at the same time.