commit 0929611f11a3d326383204337359efef1cfed964 (HEAD -> update-index)
Author: Rajakavitha1 <krajakavitha@gmail.com>
Date:   Thu May 19 18:33:04 2022 +0530
diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index d3102a87d9..709039c0f8 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -665,11 +665,14 @@ Indexes:
    <para>
     Another caveat when building a unique index concurrently is that the
     uniqueness constraint is already being enforced against other transactions
-    when the second table scan begins.  This means that constraint violations
+    when the second table scan begins. This means that constraint violations
     could be reported in other queries prior to the index becoming available
-    for use, or even in cases where the index build eventually fails.  Also,
-    if a failure does occur in the second scan, the <quote>invalid</quote> index
-    continues to enforce its uniqueness constraint afterwards.
+    for use, or even in cases where the index build eventually fails. The index
+    is inserted and labeled <quote>invalid</quote> while the index is being built,
+    and then the label is removed if the index builds successfully. If the index does
+    not build successfully, then the label <quote>invalid</quote> remains. Also, if a