@@ -300,19 +300,19 @@ REINDEX [ ( VERBOSE ) ] { INDEX | TABLE | SCHEMA | DATABASE | SYSTEM } [ CONCURR
300300 <orderedlist>
301301 <listitem>
302302 <para>
303- A new temporary index definition is addedinto the catalog
303+ A new temporary index definition is addedto the catalog
304304 <literal>pg_index</literal>. This definition will be used to replace
305305 the old index. A <literal>SHARE UPDATE EXCLUSIVE</literal> lock at
306- session level is taken on the indexes being reindexed as well asits
307- associatedtable to prevent any schema modification while processing.
306+ session level is taken on the indexes being reindexed as well astheir
307+ associatedtables to prevent any schema modification while processing.
308308 </para>
309309 </listitem>
310310
311311 <listitem>
312312 <para>
313313 A first pass to build the index is done for each new index. Once the
314314 index is built, its flag <literal>pg_index.indisready</literal> is
315- switched to <quote>true</quote> to make ready for inserts, making it
315+ switched to <quote>true</quote> to makeit ready for inserts, making it
316316 visible to other sessions once the transaction that performed the build
317317 is finished. This step is done in a separate transaction for each
318318 index.
@@ -322,7 +322,7 @@ REINDEX [ ( VERBOSE ) ] { INDEX | TABLE | SCHEMA | DATABASE | SYSTEM } [ CONCURR
322322 <listitem>
323323 <para>
324324 Then a second pass is performed to add tuples that were added while the
325- first passbuild was running. This step is also done in a separate
325+ first pass was running. This step is also done in a separate
326326 transaction for each index.
327327 </para>
328328 </listitem>
@@ -331,10 +331,10 @@ REINDEX [ ( VERBOSE ) ] { INDEX | TABLE | SCHEMA | DATABASE | SYSTEM } [ CONCURR
331331 <para>
332332 All the constraints that refer to the index are changed to refer to the
333333 new index definition, and the names of the indexes are changed. At
334- this point <literal>pg_index.indisvalid</literal> is switched to
334+ this point, <literal>pg_index.indisvalid</literal> is switched to
335335 <quote>true</quote> for the new index and to <quote>false</quote> for
336- the old, and a cache invalidation is doneso as all the sessions that
337- referenced the old indexare invalidated.
336+ the old, and a cache invalidation is donecausing all sessions that
337+ referenced the old indexto be invalidated.
338338 </para>
339339 </listitem>
340340
@@ -359,8 +359,8 @@ REINDEX [ ( VERBOSE ) ] { INDEX | TABLE | SCHEMA | DATABASE | SYSTEM } [ CONCURR
359359 <para>
360360 If a problem arises while rebuilding the indexes, such as a
361361 uniqueness violation in a unique index, the <command>REINDEX</command>
362- command will fail but leave behind an <quote>invalid</quote> new indexon top
363- of the existing one. This index will be ignored for querying purposes
362+ command will fail but leave behind an <quote>invalid</quote> new indexin addition to
363+ thepre- existing one. This index will be ignored for querying purposes
364364 because it might be incomplete; however it will still consume update
365365 overhead. The <application>psql</application> <command>\d</command> command will report
366366 such an index as <literal>INVALID</literal>:
@@ -387,7 +387,7 @@ Indexes:
387387
388388 <para>
389389 Regular index builds permit other regular index builds on the same table
390- to occurin parallel , but only one concurrent index build can occur on a
390+ to occursimultaneously , but only one concurrent index build can occur on a
391391 table at a time. In both cases, no other types of schema modification on
392392 the table are allowed meanwhile. Another difference is that a regular
393393 <command>REINDEX TABLE</command> or <command>REINDEX INDEX</command>
@@ -406,7 +406,7 @@ Indexes:
406406 concurrently. If such an index is named directly in this command, an
407407 error is raised. If a table or database with exclusion constraint indexes
408408 is reindexed concurrently, those indexes will be skipped. (It is possible
409- to reindex such indexes without theconcurrently option.)
409+ to reindex such indexes without the<command>CONCURRENTLY</command> option.)
410410 </para>
411411 </refsect2>
412412 </refsect1>