rebase

.github/workflows/docs-pr.yml

@@ -7,7 +7,8 @@ name: "Verify PR"
 on:
   pull_request:
     branches:
-    - "4.x"
+    - "main"
+    - "dev"
 
 jobs:
 

.github/workflows/docs-teardown.yml

@@ -4,7 +4,8 @@ name: "Documentation Teardown"
 on:
   pull_request_target:
     branches:
-      - "4.x"
+      - "main"
+      - "dev"
     types:
       - closed
 

modules/ROOT/pages/queries-aggregations/filtering.adoc

@@ -7,14 +7,15 @@ When querying for data, a number of operators are available for different types
 
 == Equality operators
 
-All types can be tested for either equality (`_eq`) or non-equality (`_ne`). 
+All types can be tested for either equality.
+For non-equality, you *must* use the xref:/queries-aggregations/filtering.adoc#_combining_operators[`NOT`] logical operator.
 For example:
 
 .Filtering all Users named John
 [source, graphql, indent=0]
 ----
 query {
-  users(where: {name: { _eq: "John" }})
+  users(where: {name: "John" })
     id
     name
   }
@@ -40,7 +41,7 @@ Here is an example of how to use them:
 [source, graphql, indent=0]
 ----
 query {
-  users(where: {age: { _lt: 50 }}) {
+  users(where: {age_LT: 50 }) {
     id
     name
     age

modules/ROOT/pages/subscriptions/events.adoc

@@ -35,31 +35,6 @@ type Movie {
 }
 ----
 
-Note, however, that only changes made through `@neo4j/graphql` should trigger events. 
-Changes made directly to the database or using the xref::type-definitions/directives/cypher.adoc[`@cypher` directive] will **not** trigger any event.
-
-== `CREATE`
-
-Subscriptions to `CREATE` events listen *only* to newly created nodes, not new relationships.
-In this occasion, a new event is triggered for each new node, containing its properties.
-
-This action is performed with the top-level subscription `[type]Created`, which contains the following fields:
-
-* `event`: the event triggering this subscription (in this case, `CREATE`).
-* `created<typename>`: top-level properties of the newly created node, without relationships.
-* `timestamp`: the timestamp in which the mutation was made.
-If a same query triggers multiple events, they should have the same timestamp.
-
-As an example, consider the following type definitions:
-
-[source,graphql,indent=0]
-----
-type Movie {
-    title: String
-    genre: String
-}
-----
-
 A subscription to any newly created node of the `Movie` type should look like this:
 
 [source,graphql,indent=0]

modules/ROOT/pages/type-definitions/directives/default-values.adoc

@@ -9,7 +9,7 @@ This page describes how to use default values in the Neo4j GraphQL Library.
 [[type-definitions-default-values-default]]
 == `@default`
 
-When generating the input type for the `create`` mutation, the value specified in this directive is used as the default value for this field.
+When generating the input type for the `create` mutation, the value specified in this directive is used as the default value for this field.
 
 === Definition