diff --git a/apps/www/_blog/2023-04-13-supabase-auth-sso-pkce.mdx b/apps/www/_blog/2023-04-13-supabase-auth-sso-pkce.mdx
index d86be5f7a5a..3979a97c4c4 100644
--- a/apps/www/_blog/2023-04-13-supabase-auth-sso-pkce.mdx
+++ b/apps/www/_blog/2023-04-13-supabase-auth-sso-pkce.mdx
@@ -72,7 +72,7 @@ Many developers today are using Supabase to build mobile apps, and server-side r
 
 ### A brief history of Supabase Auth
 
-When we [launched](https://news.ycombinator.com/item?id=24072051) Supabase Auth, our target was JAMstack developers. In these cases, the protocol used between the user's application and Supabase Auth is known as the **\*\*\*\***\*\*\***\*\*\*\***[Implicit Grant Flow](https://www.rfc-editor.org/rfc/rfc6749#section-4.2):\*
+When we [launched](https://news.ycombinator.com/item?id=24072051) Supabase Auth, our target was JAMstack developers. In these cases, the protocol used between the user's application and Supabase Auth is known as the [Implicit Grant Flow](https://www.rfc-editor.org/rfc/rfc6749#section-4.2):
 
 <img
   className="dark:hidden !m-0"
@@ -101,7 +101,7 @@ Server-side auth unlocks a number of benefits. Developers can:
 
 ### Introducing PKCE
 
-To solve these problems, we're introducing support for the _Proof Key for Code Exchange_ flow \*_(PKCE, pronounced “pixy”)_.\*
+To solve these problems, we're introducing support for the _Proof Key for Code Exchange_ flow (PKCE, pronounced “pixy”).
 
 The PKCE flow introduces a _code verifier_ (a randomly generated secret) and a _code challenge_ (the hash of the _code verifier_). The authorization code is returned as a query parameter so it's accessible on the server. During the PKCE flow: