From dc75c7297155d3c14fe197ab6fe7cf4303573f88 Mon Sep 17 00:00:00 2001
From: Drew Baker <89049099+Drew-P-drawers@users.noreply.github.com>
Date: Fri, 18 Apr 2025 16:11:46 -0400
Subject: [PATCH] Update deploying-sentinelone-with-fleet.md (#28386)

---
 articles/deploying-sentinelone-with-fleet.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/articles/deploying-sentinelone-with-fleet.md b/articles/deploying-sentinelone-with-fleet.md
index 3b8324cb79..9309a5b12b 100644
--- a/articles/deploying-sentinelone-with-fleet.md
+++ b/articles/deploying-sentinelone-with-fleet.md
@@ -10,7 +10,7 @@ SentinelOne is a cybersecurity platform that provides endpoint protection, detec
 
 SentinelOne requires 5 separate mobileconfig files in order to properly function on macOS. Each of these serves an important operational function. These 5 profiles are available to download on my GitHub repo [here](https://github.com/harrisonravazzolo/Bluth-Company-GitOps/tree/main/lib/macos/SentinelOne). Let's quickly run through each one and highlight what it's actually doing on your endpoints.
 
-> It's possible these profiles can be combined into one payload, but we've kept them seperate here for troubleshooting purposes.
+> It's possible these profiles can be combined into one payload, but we've kept them separate here for troubleshooting purposes.
 
 `s1_install_token.mobileconfig` - The simplest of the payloads. Find the key S1InstallRegistrationToken and replace the corresponding string value with your site token. This token can be found under the Sentinels tab for the corresponding site where you want to enroll your hosts.