@@ -612,11 +612,12 @@ Indexes:
612612
613613 <para>
614614 Regular index builds permit other regular index builds on the
615- same table to occur in parallel, but only one concurrent index build
616- can occur on a table at a time. In both cases, no other types of schema
617- modification on the table are allowed meanwhile. Another difference
618- is that a regular <command>CREATE INDEX</command> command can be performed within
619- a transaction block, but <command>CREATE INDEX CONCURRENTLY</command> cannot.
615+ same table to occur simultaneously, but only one concurrent index build
616+ can occur on a table at a time. In either case, schema modification of the
617+ table is not allowed while the index is being built. Another difference is
618+ that a regular <command>CREATE INDEX</command> command can be performed
619+ within a transaction block, but <command>CREATE INDEX CONCURRENTLY</command>
620+ cannot.
620621 </para>
621622 </refsect2>
622623 </refsect1>
@@ -650,7 +651,7 @@ Indexes:
650651 ordering. For example, we might want to sort a complex-number data
651652 type either by absolute value or by real part. We could do this by
652653 defining two operator classes for the data type and then selecting
653- the proper class whenmaking an index. More information about
654+ the proper class whencreating an index. More information about
654655 operator classes is in <xref linkend="indexes-opclass"/> and in <xref
655656 linkend="xindex"/>.
656657 </para>
@@ -668,12 +669,13 @@ Indexes:
668669 will be determined as if no index name had been specified in the
669670 command.
670671 If the <literal>ONLY</literal> option is specified, no recursion
671- is done, and the index is marked invalid
672- (<command>ALTER INDEX ... ATTACH PARTITION</command>turns the index
673- valid, once all partitions acquirethe index .) Note, however, that
674- any partition that is created in the future using
672+ is done, and the index is marked invalid.
673+ (<command>ALTER INDEX ... ATTACH PARTITION</command>marks the index
674+ valid, once all partitions acquirematching indexes .) Note, however,
675+ that any partition that is created in the future using
675676 <command>CREATE TABLE ... PARTITION OF</command> will automatically
676- contain the index regardless of whether this option was specified.
677+ have a matching index, regardless of whether <literal>ONLY</literal> is
678+ specified.
677679 </para>
678680
679681 <para>