Address feedback

Author: fabriziopandini

docs/proposals/20250124-From CAPD(docker) to CAPD(dev) .md

@@ -57,15 +57,15 @@ capable to support multiple backends including docker, in-memory, may be also ku
 
 The transition will happen in two phases:
 
-In phase 1, targeting CAPI 1.1 (current release cycle), two new kinds will be introduced in CAPD: `DevCluster` and `DevMachine`
+In phase 1, targeting CAPI 1.10 (current release cycle), three new kinds will be introduced in CAPD: `DevCluster`, `DevMachine` and `DevMachinePool`.
 
-`DevCluster` and `DevMachine` will have 
-- A `docker` backend, functionally equivalent to `DockerCluster` and `DockerMachine`
-- An `inMemory`, functionally equivalent to CAPIM's `InMemoryCluster` and `InMemoryMachine`
+`DevCluster`, `DevMachine` and `DevMachinePool` will have 
+- A `docker` backend, functionally equivalent to `DockerCluster`, `DockerMachine` and `DockerMachinePool`.
+- An `inMemory` backend, functionally equivalent to CAPIM's `InMemoryCluster` and `InMemoryMachine` (there is no `InMemoryMachinePool`).
 - if and when Maintainers of CAPK(Kubemark) will choose to converge to CAPD(dev), a `kubemark` backend,  
-  functionally equivalent to `KubemarkMachine` (there is no `KubemarkCluster`)
+  functionally equivalent to `KubemarkMachine` (there is no `KubemarkCluster` nor a `KubemarkMachinePool`).
 
-Below you can fin an example of `DockerCluster` and corresponding `DevMachine` using the docker backend:
+Below you can find an example of `DockerMachine` and corresponding `DevMachine` using the docker backend:
 
 ```yaml
 apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
@@ -146,14 +146,14 @@ spec:
 ```
 
 Please note that at the end of phase 1
-- `DockerCluster` and `DockerMachine` will continue to exist, thus allowing maintainers and users 
+- `DockerCluster`, `DockerMachine` and `DockerMachinePool` will continue to exist, thus allowing maintainers and users 
   time to migrate progressively to the new kinds; however, it is important to notice that
-  `DockerCluster` and `DockerMachine` should be considered as deprecated from now on.
-- `InMemoryCluster` and `InMemoryMachine` will be removed, as well as the entire CAPIM provider.
-  (CAPIM is used only for CAPI scale tests, so users are not impacted and migration can be executed faster).
+  `DockerCluster`, `DockerMachine` and `DockerMachinePool` should be considered as deprecated from now on.
+- `InMemoryCluster` and `InMemoryMachine` will be removed immediately, as well as the entire CAPIM provider.
+  (CAPIM is used only for CAPI scale tests, so users are not/less impacted and migration can be executed faster).
 
-Phase 2 consist of the actual removal of `DockerCluster` and `DockerMachine`; this phase will happen after maintainers 
-will complete the transition of all the E2E tests to `DevCluster` and `DevMachine`; considering we have upgrade tests using
+Phase 2 consist of the actual removal of `DockerCluster`, `DockerMachine` and `DockerMachinePool`; this phase will happen after maintainers 
+will complete the transition of all the E2E tests to `DevCluster`, `DevMachine` and `DevMachinePool`; considering we have upgrade tests using
 older releases of CAPD, completing this phase would likely require a few release cycles, targeting tentatively CAPI 1.13, Apr 2026.
 
 ## Implementation History