diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml
index 9ed25c05da..283d53e203 100644
--- a/doc/src/sgml/ref/create_table.sgml
+++ b/doc/src/sgml/ref/create_table.sgml
@@ -261,43 +261,43 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI
any existing partition of that parent.
-
-
- Each of the values specified in the partition bound specification is
- a literal, NULL, or UNBOUNDED.
- A literal is either a numeric constant or a string constant that is
- coercable to the corresponding partition key column's type.
-
+
+ Each of the values specified in the partition bound specification is
+ a literal, NULL, or UNBOUNDED.
+ A literal is either a numeric constant or a string constant that is
+ coercible to the corresponding partition key column's type.
+
-
- When creating a range partition, the lower bound specified with
- FROM is an inclusive bound, whereas the upper bound
- specified with TO is an exclusive bound. That is,
- the values specified in the FROM list are accepted
- values of the corresponding partition key columns in a given partition,
- whereas those in the TO list are not. To be precise,
- this applies only to the first of the partition key columns for which
- the corresponding values in the FROM and
- TO lists are not equal. All rows in a given
- partition contain the same values for all preceding columns, equal to
- those specified in FROM and TO
- lists. On the other hand, any subsequent columns are insignificant
- as far as implicit partition constraint is concerned.
+
+ When creating a range partition, the lower bound specified with
+ FROM is an inclusive bound, whereas the upper
+ bound specified with TO is an exclusive bound.
+ That is, the values specified in the FROM list
+ are accepted values of the corresponding partition key columns in a
+ given partition, whereas those in the TO list are
+ not. To be precise, this applies only to the first of the partition
+ key columns for which the corresponding values in the FROM
+ and TO lists are not equal. All rows in a given
+ partition contain the same values for all preceding columns, equal to
+ those specified in FROM and TO
+ lists. On the other hand, any subsequent columns are insignificant
+ as far as implicit partition constraint is concerned.
+
- Specifying UNBOUNDED in FROM
- signifies -infinity as the lower bound of the
- corresponding column, whereas it signifies +infinity
- as the upper bound when specified in TO.
-
+
+ Specifying UNBOUNDED in FROM
+ signifies -infinity as the lower bound of the
+ corresponding column, whereas it signifies +infinity
+ as the upper bound when specified in TO.
+
-
- When creating a list partition, NULL can be specified
- to signify that the partition allows the partition key column to be null.
- However, there cannot be more than one such list partitions for a given
- parent table. NULL cannot specified for range
- partitions.
-
-
+
+ When creating a list partition, NULL can be
+ specified to signify that the partition allows the partition key
+ column to be null. However, there cannot be more than one such
+ list partition for a given parent table. NULL
+ cannot be specified for range partitions.
+
A partition must have the same column names and types as the partitioned