v20251218-0003-Fix-some-more-references.patch

From 04043676d10de85fe4c2c7c710066ad440129cb2 Mon Sep 17 00:00:00 2001
From: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Date: Thu, 18 Dec 2025 14:13:02 +0530
Subject: [PATCH v20251218 3/3] Fix some more : references

---
 doc/src/sgml/ddl.sgml | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index 682d51a98c5..6ad3bffd411 100644
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -5859,11 +5859,9 @@ CREATE PROPERTY GRAPH myshop
   <para>
    With this definition, we can write a query like this:
 <programlisting>
-SELECT customer_name FROM GRAPH_TABLE (myshop MATCH (c:customer)-[:has]->(o:"order" WHERE o.ordered_when = current_date) COLUMNS (c.name AS customer_name));
+SELECT customer_name FROM GRAPH_TABLE (myshop MATCH (c IS customer)-[ IS has]->(o IS "order" WHERE o.ordered_when = current_date) COLUMNS (c.name AS customer_name));
 </programlisting>
-   With the new labels and using the colon instead of <literal>IS</literal>,
-   which are equivalent, the <literal>MATCH</literal> clause is now more
-   compact and intuitive.
+   With the new labels the <literal>MATCH</literal> clause is now more intuitive.
   </para>
   <para>
    Please notice that label <literal>order</literal> is quoted. If we run above
@@ -5899,7 +5897,7 @@ CREATE PROPERTY GRAPH myshop
    <literal>employees</literal> table to something, but it is allowed like
    this.)  Then we can run a query like this (incomplete):
 <programlisting>
-SELECT ... FROM GRAPH_TABLE (myshop MATCH (:person WHERE name = '...')-[]->... COLUMNS (...));
+SELECT ... FROM GRAPH_TABLE (myshop MATCH (IS person WHERE name = '...')-[]->... COLUMNS (...));
 </programlisting>
    This would automatically consider both the <literal>customers</literal> and
    the <literal>employees</literal> tables when looking for an edge with the
-- 
2.34.1