code · pull · Jul 31, 2026 · Jul 31, 2026 · Jul 31, 2026 · Jul 31, 2026
diff --git a/apps/docs/components/ProjectConfigVariables/ProjectConfigVariables.tsx b/apps/docs/components/ProjectConfigVariables/ProjectConfigVariables.tsx
@@ -474,7 +474,9 @@ function ProjectConfigVariablesInternal({ variable }: { variable: Variable }) {
 
   return (
     <div className="max-w-[min(100%, 500px)] my-6">
-      <h6 className={cn('mt-0 mb-1', 'text-foreground')}>{prettyFormatVariable[variable]}</h6>
+      <span className={cn('block mt-0 mb-1 font-heading font-semibold', 'text-foreground')}>
+        {prettyFormatVariable[variable]}
+      </span>
       <div className="flex flex-wrap gap-x-6">
         <OrgProjectSelector />
         <BranchSelector />

diff --git a/apps/docs/components/StepHikeCompact/index.tsx b/apps/docs/components/StepHikeCompact/index.tsx
@@ -97,7 +97,11 @@ const Details: FC<PropsWithChildren<IDetails>> = ({ children, title, fullWidth =
         fullWidth && 'w-full'
       )}
     >
-      {title && <h3 className="mt-0 text-foreground text-base">{title}</h3>}
+      {title && (
+        <span className="block mt-0 mb-[18px] text-foreground text-base font-heading font-semibold">
+          {title}
+        </span>
+      )}
       {children}
     </div>
   )

diff --git a/apps/docs/content/guides/api/rest/postgrest-error-codes.mdx b/apps/docs/content/guides/api/rest/postgrest-error-codes.mdx
@@ -147,7 +147,7 @@ Data API error unspecified
 
 One can filter for API errors in the [log explorer](/dashboard/project/_/logs/explorer). Below are useful queries for filtering and analyzing API errors:
 
-#### Find all API errors that occurred at the database level
+### Find all API errors that occurred at the database level
 
 ```sql
 select
@@ -171,7 +171,7 @@ order by timestamp desc
 limit 100;
 ```
 
-#### Find specific database error from the data API
+### Find specific database error from the data API
 
 ```sql
 select
@@ -199,7 +199,7 @@ PostgREST error codes are only captured in the logs for projects running V14+. Y
 
 </Admonition>
 
-#### Find specific API error
+### Find specific API error
 
 ```sql
 select
@@ -219,7 +219,7 @@ where
   and regexp_contains(proxy_status, '(?i)THE_RELEVANT_STATUS_CODE');
 ```
 
-#### Count errors per path by hour:
+### Count errors per path by hour:
 
 ```sql
 select
@@ -241,7 +241,7 @@ where status_code >= 300 and regexp_contains(path, '^/rest/v1/')
 group by hour, proxy_status, path;
 ```
 
-#### Find data API request from specific authenticated user
+### Find data API request from specific authenticated user
 
 ```sql
 select

diff --git a/apps/docs/content/guides/auth/oauth-server/getting-started.mdx b/apps/docs/content/guides/auth/oauth-server/getting-started.mdx
@@ -498,7 +498,7 @@ Store the client secret securely. It will only be shown once. If you lose it, yo
 
 </Admonition>
 
-#### Token endpoint authentication method
+### Token endpoint authentication method
 
 When a client exchanges an authorization code or refreshes a token, it must authenticate with the token endpoint. The `token_endpoint_auth_method` controls how this authentication happens:
 

diff --git a/apps/docs/content/guides/database/custom-postgres-config.mdx b/apps/docs/content/guides/database/custom-postgres-config.mdx
@@ -12,7 +12,7 @@ Customizing Postgres configurations provides _advanced_ control over your databa
 
 </Admonition>
 
-### Viewing settings
+## Viewing settings
 
 To list all Postgres settings and their descriptions, run:
 

diff --git a/apps/docs/content/guides/database/drizzle.mdx b/apps/docs/content/guides/database/drizzle.mdx
@@ -6,7 +6,7 @@ breadcrumb: 'ORM Quickstarts'
 hideToc: true
 ---
 
-### Connecting with Drizzle
+## Connecting with Drizzle
 
 [Drizzle ORM](https://github.com/drizzle-team/drizzle-orm) is a TypeScript ORM for SQL databases designed with maximum type safety in mind. You can use their ORM to connect to your database.
 

diff --git a/apps/docs/content/guides/database/extensions.mdx b/apps/docs/content/guides/database/extensions.mdx
@@ -7,7 +7,7 @@ description: 'Using Postgres extensions.'
 Extensions are exactly as they sound - they "extend" the database with functionality which isn't part of the Postgres core.
 Supabase has pre-installed some of the most useful open source extensions.
 
-### Enable and disable extensions
+## Enable and disable extensions
 
 <Tabs
   scrollable
@@ -54,11 +54,11 @@ In addition to the pre-configured extensions, you can also install your own SQL
 
 </Admonition>
 
-### Upgrade extensions
+## Upgrade extensions
 
 If a new version of an extension becomes available on Supabase, you need to initiate a software upgrade in the [Infrastructure Settings](/dashboard/project/_/settings/infrastructure) to access it. Software upgrades can also be initiated by restarting your server in the [General Settings](/dashboard/project/_/settings/general).
 
-### Full list of extensions
+## Full list of extensions
 
 Supabase is pre-configured with over 50 extensions and you can install additional extensions through the [database.dev](https://database.dev/) package manager.
 

diff --git a/apps/docs/content/guides/database/extensions/pgaudit.mdx b/apps/docs/content/guides/database/extensions/pgaudit.mdx
@@ -345,15 +345,15 @@ To prevent PGAudit from monitoring the problematic roles, you'll want to change
 
 ## FAQ
 
-#### Using PGAudit to debug database functions
+### Using PGAudit to debug database functions
 
 Technically yes, but it is not the best approach. It is better to check out our [function debugging guide](/docs/guides/database/functions#general-logging) instead.
 
-#### Downloading database logs
+### Downloading database logs
 
 In the [Logs Dashboard](/dashboard/project/_/logs/postgres-logs) you can download logs as CSVs.
 
-#### Logging observed table rows
+### Logging observed table rows
 
 By default, PGAudit records queries, but not the returned rows. You can modify this behavior with the `pgaudit.log_rows` variable:
 
@@ -367,13 +367,13 @@ alter role "postgres" set pgaudit.log_rows to 'off';
 
 You should not do this unless you are _absolutely_ certain it is necessary for your use case. It can expose sensitive values to your logs that ideally should not be preserved. Furthermore, if done in excess, it can noticeably reduce database performance.
 
-#### Logging function parameters
+### Logging function parameters
 
 We don't currently support configuring `pgaudit.log_parameter` because it may log secrets in encrypted columns if you are using [pgsodium](/docs/guides/database/extensions/pgsodium) or[Vault](/docs/guides/database/vault).
 
 You can upvote this [feature request](https://github.com/orgs/supabase/discussions/20183) with your use-case if you'd like this restriction lifted.
 
-#### Does PGAudit support system wide configurations?
+### Does PGAudit support system wide configurations?
 
 PGAudit allows settings to be applied to 3 different database scopes:
 

diff --git a/apps/docs/content/guides/database/postgres-js.mdx b/apps/docs/content/guides/database/postgres-js.mdx
@@ -6,7 +6,7 @@ breadcrumb: 'ORM Quickstarts'
 hideToc: true
 ---
 
-### Connecting with Postgres.js
+## Connecting with Postgres.js
 
 [Postgres.js](https://github.com/porsager/postgres) is a full-featured Postgres client for Node.js and Deno.
 

diff --git a/apps/docs/content/guides/database/replication/manual-replication-monitoring.mdx b/apps/docs/content/guides/database/replication/manual-replication-monitoring.mdx
@@ -18,9 +18,9 @@ Monitoring replication lag is important and there are 3 ways to do this:
    - pg_stat_replication_replay_lag - lag to replay WAL files from the source DB on the target DB (throttled by disk or high activity)
    - pg_stat_replication_send_lag - lag in sending WAL files from the source DB (a high lag means that the publisher is not being asked to send new WAL files OR network issues)
 
-### Primary
+## Primary
 
-#### Replication status and lag
+### Replication status and lag
 
 The `pg_stat_replication` table shows the status of any replicas connected to the primary database.
 
@@ -29,7 +29,7 @@ select pid, application_name, state, sent_lsn, write_lsn, flush_lsn, replay_lsn,
 from pg_stat_replication;
 ```
 
-#### Replication slot status
+### Replication slot status
 
 A replication slot can be in one of three states:
 
@@ -43,23 +43,23 @@ The state can be checked using the `pg_replication_slots` table:
 select slot_name, active, state from pg_replication_slots;
 ```
 
-#### WAL size
+### WAL size
 
 The WAL size can be checked using the `pg_ls_waldir()` function:
 
 ```sql
 select * from pg_ls_waldir();
 ```
 
-#### Check the LSN
+### Check the LSN
 
 ```sql
 select pg_current_wal_lsn();
 ```
 
-### Subscriber
+## Subscriber
 
-#### Subscription status
+### Subscription status
 
 The `pg_subscription` table shows the status of any subscriptions on a replica and the `pg_subscription_rel` table shows the status of each table within a subscription.
 
@@ -91,7 +91,7 @@ ORDER BY
     table_name;
 ```
 
-#### Check the LSN
+### Check the LSN
 
 ```sql
 select pg_last_wal_replay_lsn();

diff --git a/apps/docs/content/guides/database/replication/manual-replication-setup.mdx b/apps/docs/content/guides/database/replication/manual-replication-setup.mdx
@@ -14,7 +14,7 @@ This guide is for replicating data to destination systems using your own tools.
 
 </Admonition>
 
-### Prerequisites
+## Prerequisites
 
 To set up replication, the following is recommended: