Update GQL wording (#1021)

Author: JPryce-Aklundh

modules/ROOT/pages/appendix/gql-conformance/index.adoc

@@ -20,8 +20,8 @@ RETURN m.title
 ----
 
 Cypher supports the majority of mandatory GQL features.
-For a full list, see xref:appendix/gql-conformance/supported-mandatory.adoc[].
-There are, however, currently a few mandatory GQL features not implemented in Cypher.
+For a full list see xref:appendix/gql-conformance/supported-mandatory.adoc[].
+There are, however, currently a few mandatory GQL features not yet in Cypher that Neo4j is actively working towards implementing.
 These are listed in the page xref:appendix/gql-conformance/unsupported-mandatory.adoc[].
 
 Neo4j is also working towards increasing its support of optional GQL features.

modules/ROOT/pages/appendix/gql-conformance/unsupported-mandatory.adoc

@@ -1,7 +1,8 @@
 :description: Information about mandatory GQL features not currently supported by Cypher.
 = Currently unsupported mandatory GQL features
 
-Cypher supports most mandatory GQL features, though there are a few instances where its current functionality diverges.
+Cypher supports most mandatory GQL features.
+There are, however, currently a few mandatory GQL features not yet in Cypher that Neo4j is actively working towards implementing.
 The table below provides an overview of these GQL features and, where applicable, their functional equivalents in Neo4j.
 
 Unlike optional GQL features, mandatory GQL features are not assigned a GQL feature ID code.