chore: fix some typos in comment

Signed-off-by: depthlending <[email protected]>
matter-labs · Dec 11, 2024 · 60ed202 · 60ed202
1 parent 0b1a667
commit 60ed202
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/packages/app/README.md b/packages/app/README.md
@@ -113,4 +113,4 @@ GitHub Actions test results are available in:
 - Inside of each test run in the log: `Feature on Mainnet + Sepolia` --> `@search` --> `Upload test results to Allure reporter` --> `https://raw.githack.com/matter-labs/block-explorer/gh-pages/_github.run_number_/index.html`
 - Directly via a link `https://raw.githack.com/matter-labs/block-explorer/gh-pages/_github.run_number_/index.html` after each PR running. The history of test runs for public view locates in `gh-pages` branch.
 
-In case of 404 page, make sure that the folder with its `github.run_number` exists in the `gh-pages`. If the folder exist, try again in a few minutes as `https://raw.githack.com` needs to update the data. Public report link will be available when the 'Allure Report' job will be succesfully executed.
+In case of 404 page, make sure that the folder with its `github.run_number` exists in the `gh-pages`. If the folder exist, try again in a few minutes as `https://raw.githack.com` needs to update the data. Public report link will be available when the 'Allure Report' job will be successfully executed.
diff --git a/packages/worker/diagrams/batches-processing.flow.md b/packages/worker/diagrams/batches-processing.flow.md
@@ -10,7 +10,7 @@ flowchart
   GetLastBatchFromDB --> SetLastDBBatch(Set lastProcessedBatchNumber variable with last batch number from DB)
   CheckIfLastProcessedBatchNumberIsNull --> |No| GetNextBatchFromBlockchain
   SetLastDBBatch --> GetNextBatchFromBlockchain("Get the next batch from blockchain (lastProcessedBatchNumber + 1)")
-  GetNextBatchFromBlockchain --> CheckIfRequestSuccessful{Is request sucessful ?}
+  GetNextBatchFromBlockchain --> CheckIfRequestSuccessful{Is request successful ?}
   CheckIfRequestSuccessful --> |No| ResetLastDBBatch(Set lastProcessedBatchNumber = NULL)
   CheckIfRequestSuccessful --> |Yes| CheckIfBatchExists{Does the next batch exist ?}
   CheckIfBatchExists --> |No| ResetLastDBBatch(Set lastProcessedBatchNumber = NULL)
@@ -28,6 +28,6 @@ Batch state is defined and used only internally. There are 4 batch states: `Exec
 - `Executed` - batch has `executeTxHash` and `executedAt`.
 - `Proven` - batch has `proveTxHash` and `provenAt`.
 - `Committed` - batch has `commitTxHash` and `committedAt`.
-- `New` - batch does't have any of `executeTxHash`, `proveTxHash` or `commitTxHash`.
+- `New` - batch doesn't have any of `executeTxHash`, `proveTxHash` or `commitTxHash`.
 
 Note, each `Executed` batch is also `Proven` and `Committed`, each `Proven` batch is also `Committed`.