Address feedback

Author: fabriziopandini

README.md

@@ -32,17 +32,17 @@ Check out the [getting started guide](./docs/getting_started.md) for launching a
 # CAPV release support
 
 A Cluster API provider vSphere release correspond to a release in the GitHub repository for this project, and the corresponding images published in the Kubernetes docker registry.
-The CAPV release calendar will be aligned as much as possible to the Kubernetes and the Cluster API release release dates plus an offset for 
+The CAPV release calendar will be aligned as much as possible to the Kubernetes and the Cluster API release dates plus an offset for 
 performing test/validation after K8s/CAPI release are available (tentatively one or two weeks after both K8s and CAPI release are available). 
 
 The CAPV team actively supports the latest two minor releases (N, N-1); support in this context means that we:
 
 - Have CI signal with E2E tests, unit tests, CVE scans etc.
 - Accept bug fixes, perform golang or dependency bumps, etc.
-- Periodically cut patch releases
+- Cut patch releases when necessary.
 - On top of supporting the N and N-1 releases, the CAPV team also maintains CI signal for the CAPV N-2 releases in case we have to do an emergency patch release.
 
-If there is a need for an emergency patch, e.g. to fix a critical security issue, please bring this up to maintainers and it will be considered on a case-by-case basis.
+If there is a need for an patch or an emergency patch, e.g. to fix a critical security issue, please bring this up to maintainers and it will be considered on a case-by-case basis.
 
 All considered, each CAPV minor release is supported for a period of roughly 12 months:
 
@@ -61,11 +61,26 @@ The table below documents support matrix for Cluster API provider vSphere versio
 | v1.10.x       | EOL                     | EOL since v1.13.0 release date                                                       |
 | v1.9.x        | EOL                     | EOL since v1.12.0 release date                                                       |
 
-## Compatibility with Cluster API and Kubernetes Versions
+## Compatibility with Cluster API
 
-Compatibility between CAPV releases and Cluster API depends on which Cluster API contract versions supported by CAPI and by which contract version is implemented in CAPV.
+Only a limited set of combinations between releases of CAPV and Cluster API are tested on CI and thus actively
+supported:
 
-CAPV implements following Cluster API contract versions:
+| CAPV version | CAPI version used in CI |
+|--------------|:-----------------------:|
+| CAPV v1.12   |        CAPI v1.9        |
+| CAPV v1.13   |       CAPI v1.10        |
+| CAPV v1.14   |       CAPI v1.11        |
+
+Other CAPV/CAPI version combinations might work, but it is up to the users to validate those combinations; 
+also please be aware that in case of a CAPI/CAPV combination not listed above, support will be provided at best effort.
+
+Following info should be used when identifying possible CAPV/CAPI version combinations outside the table above:
+
+Compatibility between CAPV and Cluster API depends on which Cluster API contract versions is supported by CAPI and by
+which contract version is implemented in CAPV.
+
+The following table documents the Cluster API contract versions implemented by supported CAPV versions:
 
 |            | Cluster API contract version v1beta1 | Cluster API contract version v1beta1 |
 |------------|:------------------------------------:|:------------------------------------:|
@@ -75,14 +90,18 @@ CAPV implements following Cluster API contract versions:
 
 Contract versions supported by Cluster API are documented in the [versions](https://cluster-api.sigs.k8s.io/reference/versions#cluster-api-release-vs-contract-versions) page in the [Cluster API book](https://cluster-api.sigs.k8s.io).
 
-Also, please note that this project is not validating all the permutations between Cluster API versions and CAPV versions;
-below you can find the combinations that are tested in CI:
+Additionally, each version of CAPV requires a specific API version to served by Cluster API, and this
+further reduces the number of valid combinations.
 
-| CAPV version | CAPI version used in CI |
-|--------------|:-----------------------:|
-| CAPV v1.12   |        CAPI v1.9        |
-| CAPV v1.13   |       CAPI v1.10        |
-| CAPV v1.14   |       CAPI v1.11        |
+The table below documents CAPI API version required by supported CAPV versions.
+
+| CAPV version | Requires CAPI API version |
+|--------------|:-------------------------:|
+| CAPV v1.12   |          v1beta1          |
+| CAPV v1.13   |          v1beta1          |
+| CAPV v1.14   |          v1beta2          |
+
+API versions supported by Cluster API are documented in the [versions](https://cluster-api.sigs.k8s.io/reference/versions#cluster-api-release-vs-api-versions) page in the [Cluster API book](https://cluster-api.sigs.k8s.io).
 
 ## Compatibility with Kubernetes Versions