commit bef99e3f6c73fc5a64e46bc5902de5346f298047
Author: Maciek Sakrejda <m.sakrejda@gmail.com>
Date:   Sun Nov 28 16:43:42 2021 -0800

    Update note on materialized view ORDER BY

diff --git a/doc/src/sgml/ref/refresh_materialized_view.sgml b/doc/src/sgml/ref/refresh_materialized_view.sgml
index 3bf8884447..4aa5558636 100644
--- a/doc/src/sgml/ref/refresh_materialized_view.sgml
+++ b/doc/src/sgml/ref/refresh_materialized_view.sgml
@@ -93,12 +93,10 @@ REFRESH MATERIALIZED VIEW [ CONCURRENTLY ] <replaceable class="parameter">name</
   <title>Notes</title>
 
   <para>
-   While the default index for future
-   <link linkend="sql-cluster"><command>CLUSTER</command></link>
-   operations is retained, <command>REFRESH MATERIALIZED VIEW</command> does not
-   order the generated rows based on this property. If you want the data
-   to be ordered upon generation, you must use an <literal>ORDER BY</literal>
-   clause in the backing query.
+   If there is an <literal>ORDER BY</literal> clause in the materialized view's
+   defining query, the original contents of the materialized view will be ordered
+   that way; but <command>REFRESH MATERIALIZED VIEW</command> does not guarantee
+   to preserve that ordering.
   </para>
  </refsect1>