Update neo4j-admin-import.adoc

modules/ROOT/pages/tools/neo4j-admin/neo4j-admin-import.adoc

@@ -424,14 +424,12 @@ If you cannot afford a full downtime of your database, split the operation into
 
 * _prepare_ stage (offline)
 * _build_ stage (offline or read-only)
-* _merge_ stagen(offline)
+* _merge_ stage (offline)
 
 The database must be stopped for the `prepare` and `merge` stages.
 During the `build` stage, the database can be left online but put into read-only mode.
 For a detailed example, see <<incremental-import-stages>>.
 
-Note that your database should have correct uniqueness constraints for the affected nodes, but the tool will tell you and exit, if such is missing.
-
 [WARNING]
 ====
 It is highly recommended to back up your database before running the incremental import, as if the _merge_ stage fails, is aborted, or crashes, it may corrupt the database.
@@ -470,6 +468,7 @@ The incremental import command can be used to add:
 [WARNING]
 ====
 Note that you must have node property uniqueness constraints in place for the property key and label combinations that form the primary key, or the uniquely identifiable nodes.
+Otherwise, the command will throw an error and exit.
 For more information, see <<import-tool-header-format>>.
 ====
 * New relationships between existing or new nodes.