Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: Reneta Popova <reneta.popova@neo4j.com>
  • Loading branch information
NataliaIvakina and renetapopova authored Jun 28, 2024
1 parent 3bee258 commit 75501e2
Showing 1 changed file with 14 additions and 14 deletions.
28 changes: 14 additions & 14 deletions modules/ROOT/pages/notifications/all-notifications.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -926,7 +926,7 @@ The home database provided does not currently exist in the DBMS.
This command will not take effect until this database is created. (HOME DATABASE: `nonexistingdatabase`)

Suggestions for improvement::
Make sure the home database has not been misspelled.
Verify that the home database name is not misspelled.

======
[.include-with-GQLSTATUS-code]
Expand All @@ -948,7 +948,7 @@ The database `Ne4j` does not exist.
Verify that the spelling is correct or create the database for the command to take effect.

Suggestions for improvement::
Make sure the home database has not been misspelled.
Verify that the home database name is not misspelled.
======
=====

Expand Down Expand Up @@ -1010,8 +1010,8 @@ Description of the returned code::
One of the labels in your query is not available in the database, make sure you didn't misspell it or that the label is available when you run this statement in your application (the missing label name is: `Perso`)

Suggestions for improvement::
Make sure you didn't misspell the label.
If nodes with the given label will be created in the future, then no change is needed.
Verify that the label is not misspelled.
If you plan to create nodes with that label in the future, then no change is needed.

======
[.include-with-GQLSTATUS-code]
Expand All @@ -1033,8 +1033,8 @@ The label `Perso` does not exist.
Verify that the spelling is correct.

Suggestions for improvement::
Make sure you didn't misspell the label.
If nodes with the given label will be created in the future, then no change is needed.
Verify that the label is not misspelled.
If you plan to create nodes with that label in the future, no change is needed.
======
=====

Expand Down Expand Up @@ -1096,8 +1096,8 @@ One of the relationship types in your query is not available in the database,
make sure you didn't misspell it or that the label is available when you run this statement in your application (the missing relationship type is: `NonExistingType`)

Suggestions for improvement::
Make sure you did not misspell the relationship type.
If relationships will be created, with the given relationship type, in the future, then no change to the query is needed.
Verify that the relationship type is not misspelled.
If you plan to create relationships of this type in the future, no change is needed.

======
[.include-with-GQLSTATUS-code]
Expand All @@ -1118,8 +1118,8 @@ The relationship type `NonExistingType` does not exist.
Verify that the spelling is correct.

Suggestions for improvement::
Make sure you did not misspell the relationship type.
If relationships will be created, with the given relationship type, in the future, then no change to the query is needed.
Verify that the relationship type is not misspelled.
If you plan to create relationships of this type in the future, no change is needed.
======
=====

Expand Down Expand Up @@ -1179,8 +1179,8 @@ One of the property names in your query is not available in the database,
make sure you didn't misspell it or that the label is available when you run this statement in your application (the missing property name is: `nonExistingProp`)

Suggestions for improvement::
Make sure you didn't misspell the property key.
If the property key will be created in the future, then no change is needed to the query.
Verify that the property key is not misspelled.
If you plan to create that property key in the future, no change is needed.

======
[.include-with-GQLSTATUS-code]
Expand All @@ -1202,8 +1202,8 @@ The property `nme` does not exist.
Verify that the spelling is correct.

Suggestions for improvement::
Make sure you didn't misspell the property key.
If the property key will be created in the future, then no change is needed to the query.
Verify that the property key is not misspelled.
If you plan to create that property key in the future, no change is needed.
======
=====

Expand Down

0 comments on commit 75501e2

Please sign in to comment.