From 351aa2a482cda4ec88899f3fbf5c06eb35869949 Mon Sep 17 00:00:00 2001
From: Ethan McKanna <105890749+EthanMcKanna@users.noreply.github.com>
Date: Tue, 29 Aug 2023 19:27:55 -0500
Subject: [PATCH] Better word choice for solid-modeling.md

---
 content/en-us/parts/solid-modeling.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en-us/parts/solid-modeling.md b/content/en-us/parts/solid-modeling.md
index 331007888..658c730a7 100644
--- a/content/en-us/parts/solid-modeling.md
+++ b/content/en-us/parts/solid-modeling.md
@@ -175,7 +175,7 @@ While a value between 30 and 70 degrees usually produces a good result, values b
 In addition to the **Union**, **Intersect**, and **Negate** tools in Studio, you can allow players to use solid modeling operations while inside an experience through `Class.BasePart:UnionAsync()|UnionAsync()`, `Class.BasePart:IntersectAsync()|IntersectAsync()`, and `Class.BasePart:SubtractAsync()|SubtractAsync()`. All of these methods must be called on a `Class.BasePart` and they all require an array of one or more parts to union with, intersect with, or subtract from the calling part.
 
 <Alert severity="warning">
-In-experience solid modeling operations are asynchronous, meaning they can impact performance. For best results, you should not perform a large series of `Class.BasePart:UnionAsync()|UnionAsync()`, `Class.BasePart:IntersectAsync()|IntersectAsync()`, or `Class.BasePart:SubtractAsync()|SubtractAsync()` calls in quick sequence.
+In-experience solid modeling operations are asynchronous, meaning they can impact performance. For best results, you should not perform a large series of `Class.BasePart:UnionAsync()|UnionAsync()`, `Class.BasePart:IntersectAsync()|IntersectAsync()`, or `Class.BasePart:SubtractAsync()|SubtractAsync()` calls in quick succession.
 </Alert>
 
 <Alert severity="info">