From 40e3606effb20eb697962dadefedae99ceaab0df Mon Sep 17 00:00:00 2001 From: Jose Carlos Montero Gomez Date: Mon, 13 Nov 2023 14:37:50 +0100 Subject: [PATCH] Fix Issue #397: Incorrect Documentation (#399) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0c46c56c9..f4ae0a4e9 100644 --- a/README.md +++ b/README.md @@ -26,7 +26,7 @@ A more detailed description of Uniswap v4 Core can be found in the draft of the - `settle` - `mint` -Only the net balances owed to the pool (negative) or to the user (positive) are tracked throughout the duration of a lock. This is the `delta` field held in the lock state. Any number of actions can be run on the pools, as long as the deltas accumulated during the lock reach 0 by the lock’s release. This lock and call style architecture gives callers maximum flexibility in integrating with the core code. +Only the net balances owed to the pool (positive) or to the user (negative) are tracked throughout the duration of a lock. This is the `delta` field held in the lock state. Any number of actions can be run on the pools, as long as the deltas accumulated during the lock reach 0 by the lock’s release. This lock and call style architecture gives callers maximum flexibility in integrating with the core code. Additionally, a pool may be initialized with a hook contract, that can implement any of the following callbacks in the lifecycle of pool actions: