doc: Fix typos in consensus.md, dao.md, services.md

doc/src/arch/consensus.md

@@ -70,7 +70,7 @@ that, we compute the squared distance of its height target from `MAX_INT`.
 For two honest nodes that mine the next block height of the highest ranking
 fork, their block will have the same rank. To mitigate this tie scenario,
 we also compute the squared distance of the blocks `RandomX` hash from
-`MAX_INT`, allowing us to always chose the actual higher ranking block for
+`MAX_INT`, allowing us to always choose the actual higher ranking block for
 that height, in case of ties. The complete block rank is a tuple containing
 both squared distances.
 

doc/src/arch/dao.md

@@ -172,7 +172,7 @@ represented as arrows $c₁, …, cₖ$.
 
 When making a proposal, we need to prove ownership of a threshold of coins.
 Likewise for voting. Essentially they are similar problems of proving ownership
-of a coin $c$ that is still valid. As showed above this reduces to the following
+of a coin $c$ that is still valid. As shown above this reduces to the following
 statements:
 
 * Is $c$ in the set of all coins $C$?

doc/src/arch/services.md

@@ -156,7 +156,7 @@ impl Child {
 ```
 
 Otherwise if the relationship is just one way, use `Arc<Foo>`. For example if doing dependency
-injection where component B dependent on component A, then we could do:
+injection where component B is dependent on component A, then we could do:
 
 ```rust
 let comp_a = Foo::new();