From 46d4fbd038b40aba87dd596ddf63e06b977a232f Mon Sep 17 00:00:00 2001
From: Alan Jeffrey <403333+asajeffrey@users.noreply.github.com>
Date: Tue, 21 Sep 2021 17:18:35 -0500
Subject: [PATCH] Apply suggestions from code review

Co-authored-by: Lily Brown <lily@lily.fyi>
---
 rfcs/unsealed-table-assign-optional-property.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/rfcs/unsealed-table-assign-optional-property.md b/rfcs/unsealed-table-assign-optional-property.md
index 57e7f0fd..78f674aa 100644
--- a/rfcs/unsealed-table-assign-optional-property.md
+++ b/rfcs/unsealed-table-assign-optional-property.md
@@ -23,8 +23,8 @@ Currently, this code doesn't typecheck, due to `p` and `q` being unknown propert
 
 ## Design
 
-In order to support this idiom, we propose that assigning a table with
-to an unsealed table should add an optional proerty.
+In order to support this idiom, we propose that assigning a table
+to an unsealed table should add an optional property.
 
 For example, before this change the type of `t` is `{ u: {} }`,
 and after this change is `{ u: { p: number?, q: number? } }`.