Clarify CAPI vs CAPI API improvements

Co-authored-by: Lubomir I. Ivanov <[email protected]>

Author: g-gaston

docs/proposals/20240807-in-place-updates.md

@@ -112,7 +112,7 @@ As this proposal is an output of the In-place updates Feature Group, ensuring th
 
 Please note that the practical consequence of focusing on in-place rollout strategies, is that the possibility to implement different types of custom rollout strategies, even if technically possible, won’t be validated in this first iteration (future goal).
 
-Another important point to surface, before digging into implementation details of the proposal, is the fact that this proposal is not tackling the problem of improving CAPI API to embrace all the possibilities that rollout extensions are introducing.
+Another important point to surface, before digging into implementation details of the proposal, is the fact that this proposal is not tackling the problem of improving CAPI to embrace all the possibilities that rollout extensions are introducing.
 
 E.g. If a rollout extension introduces support for in-place updates, using “BootstrapConfig” (emphasis on bootstrap) as the place where most of the machine configurations are defined seems not ideal.