review fixes (#11)

fix: MerklLogEntry -> MerkleLogEntry
fix: consistency use 'commit' rather than 'committed eveywhere

AB#8859

Co-authored-by: Robin Bryce <[email protected]>

Author: robinbryce

datatrails-common-api/assets/v2/assets/eventresponse.proto

@@ -174,7 +174,7 @@ message EventResponse {
     // verkle_log. We use oneof to avoid repeating the scattering of randomly
     // re-purposed fields we currently have for simple hash vs khipu.
     oneof proof_details {
-        MerklLogEntry merklelog_entry = 19 [ (grpc.gateway.protoc_gen_openapiv2.options.openapiv2_field) = {
+        MerkleLogEntry merklelog_entry = 19 [ (grpc.gateway.protoc_gen_openapiv2.options.openapiv2_field) = {
             description:
             "verifiable merkle mmr log entry details"
             max_length: 1024

datatrails-common-api/assets/v2/assets/merklelogentry.proto

@@ -36,14 +36,14 @@ message MerkleLogCommitMessage {
 
 
 // The details stored in the SaaS db for a proof mech MERKLE_LOG commitment
-message MerklLogEntry {
+message MerkleLogEntry {
 
     // The tenant log version and epoch when the log entry was created.
     uint32 log_version = 1;
     uint32 log_epoch = 2;
 
     // Event trust level commited fields
-    MerkleLogCommit committed = 3;
+    MerkleLogCommit commit = 3;
 
     // TODO: Event trust level confirmed fields