chore(docs): Minor formatting fixes (#45109)

## I have read the
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
file.

YES

## What kind of change does this PR introduce?

Fixes minor formatting issue and removes extra unneeded quotes


<img width="3738" height="434" alt="Screen Capture 2026-04-22 at 13 31
39@2x"
src="https://github.com/user-attachments/assets/b91313d6-2084-4316-9945-79cf1e810d8e"
/>

<img width="3460" height="1040" alt="Screen Capture 2026-04-22 at 13 32
39@2x"
src="https://github.com/user-attachments/assets/f8d7bd4f-ce9a-4a32-80fc-ecbee6464d8b"
/>


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Documentation**
* Fixed formatting inconsistencies across troubleshooting articles by
standardizing title metadata formatting and improving text readability
in notices and tips sections.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

apps/docs/content/troubleshooting/disk-size-not-shrinking-after-deleting-data-135390.mdx

@@ -1,5 +1,5 @@
 ---
-title = "'Disk size not shrinking after deleting data'"
+title = "Disk size not shrinking after deleting data"
 topics = [ "database", "storage" ]
 keywords = []
 ---

apps/docs/content/troubleshooting/get-detailed-storage-metrics-with-the-aws-cli-587a7d.mdx

@@ -1,5 +1,5 @@
 ---
-title = "'Get detailed Storage metrics with the AWS CLI'"
+title = "Get detailed Storage metrics with the AWS CLI"
 topics = [ "cli", "storage", "studio" ]
 keywords = []
 database_id = "2c33968e-26c0-4613-aee1-5de36d068394"

apps/docs/content/troubleshooting/manually-created-databases-are-not-visible-in-the-supabase-dashboard-4415aa.mdx

@@ -1,5 +1,5 @@
 ---
-title = "'Manually created databases are not visible in the Supabase Dashboard'"
+title = "Manually created databases are not visible in the Supabase Dashboard"
 topics = [ "database"]
 keywords = []
 database_id = "f6420e72-ea67-4825-b3f7-e722ea5c0d96"

apps/docs/content/troubleshooting/otp-verification-failures-token-has-expired-or-otp_expired-errors-5ee4d0.mdx

@@ -1,5 +1,5 @@
 ---
-title = "'OTP Verification Failures: 'token has expired' or 'otp_expired' errors'"
+title = "OTP Verification Failures: 'token has expired' or 'otp_expired' errors"
 topics = [ "auth", "cli" ]
 keywords = []
 database_id = "25eddb73-3cca-485b-b87f-7279dd46b7a7"

apps/docs/content/troubleshooting/rotating-anon-service-and-jwt-secrets-1Jq6yd.mdx

@@ -9,17 +9,13 @@ database_id = "caa72a34-696c-47c6-8976-e50cf7fb396e"
 
 <Admonition type="deprecation">
 
-This troubleshooting guide is about rotating **Legacy anon, service_role API keys**. We are deprecating Legacy
-, and recommend migrating to New API keys. To learn more about API
-keys, refer to [the API documentation](/docs/guides/api/api-keys).
+This troubleshooting guide is about rotating **Legacy anon, service_role API keys**. We are deprecating Legacy, and recommend migrating to New API keys. To learn more about API keys, refer to [the API documentation](/docs/guides/api/api-keys).
 
 </Admonition>
 
 <Admonition type="tip">
 
-Once the JWT secret is regenerated, all current API secrets will be immediately invalidated, and
-all connections using them will be severed. You will need to deploy the new secrets for
-connections to begin working again. You can avoid downtime by migrating to new API Keys.
+Once the JWT secret is regenerated, all current API secrets will be immediately invalidated, and all connections using them will be severed. You will need to deploy the new secrets for connections to begin working again. You can avoid downtime by migrating to new API Keys.
 
 </Admonition>
 

apps/docs/content/troubleshooting/supabase-project-provisioned-via-bolt-not-visible-in-dashboard-7188fc.mdx

@@ -1,5 +1,5 @@
 ---
-title = "'Supabase project provisioned via Bolt not visible in dashboard'"
+title = "Supabase project provisioned via Bolt not visible in dashboard"
 topics = [ "database" ]
 keywords = ["Bolt"]
 database_id = "d64f5f5d-ef80-4423-ba24-1a79b4e69ce6"

apps/docs/content/troubleshooting/supabase-storage-inefficient-folder-operations-and-hierarchical-rls-challenges-b05a4d.mdx

@@ -1,5 +1,5 @@
 ---
-title = "'Supabase Storage: Inefficient folder operations and hierarchical RLS challenges'"
+title = "Supabase Storage: Inefficient folder operations and hierarchical RLS challenges"
 topics = [ "storage" ]
 keywords = []
 database_id = "3b52daf2-d78d-4630-8e9f-8bf5d90208bf"

apps/docs/content/troubleshooting/why-supabase-edge-functions-cannot-provide-static-egress-ips-for-whitelisting-3d78b0.mdx

@@ -1,5 +1,5 @@
 ---
-title = "'Why Supabase Edge Functions cannot provide static egress IPs for allow listing'"
+title = "Why Supabase Edge Functions cannot provide static egress IPs for allow listing"
 topics = [ "auth", "functions", "platform", "self-hosting" ]
 keywords = []
 database_id = "99b56e92-62f2-4602-8e13-d38caf7aff4c"