Skip to content

Commit 708d75e

Browse files
committed
a few more updates
1 parent 5e89b0c commit 708d75e

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

modules/ROOT/pages/configuration/configuration-settings.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2229,7 +2229,7 @@ m|+++block+++
22292229
[frame="topbot", stripes=odd, grid="cols", cols="<1s,<4"]
22302230
|===
22312231
|Description
2232-
a|Relationship count threshold for considering a node to be dense. This setting applies only to `standard`, `aligned`, `high_limit` formats.
2232+
a|Relationship count threshold for considering a node to be dense. This setting applies only to `standard`, `aligned`, and `high_limit` formats.
22332233
|Valid values
22342234
a|An integer that is minimum `1`.
22352235
|Default value

modules/ROOT/pages/database-internals/concurrent-data-access.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -258,7 +258,7 @@ For these additional locks, no assumptions or guarantees can be made concerning
258258
=== Locks for dense nodes
259259

260260
When creating or deleting relationships in Neo4j, dense nodes are not exclusively locked during a transaction.
261-
Rather, internally shared locks prevent the deletion of nodes, and shared degree locks are acquired for synchronizing with concurrent label changes for those nodes to ensure correct count updates.
261+
Rather, internally shared locks prevent the deletion of nodes and shared degree locks are acquired for synchronizing with concurrent label changes for those nodes to ensure correct count updates.
262262

263263
`standard`, `aligned`, and `high_limit` store formats::
264264
A node is considered dense if it, at any point, has had 50 or more relationships.

0 commit comments

Comments
 (0)