From 960e34e2332e7666190119169101143647dac8d9 Mon Sep 17 00:00:00 2001
From: gaymeowing <62822174+gaymeowing@users.noreply.github.com>
Date: Mon, 7 Apr 2025 08:21:02 -0400
Subject: [PATCH] Motivation grammar fix

---
 docs/user-defined-type-function-strings-as-keys.md | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/docs/user-defined-type-function-strings-as-keys.md b/docs/user-defined-type-function-strings-as-keys.md
index 38ee054..cb15940 100644
--- a/docs/user-defined-type-function-strings-as-keys.md
+++ b/docs/user-defined-type-function-strings-as-keys.md
@@ -6,9 +6,7 @@ This RFC proposes allowing strings as keys for methods on the `table` type userd
 
 ## Motivation
 
-Currently having to always wrap string literal keys in `types.singleton` is annoying, and becomes especially annoying when using `types.newtable` due to having to write `[types.singleton("key")]` for every single key in the props table.
-
-This leads to developers having to write the following:
+Currently having to always wrap string literal keys in `types.singleton` is annoying, and becomes especially annoying when using `types.newtable` due to having to write something like the following:
 
 ```luau
 types.newtable({
@@ -17,7 +15,7 @@ types.newtable({
 })
 ```
 
-When the following could be written instead, if it were allowed:
+Instead of:
 
 ```luau
 types.newtable({