diff --git a/doc/modules/ROOT/pages/algorithms/louvain.adoc b/doc/modules/ROOT/pages/algorithms/louvain.adoc index c0e255316e..5d19fde4c5 100644 --- a/doc/modules/ROOT/pages/algorithms/louvain.adoc +++ b/doc/modules/ROOT/pages/algorithms/louvain.adoc @@ -389,7 +389,6 @@ YIELD communityCount, modularity, modularities |=== | communityCount | modularity | modularities | 2 | 0.3571428571428571 | [0.3571428571428571] -|1 row |=== -- @@ -417,7 +416,6 @@ YIELD communityCount, modularity, modularities |=== | communityCount | modularity | modularities | 2 | 0.3571428571428571 | [0.3571428571428571] -|1 row |=== -- diff --git a/doc/modules/ROOT/pages/management-ops/administration.adoc b/doc/modules/ROOT/pages/management-ops/administration.adoc index 4dbcf26167..6ca63a5a6d 100644 --- a/doc/modules/ROOT/pages/management-ops/administration.adoc +++ b/doc/modules/ROOT/pages/management-ops/administration.adoc @@ -35,7 +35,7 @@ GRANT ROLE admin TO carol; ---- As we can see, `alice` and `bob` are standard users with read access to the database. -`carol` is an administrator by virtue of being granted the `admin` role (for more information about this role see the https://neo4j.com/docs/cypher-manual/current/administration/security/administration/#administration-security-administration-introduction[Cypher manual]). +`carol` is an administrator by virtue of being granted the `admin` role (for more information about this role see the https://neo4j.com/docs/operations-manual/current/authentication-authorization/built-in-roles/[Operations manual]). Now `alice` and `bob` each project a few graphs. They both project a graph called `graphA` and `bob` also projects a graph called `graphB`. diff --git a/doc/modules/ROOT/pages/management-ops/graph-creation/index.adoc b/doc/modules/ROOT/pages/management-ops/graph-creation/index.adoc index a2980ea022..84447c232d 100644 --- a/doc/modules/ROOT/pages/management-ops/graph-creation/index.adoc +++ b/doc/modules/ROOT/pages/management-ops/graph-creation/index.adoc @@ -52,7 +52,7 @@ The following table lists the supported property types, as well as their corresp | Double | Float | 64 bit signed | `Double.NaN` | List of Long | List of Integer | - | `null` | List of Double | List of Float | - | `null` -| List of Float | - | `null` +| List of Float | - | - | `null` |=== diff --git a/doc/modules/ROOT/pages/management-ops/graph-export/graph-catalog-apache-arrow-ops.adoc b/doc/modules/ROOT/pages/management-ops/graph-export/graph-catalog-apache-arrow-ops.adoc index bdb68c2b29..9c92084bb3 100644 --- a/doc/modules/ROOT/pages/management-ops/graph-export/graph-catalog-apache-arrow-ops.adoc +++ b/doc/modules/ROOT/pages/management-ops/graph-export/graph-catalog-apache-arrow-ops.adoc @@ -261,7 +261,7 @@ The specific configuration needs to include the following keys: The schema of the result records is identical to the corresponding procedure: .Results -[opts="header",cols="1,1,1,1,1"] +[opts="header",cols="1,1,1"] |=== | sourceNodeId | targetNodeId | relationshipType | 0 | 1 | 0 diff --git a/doc/modules/ROOT/partials/migration/migration-algorithms-node-classification.adoc b/doc/modules/ROOT/partials/migration/migration-algorithms-node-classification.adoc index cfd1aca08e..7e5a0f44f6 100644 --- a/doc/modules/ROOT/partials/migration/migration-algorithms-node-classification.adoc +++ b/doc/modules/ROOT/partials/migration/migration-algorithms-node-classification.adoc @@ -40,7 +40,7 @@ Please see the table below. |=== | 1.x | 2.x | `gds.beta.pipeline.nodeClassification.configureParams` -| | This procedure, which is no longer present, added logistic regression model candidates. Adding logistic regression candidates, can instead be done by calling `gds.beta.pipeline.nodeClassification.addLogisticRegression` one or multiple times. +| This procedure, which is no longer present, added logistic regression model candidates. Adding logistic regression candidates, can instead be done by calling `gds.beta.pipeline.nodeClassification.addLogisticRegression` one or multiple times. |===