From fbcada2f83cddd7f325a223baf2a5caae0a1529e Mon Sep 17 00:00:00 2001
From: Chris Gwilliams <517923+encima@users.noreply.github.com>
Date: Thu, 9 Jan 2025 08:50:41 +0000
Subject: [PATCH] Update
 apps/docs/content/guides/database/sharding-partitioning.mdx

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
---
 apps/docs/content/guides/database/sharding-partitioning.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/apps/docs/content/guides/database/sharding-partitioning.mdx b/apps/docs/content/guides/database/sharding-partitioning.mdx
index 05e1c233e82..a67a7f3b8e5 100644
--- a/apps/docs/content/guides/database/sharding-partitioning.mdx
+++ b/apps/docs/content/guides/database/sharding-partitioning.mdx
@@ -69,7 +69,7 @@ To move a partition from one shard to another, you can use the following steps:
 
 You can query partitioned tables by querying the parent table or specific partitions.
 
-### Querying the Parent Table
+### Querying the Parent table
 
 When you query the parent table, Postgres automatically routes the query to the relevant partitions based on the conditions specified in the query.