@@ -46,7 +46,7 @@ REINDEX { INDEX | TABLE | DATABASE | SYSTEM } <replaceable class="PARAMETER">nam
4646
4747 <listitem>
4848 <para>
49- An index has become <quote>bloated</>, thatit is contains many
49+ An index has become <quote>bloated</>, thatis it contains many
5050 empty or nearly-empty pages. This can occur with B-tree indexes in
5151 <productname>PostgreSQL</productname> under certain uncommon access
5252 patterns. <command>REINDEX</command> provides a way to reduce
@@ -203,7 +203,7 @@ REINDEX { INDEX | TABLE | DATABASE | SYSTEM } <replaceable class="PARAMETER">nam
203203 but not reads of the index's parent table. It also takes an exclusive lock
204204 on the specific index being processed, which will block reads that attempt
205205 to use that index. In contrast, <command>DROP INDEX</> momentarily takes
206- exclusive lock on the parent table, blocking both writes and reads. The
206+ an exclusive lock on the parent table, blocking both writes and reads. The
207207 subsequent <command>CREATE INDEX</> locks out writes but not reads; since
208208 the index is not there, no read will attempt to use it, meaning that there
209209 will be no blocking but reads might be forced into expensive sequential