diff --git a/cherrypick/README.md b/cherrypick/README.md
index a63016a..f4b599d 100644
--- a/cherrypick/README.md
+++ b/cherrypick/README.md
@@ -97,7 +97,7 @@ final dataBloc = await subScope.resolveAsync<DataBloc>();
 ### Fast Dependency Lookup (Performance Improvement)
 
 > **Performance Note:**  
-> As of the latest version, CherryPick uses a Map-based resolver index for dependency lookup. This means calls to `resolve<T>()` and related methods are now O(1) operations, regardless of the number of modules or bindings in your scope. Previously, the library had to iterate over all modules and bindings to locate the requested dependency, which could impact performance as your project grew.
+> **Starting from version 3.0.0**, CherryPick uses a Map-based resolver index for dependency lookup. This means calls to `resolve<T>()` and related methods are now O(1) operations, regardless of the number of modules or bindings in your scope. Previously, the library had to iterate over all modules and bindings to locate the requested dependency, which could impact performance as your project grew.
 >
 > This optimization is internal and does not change any library APIs or usage patterns, but it significantly improves resolution speed in larger applications.
 
diff --git a/doc/full_tutorial_en.md b/doc/full_tutorial_en.md
index 0ee68d0..03c24b9 100644
--- a/doc/full_tutorial_en.md
+++ b/doc/full_tutorial_en.md
@@ -180,7 +180,7 @@ final service = scope.tryResolve<OptionalService>(); // returns null if not exis
 ### Fast Dependency Lookup (Performance Improvement)
 
 > **Performance Note:**  
-> As of the latest version, CherryPick uses a Map-based resolver index for dependency lookup. This means calls to `resolve<T>()`, `tryResolve<T>()` and similar methods are now O(1) operations, regardless of the number of modules or bindings within your scope. Previously it would iterate over all modules and bindings, which could reduce performance as your project grew. This optimization is internal and does not affect the public API or usage patterns, but significantly improves resolution speed for larger applications.
+> **Starting from version 3.0.0**, CherryPick uses a Map-based resolver index for dependency lookup. This means calls to `resolve<T>()`, `tryResolve<T>()` and similar methods are now O(1) operations, regardless of the number of modules or bindings within your scope. Previously it would iterate over all modules and bindings, which could reduce performance as your project grew. This optimization is internal and does not affect the public API or usage patterns, but significantly improves resolution speed for larger applications.
 
 ---
 
diff --git a/doc/full_tutorial_ru.md b/doc/full_tutorial_ru.md
index c298604..9af1f20 100644
--- a/doc/full_tutorial_ru.md
+++ b/doc/full_tutorial_ru.md
@@ -181,7 +181,7 @@ final service = scope.tryResolve<OptionalService>(); // вернет null, ес
 ### Быстрый поиск зависимостей (Performance Improvement)
 
 > **Примечание по производительности:**  
-> В последних версиях CherryPick для поиска зависимости внутри scope используется Map-индекс. Благодаря этому методы `resolve<T>()`, `tryResolve<T>()` и аналогичные теперь работают за O(1), независимо от количества модулей и биндингов в вашем проекте. Ранее для поиска приходилось перебирать весь список вручную, что могло замедлять работу крупных приложений. Это внутреннее улучшение не меняет внешнего API или паттернов использования, но заметно ускоряет разрешение зависимостей на больших проектах.
+> Начиная с версии **3.0.0**, CherryPick для поиска зависимости внутри scope использует Map-индекс. Благодаря этому методы `resolve<T>()`, `tryResolve<T>()` и аналогичные теперь работают за O(1), независимо от количества модулей и биндингов в вашем проекте. Ранее для поиска приходилось перебирать весь список вручную, что могло замедлять работу крупных приложений. Это внутреннее улучшение не меняет внешнего API или паттернов использования, но заметно ускоряет разрешение зависимостей на больших проектах.
 
 ---