diff --git a/main/docs/secure/tokens/refresh-tokens/multi-resource-refresh-token.mdx b/main/docs/secure/tokens/refresh-tokens/multi-resource-refresh-token.mdx
index eea4b0eaa..f9234ea68 100644
--- a/main/docs/secure/tokens/refresh-tokens/multi-resource-refresh-token.mdx
+++ b/main/docs/secure/tokens/refresh-tokens/multi-resource-refresh-token.mdx
@@ -25,7 +25,7 @@ When using MRRT, Auth0 merges two sources of authorization to determine what acc
 
 This allows applications to reuse the refresh token not only for APIs requested at login, but also for additional APIs allowed in the MRRT policy.
 
-**T****he key benefits of MRRT include**:
+**The key benefits of MRRT include**:
 
 * A single refresh token, per application, to manage when controlling access to multiple APIs.
 * No need to go through a full <Tooltip tip="Authorization Flow: Authorization grant (or workflow) specified in the OAuth 2.0 framework." cta="View Glossary" href="/docs/glossary?term=authorization+flow">authorization flow</Tooltip> every time your application needs to access a new API.