chore: fix some typos (#151)

docs/design/architecture.md

@@ -26,7 +26,7 @@ The key actors in the Walrus architecture are the following:
   storage nodes being Byzantine) within each storage epoch and across storage epochs.
 
 - All clients and storage nodes operate a blockchain client (specifically on Sui), and mediate
-  payments, resources (space), mapping of shards to storage nodes ,and metadata through blockchain
+  payments, resources (space), mapping of shards to storage nodes, and metadata through blockchain
   smart contracts. Users interact with the blockchain to acquire storage resources and upload
   certificates for stored blobs. Storage nodes listen to the blockchain events to coordinate
   their operations.

docs/dev-guide/dev-operations.md

@@ -70,7 +70,7 @@ may currently be done in 3 different ways:
   used to authenticate the Sui blob object corresponding to the blob ID, and check it is certified,
   before the expiry epoch, and not deletable.
 - A Sui smart contract can read the blob object on Sui (or a reference to it) to check
-  is is certified, before the expiry epoch, and not deletable.
+  it is certified, before the expiry epoch, and not deletable.
 
 The underlying protocol of the
 [Sui light client](https://github.com/MystenLabs/sui/tree/main/crates/sui-light-client)

docs/walrus-sites/overview.md

@@ -125,7 +125,7 @@ worker approach. The steps below all reference the following figure:
   *origin* `dapp.walrus.site`, and makes a SuiNS resolution for `dapp.sui`, obtaining the related
   object ID. Using the object ID, it then fetches the dynamic fields of the object (also checking
   [redirects](./portal.md)). From the dynamic fields, it selects the one for `/index.html`, and
-  extracts its Walrus blob ID and headers (see the [advanced section on headers](./routing.md).
+  extracts its Walrus blob ID and headers (see the [advanced section on headers](./routing.md)).
 - **Blob fetch** (steps 11-14): Given the blob ID, the service worker queries a Walrus aggregator
   for the blob.
 - **Returning the response** (steps 15-16): Now that the service worker has the bytes for

docs/walrus-sites/restrictions.md

@@ -47,7 +47,7 @@ iOS. Therefore, Sui wallets cannot currently be used on a service-worker portal
 however, that *browsing* a Walrus Site is still possible on iOS through any browser.
 
 To provide a seamless experience for iOS users (and other users on browsers that do not support
-service workers), we implemented a redidect to a server-side portal (<https://blob.store>). Whenever
+service workers), we implemented a redirect to a server-side portal (<https://blob.store>). Whenever
 a user on an iOS wallet browses a Walrus Site, the redirect will automatically take them to the
 `<site_name>.blob.store` server-side portal. This way, the user can still use the wallet.