Update evaluation methodology for RTL release compliance

Clarified evaluation methodology for Caliptra RTL release compliance.

Author: calebofearth

CaliptraChecklistAndEvaluationMethodology.md

@@ -244,7 +244,7 @@ The following is a consolidated list of all requirements to ensure comprehensive
   * **Evaluation Methodology:** Manufacturers MUST show all changes made to RTL files. Manufacturers MUST show that changes to files in the Integrator RTL modification list are limited to the scope described in those requirements, and MUST show TAC approval for other changes. The [audit tools](https://github.com/chipsalliance/caliptra-rtl/tree/main/tools) can be used to identify changes.
 * **Checklist Item:**
   * **Requirement:** Integrators MUST consume a Caliptra RTL release that is compliant with the versioning compatibility matrix published at [Caliptra Versioning](https://chipsalliance.github.io/caliptra-web/versioning).
-  * **Evaluation Methodology:** Manufacturers MUST identify the Caliptra RTL release consumed by the product and provide evidence that the selected ROM/FMC/Runtime versions are compatible according to the published versioning compatibility matrix.
+  * **Evaluation Methodology:** Manufacturers MUST identify the Caliptra RTL release consumed by the product to demonstrate that it meets the minimum acceptable Major and Minor versions defined in the versioning table. Manufacturers MUST provide evidence that the selected ROM version is compatible according to the published versioning compatibility matrix.
 * **Checklist Item:**
   * **Requirement:** Netlists, layout, and other development collateral derived from the RTL MUST maintain the same behavior as the released RTL when Caliptra is in the [Production Non-Debug state](https://github.com/chipsalliance/Caliptra/blob/main/doc/Caliptra.md#caliptra-security-states).
   * **Evaluation Methodology:** Manufacturers MUST provide evidence that collateral derived from the released RTL has not had its behavior modified.