diff --git a/api-reference/authentication.mdx b/api-reference/authentication.mdx
index 0c3cca9..1ff0d07 100644
--- a/api-reference/authentication.mdx
+++ b/api-reference/authentication.mdx
@@ -17,7 +17,7 @@ Trophy keeps track of and displays when each API key in your account was created
   <img height="200" noZoom src="../assets/api/authentication/api_keys.png" />
 </Frame>
 
-### Anatomy of an API key {#anatomy-of-an-api-key}
+### Anatomy of an API Key {#anatomy-of-an-api-key}
 
 Each API key is made up of 2 parts separated by a period:
 
@@ -44,7 +44,7 @@ curl https://app.trophy.so/api/users/<userId>/metrics/<key> \
 
 If you do not pass an API key, or your API key is invalid, you'll receive a `401` response code.
 
-## Managing API keys {#managing-api-keys}
+## Managing API Keys {#managing-api-keys}
 
 There are a few different operations you can perform on API keys from within your Trophy dashboard to manage your integration.
 
@@ -56,7 +56,7 @@ There are a few different operations you can perform on API keys from within you
   />
 </Frame>
 
-### Rotating keys {#rotating-keys}
+### Rotating Keys {#rotating-keys}
 
 API keys can be rotated if you want to change them for any reason. At the point of rotation, the original API key will no longer function and any requests still using it will begin receiving `401` responses immediately.
 
@@ -64,7 +64,7 @@ API keys can be rotated if you want to change them for any reason. At the point
   Note that when rotating keys, both the prefix and the body will change.
 </Note>
 
-### Revoking keys {#revoking-keys}
+### Revoking Keys {#revoking-keys}
 
 API keys can also be revoked entirely at which point they become _Inactive_. At the point of revocation, the API key will no longer function and any requests still using it will begin receiving `401` responses immediately.
 
@@ -74,7 +74,7 @@ Once revoked you can re-activate the API key at any time.
   Neither the prefix or the body of the key change when revoked or re-activated.
 </Note>
 
-### Deleting API keys {#deleting-api-keys}
+### Deleting API Keys {#deleting-api-keys}
 
 If you're 100% sure you no longer need an API key, they can be deleted.
 
diff --git a/features/points.mdx b/features/points.mdx
index d6c92cc..ec656ba 100644
--- a/features/points.mdx
+++ b/features/points.mdx
@@ -301,7 +301,7 @@ Each level has a threshold. When a user's total points in the system exceeds thi
 
 Use levels for rank tiers, progression UI, reward tiers, or analytics. Trophy keeps each user's current level in sync whenever they earn or lose points in that system.
 
-### Configuring levels {#configuring-levels}
+### Configuring Levels {#configuring-levels}
 
 To set up levels for a points system, open it from the [points page](https://app.trophy.so/points) in the Trophy dashboard and use the levels tab to add or manage levels.
 
@@ -378,7 +378,7 @@ For server-driven notifications (email, push, CRM) that must not depend on the c
 
 This webhook fires when a user’s level changes as a result of earning or losing points, and includes `previousLevel` and `newLevel`.
 
-#### Account-level analytics {#account-level-analytics}
+#### Account-Level Analytics {#account-level-analytics}
 
 The [get level summary API](/api-reference/endpoints/points/get-points-level-summary) returns how many users are currently at each level which is useful for admin dashboards, funnel views, or balancing progression.