diff --git a/articles/what-api-endpoints-to-expose-to-the-public-internet.md b/articles/what-api-endpoints-to-expose-to-the-public-internet.md
index 96c5e535b7..43261a6cb5 100644
--- a/articles/what-api-endpoints-to-expose-to-the-public-internet.md
+++ b/articles/what-api-endpoints-to-expose-to-the-public-internet.md
@@ -15,7 +15,7 @@ If you are using Fleet Desktop and want it to work on remote devices, the bare m
 
 For full Fleet Desktop and scripts functionality, `/api/fleet/orbit/*` and`/api/fleet/device/ping` must also be exposed.
 
-## Using fleetctl CLI from outsite of your network
+## Using fleetctl CLI from outside of your network
 
 If you would like to use the fleetctl CLI from outside of your network, the following endpoints will also need to be exposed for `fleetctl`:
 
@@ -42,4 +42,4 @@ If you would like to use Fleet's MDM features, the following endpoints need to b
 <meta name="authorGitHubUsername" value="mike-j-thomas">
 <meta name="authorFullName" value="Mike Thomas">
 <meta name="publishedOn" value="2023-11-13">
-<meta name="articleTitle" value="Which API endpoints to expose to the public internet?">
\ No newline at end of file
+<meta name="articleTitle" value="Which API endpoints to expose to the public internet?">