diff --git a/Model/Plugin/ChangeDetector.php b/Model/ChangeDetector.php
similarity index 92%
rename from Model/Plugin/ChangeDetector.php
rename to Model/ChangeDetector.php
index 1877239..1a792c5 100644
--- a/Model/Plugin/ChangeDetector.php
+++ b/Model/ChangeDetector.php
@@ -1,6 +1,6 @@
 <?php
 /**
- * This file is part of Zepgram\ZeroDowntimeDeployment\Model\Plugin
+ * This file is part of Zepgram\ZeroDowntimeDeployment\Model
  *
  * @package    Zepgram\ZeroDowntimeDeployment
  * @file       ChangeDetector.php
@@ -13,7 +13,7 @@
 
 declare(strict_types=1);
 
-namespace Zepgram\ZeroDowntimeDeployment\Model\Plugin;
+namespace Zepgram\ZeroDowntimeDeployment\Model;
 
 use Magento\Deploy\Model\DeploymentConfig\ChangeDetector as MagentoChangeDetector;
 use Magento\Deploy\Model\DeploymentConfig\DataCollector;
diff --git a/README.md b/README.md
index 062247c..026f752 100644
--- a/README.md
+++ b/README.md
@@ -30,9 +30,9 @@ For example:
 
 The mainly steps to reach the ZDD with Magento2:
 1. Start the deployment: green pods are the old one, for now they must stay active while creating blue pods.
+1. You must set your blue pods to a dedicated redis database and keep the green pods on their own redis db (avoiding cache corrupting).
 1. Run `bin/magento setup:upgrade --keep-generated` to upgrade your database.
 1. Upgrading is done: now green pods must be killed and replaced by blue pods based on health check statement.
-1. Even if cache has been already cleared by `bin/magento setup:upgrade` you must clean it again with `bin/magento cache:flush` because old pods may corrupt your cache.
 
 You can find a lot of articles detailling the procedure:
 - https://inviqa.com/blog/how-achieve-zero-downtime-deployments-magento-2
diff --git a/composer.json b/composer.json
index 7ac5ace..21c78e9 100644
--- a/composer.json
+++ b/composer.json
@@ -2,9 +2,10 @@
   "name": "zepgram/module-zero-downtime-deployment",
   "description": "Disable native change detection when Magento2 is on production mode to allow Zero Downtime Deployment (ZDD)",
   "type": "magento2-module",
-  "version": "0.0.1",
+  "version": "0.0.2",
   "require": {
-    "magento/framework": "^101.0.7|^102.0.0"
+    "magento/framework": "^102.0.0",
+    "magento/module-deploy": "^100.2.0"
   },
   "autoload": {
     "files": [
diff --git a/etc/di.xml b/etc/di.xml
index 6b76853..5a40297 100644
--- a/etc/di.xml
+++ b/etc/di.xml
@@ -15,7 +15,7 @@
     <type name="Magento\Deploy\Model\Plugin\ConfigChangeDetector">
         <arguments>
             <argument name="changeDetector" xsi:type="object">
-                Zepgram\ZeroDowntimeDeployment\Model\Plugin\ChangeDetector
+                Zepgram\ZeroDowntimeDeployment\Model\ChangeDetector
             </argument>
         </arguments>
     </type>
diff --git a/etc/module.xml b/etc/module.xml
index 828baf0..acb10c6 100644
--- a/etc/module.xml
+++ b/etc/module.xml
@@ -12,7 +12,7 @@
 -->
 <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:noNamespaceSchemaLocation="urn:magento:framework:Module/etc/module.xsd">
-    <module name="Zepgram_ZeroDowntimeDeployment" setup_version="0.0.1">
+    <module name="Zepgram_ZeroDowntimeDeployment" setup_version="0.0.2">
       <sequence>
         <module name="Magento_Deploy"/>
       </sequence>