Address Comments on Device Identity Provisioning

Signed-off-by: Fabrizio Damato <fabrizio.damato@amd.com>

Author: fdamato

specifications/device-identity-provisioning/spec.ocp

@@ -394,7 +394,7 @@ In this specification, a "slot" refers to a storage location within the device t
 
 - **SPDM context**: SPDM defines 8 possible slots (0-7) where certificate chains can be stored. When an SPDM requester invokes `GET_CERTIFICATE`, they specify which slot's certificate chain they want to retrieve.
 
-- **Attestation context**: During attestation, the device uses these certificate chains to establish trust. For example, when generating an EAT, the device may include a LEAF certificate that chains to one of the certificates stored in these slots. The verifier can then retrieve the appropriate certificate chain to validate the complete trust path.
+- **Attestation context**: During attestation, the device uses these certificate chains to establish trust. For example, when generating Evidence, the device may include a LEAF certificate that chains to one of the certificates stored in these slots. The verifier can then retrieve the appropriate certificate chain to validate the complete trust path.
 
 - **OCP abstraction**: While SPDM uses numeric slot IDs (0-7), the OCP commands abstract this using Key Provisioning Entity identifiers (VENDOR, OWNER, TENANT). The device internally maps these entities to specific slot numbers, which can be discovered via `OCP_GET_SLOT_ID_MAPPING`.
 
@@ -574,14 +574,12 @@ Table: GET_ENDORSEMENT VendorDefinedRespPayload {#tbl:get-endorsement-resp}
 | 1      | CommandCode             | 1                       | Shall be 05h to indicate                 |
 |        |                         |                         | GET_ENDORSEMENT.                         |
 +--------+-------------------------+-------------------------+------------------------------------------+
-| 2      | Reserved                | 4                       | Reserved.                                |
-+--------+-------------------------+-------------------------+------------------------------------------+
-| 6      | Reserved                | 1                       | Reserved.                                |
+| 2      | Reserved                | 2                       | Reserved.                                |
 +--------+-------------------------+-------------------------+------------------------------------------+
-| 7      | CertChainLength         | 2                       | Length of the certificate chain.         |
+| 4      | CertChainLength         | 2                       | Length of the certificate chain.         |
 |        |                         |                         | Zero if status is not success.           |
 +--------+-------------------------+-------------------------+------------------------------------------+
-| 9      | CertChain               | CertChainLength         | DER-encoded certificate chain.           |
+| 6      | CertChain               | CertChainLength         | DER-encoded certificate chain.           |
 |        |                         |                         | Does NOT include LEAF certificate.       |
 |        |                         |                         | Present only if status is success.       |
 +--------+-------------------------+-------------------------+------------------------------------------+
@@ -604,9 +602,9 @@ For SPDM-aware implementations:
 For devices that support both SPDM and OCP attestation paths:
 
 - `OCP_SET_ENDORSEMENT` internally manages slot allocation based on the KeyProvisioningEntity
-- `OCP_GET_ENDORSEMENT` retrieves endorsements by entity rather than slot number
+- `OCP_GET_ENDORSEMENT` retrieves endorsements by KeyProvisioningEntity rather than slot number
 - `GET_CERTIFICATE` (SPDM) can still be used with the slot numbers reported by `OCP_GET_SLOT_ID_MAPPING`
-- The device ensures consistency between OCP entity-based and SPDM slot-based access
+- The device ensures consistency between OCP KeyProvisioningEntity and SPDM slot-based access
 
 This approach simplifies the interface by abstracting slot management while maintaining full compatibility with SPDM.