Add syntax example for MATCH

modules/ROOT/examples/MATCH.bnf

@@ -0,0 +1,14 @@
+# MATCH clause short
+
+<simple match statement> ::= 
+  "MATCH" <graph pattern>
+
+<graph pattern> ::= 
+  [ <match mode> ] link:/cypher-manual/25/patterns/reference/#path-patterns[<path pattern>] [ { "," link:/cypher-manual/25/patterns/reference/#path-patterns[<path pattern>] }... ] [ <graph pattern where clause> ]
+
+<match mode> ::= 
+    "REPEATABLE" { "ELEMENT" [ "BINDINGS" ] | "ELEMENTS" }
+  | "DIFFERENT" { "RELATIONSHIP" [ "BINDINGS" ] | "RELATIONSHIPS" }
+
+link:/cypher-manual/25/patterns/reference/#path-patterns[<path pattern>] ::= 
+  [ link:/cypher-manual/25/syntax/naming/[<identifier>] "=" ] [ <path pattern prefix> ] <path pattern expression>

modules/ROOT/pages/clauses/match.adoc

@@ -618,3 +618,7 @@ This is because the xref:planning-and-tuning/execution-plans.adoc[Cypher planner
 
 As a result, `MATCH` queries using dynamic values cannot leverage xref:planning-and-tuning/operators/operators-detail.adoc#leaf-operators[index scans or seeks] and must instead use the xref:planning-and-tuning/operators/operators-detail.adoc#query-plan-all-nodes-scan[`AllNodesScan`] operator, which reads all nodes from the node store and is therefore more costly.
 
+== Syntax
+:syntax-filename: match
+
+include::partial$syntax.adoc[]

modules/ROOT/partials/syntax.adoc

@@ -0,0 +1,10 @@
+[source, bnf, subs="+macros"]
+----
+include::example${syntax-filename}.bnf[]
+----
+
+.Railroad diagram
+[%collapsible]
+====
+image::railroad/{syntax-filename}.svg["Railroad diagram for '{syntax-filename}'"]
+====