diff --git a/adr/adr-001-checkpoint-snarks.md b/adr/adr-001-checkpoint-snarks.md index f245c738..432682ce 100644 --- a/adr/adr-001-checkpoint-snarks.md +++ b/adr/adr-001-checkpoint-snarks.md @@ -256,7 +256,7 @@ pub fn new( } ``` -We also need to implemented a find_and_verify_latest_checkpoint method to scan backwards from the current height to find and verify the latest checkpoint SNARK. +We also need to implement a find_and_verify_latest_checkpoint method to scan backwards from the current height to find and verify the latest checkpoint SNARK. ```rust async fn find_and_verify_latest_checkpoint(&mut self, start: u64, end: u64) -> Result<()> { diff --git a/adr/adr-002-create-account-op.md b/adr/adr-002-create-account-op.md index cb239145..667d3e34 100644 --- a/adr/adr-002-create-account-op.md +++ b/adr/adr-002-create-account-op.md @@ -6,7 +6,7 @@ Once a new user is added to the IMT, we know that all updates to a hashchain are ## Status Quo -The de facto solution to this problem is by centralizing the account creation - a service exists that signs off on an account creation event after a user verifies to the central entity that they own some resource, i.e. a phone number via a OTP. +The de facto solution to this problem is by centralizing the account creation - a service exists that signs off on an account creation event after a user verifies to the central entity that they own some resource, i.e. a phone number via an OTP. This creates cause for concern: diff --git a/adr/adr-003-service-registration.md b/adr/adr-003-service-registration.md index 0ed450ed..851725df 100644 --- a/adr/adr-003-service-registration.md +++ b/adr/adr-003-service-registration.md @@ -90,7 +90,7 @@ pub struct NoteOperationArgs { ``` -This differs from the existing implementation significantly, whose only account source is a SignedBySequencer. Futher adjustments were made to AddKey and RevokeKey to enable hashchain verification using a SignatureBundle as originally intended. +This differs from the existing implementation significantly, whose only account source is a SignedBySequencer. Further adjustments were made to AddKey and RevokeKey to enable hashchain verification using a SignatureBundle as originally intended. ## Effects