chore: typo fix correction

docs/blog/04_testnet_update.md

@@ -28,7 +28,7 @@ whole.
 
 - Find out how to
   [upload and delete deletable blobs](../usage/client-cli.md#reclaiming-space-via-deletable-blobs)
-  thought the CLI.
+  through the CLI.
 - Find out more about how [delete operations work](../dev-guide/dev-operations.md#delete).
 
 ## Epochs

docs/design/operations-off-chain.md

@@ -66,7 +66,7 @@ The flow is as follows:
   epoch. The storage nodes verify the proof and sign it.
 
 - The storage node who found the inconsistency aggregates the signatures into an inconsistency
-  certificate and sends it to the Walrus smart contract, which verifies it and emits a inconsistent
+  certificate and sends it to the Walrus smart contract, which verifies it and emits an inconsistent
   resource event.
 
 - Upon receiving an inconsistent resource event, correct storage nodes delete sliver data for the

docs/dev-guide/components.md

@@ -23,7 +23,7 @@ Walrus is also composed of a number of Walrus-specific services and binaries:
   [Command Line Interface (CLI)](../usage/client-cli.md), a [JSON API](../usage/json-api.md)
   and an [HTTP API](../usage/web-api.md) to perform Walrus operations.
 - Aggregator services allow reading blobs via HTTP requests.
-- Publisher services are used store blobs to Walrus.
+- Publisher services are used to store blobs to Walrus.
 - A set of storage nodes store encoded blobs. These nodes form the decentralized
   storage infrastructure of Walrus.
 

docs/dev-guide/sui-struct.md

@@ -113,7 +113,7 @@ public struct BlobCertified has copy, drop {
 }
 ```
 
-The `BlobCertified` event with `deletable` set to false and a `end_epoch` in the future indicates
+The `BlobCertified` event with `deletable` set to false and an `end_epoch` in the future indicates
 that the blob will be available until this epoch. A light client proof this event was emitted
 for a blob ID constitutes a proof of availability for the data with this blob ID.
 

docs/usage/troubleshooting.md

@@ -8,7 +8,7 @@ You can enable debug logging for Walrus by setting the environment variable `RUS
 
 Before undertaking any other steps, make sure you have the [latest `walrus`
 binary](./setup.md#installation). If you have multiple versions in different locations, find the
-the binary that will actually be used with `which walrus`.
+binary that will actually be used with `which walrus`.
 
 ## Old hardware or incompatible VMs