fix: typos in documentation (#1561)

Co-authored-by: Rootul P <[email protected]>

Author: jasmyhigh

docs/celestia-architecture/adr-001-block-propagation.md

@@ -102,7 +102,7 @@ When a user requests a block from the LL node, the request will be set to the IP
 
 ![user request flow](./assets/user-request.png)
 
-The goal is to not change the public interface for RPC's. It is yet to be seen if this possible. This means that CIDs will need to be set and loaded from the store in order to get all the related block information a user requires.
+The goal is to not change the public interface for RPC's. It is yet to be seen if this is possible. This means that CIDs will need to be set and loaded from the store in order to get all the related block information a user requires.
 
 ## Status
 

docs/celestia-architecture/adr-002-ipld-da-sampling.md

@@ -47,7 +47,7 @@ and [`NodeAdder`](https://github.com/ipfs/go-ipld-format/blob/d2e09424ddee0d7e69
 As an optimization, we can also use a [`Batch`](https://github.com/ipfs/go-ipld-format/blob/d2e09424ddee0d7e696d01143318d32d0fb1ae63/batch.go#L29)
 to batch adding and removing nodes.
 This will be achieved by passing around a [CoreAPI](https://github.com/ipfs/interface-go-ipfs-core/blob/b935dfe5375eac7ea3c65b14b3f9a0242861d0b3/coreapi.go#L15)
-object, which derive from the IPFS node which is created along a with a tendermint node (see [#152]).
+object, which derives from the IPFS node which is created along with a tendermint node (see [#152]).
 This code snippet does exactly that (see the [go-ipfs documentation] for more examples):
 ```go
 // This constructs an IPFS node instance

docs/celestia-architecture/adr-003-application-data-retrieval.md

@@ -7,7 +7,7 @@
 ## Context
 
 This ADR builds on top of [ADR 002](adr-002-ipld-da-sampling.md) and will use the implemented APIs described there.
-The reader should familiarize themselves at least with the high-level concepts the as well as in the [specs](https://github.com/celestiaorg/celestia-specs/blob/master/src/specs/data_structures.md#2d-reed-solomon-encoding-scheme).
+The reader should familiarize themselves at least with the high-level concepts as well as in the [specs](https://github.com/celestiaorg/celestia-specs/blob/master/src/specs/data_structures.md#2d-reed-solomon-encoding-scheme).
 
 The academic [paper](https://arxiv.org/abs/1905.09274) describes the motivation and context for this API.
 The main motivation can be quoted from section 3.3 of that paper:

docs/celestia-architecture/adr-007-minimal-changes-to-tendermint.md

@@ -123,7 +123,7 @@ describe how to hash the block data here:
 - Add PreprocessTxs method to ABCI (https://github.com/celestiaorg/celestia-core/pull/110)
 - Add method to ABCI interface
 - Create sync and async versions
-- Add sync version the the CreateProposalBlock method of BlockExecutor
+- Add sync version to the CreateProposalBlock method of BlockExecutor
 
 #### Fill the DAH while making the block