post review corrections 4 (main graph types pages)

Author: JPryce-Aklundh

modules/ROOT/pages/schema/graph-types/alter-element-types.adoc

@@ -9,7 +9,7 @@ When altering a graph type, only those node or relationship element types to be
 ====
 Altering element types in a graph type requires the following privileges:
 
-*  link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/database-administration/#access-control-database-administration-constraints[`CREATE CONSTRAINT`]
+* link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/database-administration/#access-control-database-administration-constraints[`CREATE CONSTRAINT`]
 * link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/database-administration/#access-control-database-administration-constraints[`DROP CONSTRAINT`]
 * link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/database-administration/#access-control-database-administration-tokens[`NAME MANAGEMENT`] (if graph type includes node labels, relationship types, or properties not already in the graph)
 ====
@@ -33,7 +33,7 @@ ALTER CURRENT GRAPH TYPE SET {
 ----
 
 [NOTE]
-For details about all the elements included in the above graph type, see xref:schema/graph-types/set-graph-types.adoc[].
+For details about the different elements a graph type can contain, see xref:schema/graph-types/set-graph-types.adoc[].
 
 .Alter node and relationship element types in a graph type
 [source, cypher]
@@ -97,8 +97,6 @@ For more information about how graph types are implemented, see xref:schema/grap
 
 The behavior of key and property uniqueness constraints on identifying node labels and relationship types, as well as constraints on non-identifying node labels and relationship types with regard to the `ALTER CURRENT GRAPH TYPE ALTER` command follows that of xref:schema/constraints/index.adoc[Neo4j constraints]; they can be created and dropped, but they cannot be altered through a single command (they must, in that case, be dropped and recreated to fit the desired alteration).
 
-It is not allowed to add key and property uniqueness constraints to node or relationship element types when altering a graph type. Nor can they be converted into another one through alteration.
-
 It is not allowed to add key and property uniqueness constraints to node or relationship element types when altering a graph type.
 Nor can they be converted into another one through alteration.
 

modules/ROOT/pages/schema/graph-types/drop-graph-type-elements.adoc

@@ -17,11 +17,11 @@ ALTER CURRENT GRAPH TYPE SET {
    (:Robot => :Resident&Machine {application :: STRING NOT NULL, id :: INTEGER NOT NULL}),
    (:City => {name :: STRING NOT NULL, population :: INTEGER}),
    (:Resident)-[:LIVES_IN => {since :: ANY NOT NULL}]->(:City),
-   CONSTRAINT company_name FOR (c:Company) REQUIRE c.name IS KEY,
-   CONSTRAINT resident_address FOR (resident:Resident) REQUIRE resident.address :: STRING,
-   CONSTRAINT ownership_id FOR ()-[owner:OWNER_OF]->() REQUIRE owner.ownershipId IS UNIQUE,
    (:Company => {name :: STRING, address :: STRING IS UNIQUE}),
-   (:Person)-[:WORKS_FOR => {role :: STRING}]->(:Company)
+   (:Person)-[:WORKS_FOR => {role :: STRING}]->(:Company),
+   CONSTRAINT company_name FOR (c:Company) REQUIRE c.name IS KEY,
+   CONSTRAINT animal_id FOR (a:Animal) REQUIRE a.id IS UNIQUE,
+   CONSTRAINT resident_address FOR (resident:Resident) REQUIRE resident.address :: STRING
 }
 ----
 
@@ -124,7 +124,7 @@ The names of constraints are returned by the xref:schema/constraints/list-constr
 [source, cypher]
 ----
 ALTER CURRENT GRAPH TYPE DROP {
-    CONSTRAINT ownership_id,
+    CONSTRAINT animal_id,
     CONSTRAINT constraint_302a3693
 }
 ----

modules/ROOT/pages/schema/graph-types/extend-graph-types.adoc

@@ -9,7 +9,7 @@ This command cannot alter existing elements in a graph type but adds entirely ne
 ====
 Extending a graph type requires the following privileges:
 
-*  link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/database-administration/#access-control-database-administration-constraints[`CREATE CONSTRAINT`]
+* link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/database-administration/#access-control-database-administration-constraints[`CREATE CONSTRAINT`]
 * link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/database-administration/#access-control-database-administration-tokens[`NAME MANAGEMENT`] (if graph type includes node labels, relationship types, or properties not already in the graph)
 ====
 
@@ -30,13 +30,13 @@ ALTER CURRENT GRAPH TYPE SET {
 ----
 
 [NOTE]
-For details about all the elements included in the above graph type, see xref:schema/graph-types/set-graph-types.adoc[].
+For details about the different elements a graph type can contain, see xref:schema/graph-types/set-graph-types.adoc[].
 
 .Extend a graph type by adding new element types
 [source, cypher]
 ----
 ALTER CURRENT GRAPH TYPE ADD {
-    (:Company => {name :: STRING, address :: STRING IS KEY}), // <1>
+    (:Company => {name :: STRING, address :: STRING IS UNIQUE}), // <1>
     (:Person)-[:WORKS_FOR => {role :: STRING}]->(:Company)
 }
 ----
@@ -63,7 +63,7 @@ It is implemented with the following constraints:
 
 | `(:Company)`
 | Node property key
-| `address IS KEY`
+| `address IS UNIQUE`
 
 | `()-[:WORKS_FOR]\->()`
 | Relationship property type
@@ -82,7 +82,7 @@ For more information about how graph types are implemented, see xref:schema/grap
 
 The graph type now includes the added node and relationship element type:
 
-.Set graph type - with added node and relationship element types
+.Current graph type -- with added node and relationship element types
 [source]
 ----
 (p:Person => :Resident {name :: STRING, ssn :: INTEGER})
@@ -119,3 +119,4 @@ This is not valid.
 The reverse (adding a node or relationship element type with an identifying label/type already defined by a property type or property existence constraint) is also not possible.
 <3> This attempts to add a node element type with an identifying label already used as an implied label in a node element type in the existing graph type (`Pet`).
 This is not valid.
+The reverse (adding a node element type with an implied label that is already used as an identifying label in an existing node element type) is also not possible.