From 960a1f7a4a9d25e525aa4fa83231d49876dd3d88 Mon Sep 17 00:00:00 2001
From: Junseo Yoo <59751754+joonyoo181@users.noreply.github.com>
Date: Wed, 12 Jun 2024 09:32:41 -0700
Subject: [PATCH] grammar fix: "interactions" -> "interaction"

Co-authored-by: vegorov-rbx <75688451+vegorov-rbx@users.noreply.github.com>
---
 docs/rawget-type-operator.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/rawget-type-operator.md b/docs/rawget-type-operator.md
index 75ccbe2..8bdffd0 100644
--- a/docs/rawget-type-operator.md
+++ b/docs/rawget-type-operator.md
@@ -44,7 +44,7 @@ The implementation effort for this type operator is very minimal. Since the `raw
 
 There aren't appreciable drawbacks. One possible drawback is the increase in the size of the codebase, which may complicate maintenance. However, this is not expected to be a major drawback since the code for `index` type operators already exists. By reusing the code, it is even fair to say that there will be less than 50 lines of code needed to implement this type operator.
 
-Another drawback can come from the extra knowledge a user may need in order to use this type operator. For example, users will need to know the inner workings of types and how different operations interact with them (for instance, how `index` interacts with metatables that have the `__index` metamethod). However, there are documentations that outline each interactions, and thus this drawback does not seem to pose an issue.
+Another drawback can come from the extra knowledge a user may need in order to use this type operator. For example, users will need to know the inner workings of types and how different operations interact with them (for instance, how `index` interacts with metatables that have the `__index` metamethod). However, there are documentations that outline each interaction, and thus this drawback does not seem to pose an issue.
 
 ## Alternatives