Update docs/machine-requests/manual-jwt.mdx

Co-authored-by: Bryce Kalow <[email protected]>
clerk · Feb 7, 2025 · d029ef2 · d029ef2
1 parent 0caaaef
commit d029ef2
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/machine-requests/manual-jwt.mdx b/docs/machine-requests/manual-jwt.mdx
@@ -5,7 +5,7 @@ description: Learn how to manually verify Clerk-generated machine tokens (JWTs).
 
 Your Clerk-generated [machine tokens](/docs/machine-requests/machine-tokens) are JWTs which are signed using your instance's private key and can be verified using your instance's public key.
 
-For every machine request, you must validate the token to ensure it hasn't expired or been tampered with (i.e., it's authentic and secure). Additionally, you likely want to differentiate between machine and user requests. If these validations succeed, then the machine is authenticated to your application.
+For every machine request, you must validate the token to ensure it hasn't expired or been tampered with (i.e., it's authentic and secure). Additionally, you might want to differentiate between machine and user requests within your application. If these validations succeed, then the machine is authenticated and granted access to your application.
 
 > [!TIP]
 > To differentiate between a machine token and user token, the `sub` claim in a machine token starts with `mch_` instead of `user_` on a session token.