Merge pull request #5483 from EnterpriseDB/docs/edits_to_pgd_pr5384

Edits to PGD PR5384

product_docs/docs/pgd/5/scaling.mdx

@@ -28,7 +28,7 @@ PGD Autopartition in PGD 5.5 and later leverages underlying Postgres features th
 partition to be attached or detached/dropped without locking the rest of the
 table. Versions of PGD prior to 5.5 don't support this feature and will lock the tables.
 
-An ERROR is raised if the table isn't RANGE partitioned or a multi-column
+An error is raised if the table isn't RANGE partitioned or a multi-column
 partition key is used.
 
 By default, AutoPartition manages partitions globally. In other words, when a
@@ -59,7 +59,7 @@ managed by AutoPartition. Doing so can make the AutoPartition metadata
 inconsistent and might cause it to fail.
 
 
-## AutoPartition Examples
+## AutoPartition examples
 
 Daily partitions, keep data for one month:
 
@@ -176,12 +176,13 @@ function to find the partition for the given partition key value. If partition
 to hold that value doesn't exist, then the function returns NULL. Otherwise Oid
 of the partition is returned.
 
-## Enabling or disabling AutoPartitioning
+## Enabling or disabling autopartitioning
 
 Use
 [`bdr.autopartition_enable()`](/pgd/latest/reference/autopartition#bdrautopartition_enable)
-to enable AutoPartitioning on the given table. If AutoPartitioning is already
+to enable autopartitioning on the given table. If autopartitioning is already
 enabled, then no action occurs. Similarly, use
 [`bdr.autopartition_disable()`](/pgd/latest/reference/autopartition#bdrautopartition_disable)
-to disable AutoPartitioning on the given table.
+to disable autopartitioning on the given table.
+