docs: change the requirement of connectOrCreate to require @unique (#66) (#68)

* docs: change the requirement of connectOrCreate to require `@unique`

Author: mjfwebb

modules/ROOT/pages/mutations/create.adoc

@@ -111,8 +111,8 @@ Read about xref:mutations/update.adoc#_connectorcreate_relationships[`update`] f
 
 == `connectOrCreate` relationships
 
-If a related node has a `@unique` or `@id` directive defined, `connectOrCreate` can be used in a nested `create` to perform a `MERGE` operation on the related node.
-This should create a new relationship and the related node if it doesn't exist yet.
+If a related node has the `@unique` directive defined, `connectOrCreate` can be used in a nested `create` to perform a `MERGE` operation on the related node.
+This will create a new relationship and the related node if it doesn't exist yet.
 
 Consider the following type definitions:
 
@@ -125,7 +125,7 @@ type Actor {
 
 type Movie {
     title: String
-    id: ID! @id
+    id: ID! @id @unique
     actors: [Actor!]! @relationship(type: "ACTED_IN", direction: IN)
 }
 ----
@@ -163,4 +163,4 @@ The Neo4j GraphQL Library contains an optimization feature designed to mitigate
 
 * A field is populated using the directive `@populated_by`.
 * The `connect` or `connectOrCreate` operation is used.
-* Interface and union types are present in the mutation.
+* Interface and union types are present in the mutation.