diff --git a/apps/docs/content/troubleshooting/resolving-42p01-relation-does-not-exist-error-W4_9-V.mdx b/apps/docs/content/troubleshooting/resolving-42p01-relation-does-not-exist-error-W4_9-V.mdx
index e2661ae6854..48d7260e8f0 100644
--- a/apps/docs/content/troubleshooting/resolving-42p01-relation-does-not-exist-error-W4_9-V.mdx
+++ b/apps/docs/content/troubleshooting/resolving-42p01-relation-does-not-exist-error-W4_9-V.mdx
@@ -48,7 +48,7 @@ rename to table_name;
 
 ---
 
-### Cause 3: table or function actually does not exist
+### Cause 3: Table or function actually does not exist
 
 One may have never made the table or dropped it deliberately or accidentally. This can be quickly checked with the following query:
 
diff --git a/apps/docs/content/troubleshooting/why-are-there-gaps-in-my-postgres-id-sequence-Frifus.mdx b/apps/docs/content/troubleshooting/why-are-there-gaps-in-my-postgres-id-sequence-Frifus.mdx
index 5bc3e0e6717..83a866c42fc 100644
--- a/apps/docs/content/troubleshooting/why-are-there-gaps-in-my-postgres-id-sequence-Frifus.mdx
+++ b/apps/docs/content/troubleshooting/why-are-there-gaps-in-my-postgres-id-sequence-Frifus.mdx
@@ -20,7 +20,7 @@ It's also important to understand the distinction that sequences guarantee **uni
 
 If you don't know the name of your sequence, it's often formed based on a standard naming convention: table_name_id_seq, where table_name is the name of your table and id is the name of your serial column.
 
-### Common Reasons for Gaps in Sequences
+### Common reasons for gaps in sequences
 
 1. Rollbacks
    One of the most common reasons for a gap is the rollback of a transaction. If you initiate a transaction that includes an insert operation, the sequence responsible for generating the ID for the new row increments. If, for any reason, the transaction doesn't complete successfully—perhaps due to a constraint violation or a deliberate decision to rollback—the insert operation is undone, but the sequence value used is not returned or reused. The documentation explains that as well:
@@ -36,7 +36,7 @@ If you don't know the name of your sequence, it's often formed based on a standa
 4. Upserts
    When an upsert is executed, it can still increase the sequence even if it is set to do nothing on conflicts
 
-### Checking for Gaps
+### Checking for gaps
 
 To check for gaps in the sequence of IDs in a PostgreSQL table, you can use a SQL query that compares the sequence of IDs to a generated series of numbers that spans the same range:
 
@@ -52,7 +52,7 @@ WHERE
 
 This query should help you pinpoint where gaps exist.
 
-### Encountering Errors and Adjusting Sequences
+### Encountering errors and adjusting sequences
 
 In operations involving sequences, you might encounter an error message such as: