some maybe final fixes

Author: JPryce-Aklundh

modules/ROOT/pages/constraints/managing-constraints.adoc

@@ -690,8 +690,9 @@ Added 1 constraint.
 
 ======
 
-[[multiple-constraints]]
-=== Multiple constraints
+[[handling-multiple-constraints]]
+=== Handling multiple constraints
+
 Creating an already existing constraint will fail.
 This includes the following scenarios:
 
@@ -1320,7 +1321,7 @@ CREATE (:Book {isbn: '9780393972832', title: 'Moby Dick'}),
 ----
 
 
-.Create a constraint requiring `Book` nodes to have unique `title` properties, when there already exists two nodes with the same `title`
+.Create a constraint requiring `Book` nodes to have unique `title` properties, when there already exists two `Book` nodes with the same `title`
 [source, cypher, role=test-fail]
 ----
 CREATE CONSTRAINT book_title FOR (book:Book) REQUIRE book.title IS UNIQUE
@@ -1354,8 +1355,7 @@ RETURN book1, book2
 .Create a relationship property existence constraint when conflicting relationships exist
 ======
 
-
-.Create a constraint requiring all `WROTE` relationships to have a `language` property, when there already exists a relationship without a property named `language`
+.Create a constraint requiring all `WROTE` relationships to have a `language` property, when there already exists a `WROTE` relationship without a `language` property
 [source, cypher, role=test-fail]
 ----
 CREATE CONSTRAINT wrote_language FOR ()-[wrote:WROTE]-() REQUIRE wrote.language IS NOT NULL
@@ -1704,7 +1704,8 @@ YIELD name, type, createStatement
 | STRING
 
 | labelsOrTypes
-| The labels or relationship types of this constraint. label:default-output[]
+| The labels or relationship types of this constraint.
+The list returned will only include a single value (the name of the constrained node label or relationship type). label:default-output[]
 | LIST<STRING>
 
 | properties