fix: typos in documentation files

src/strategies/hopr-stake-and-balance-qv/utils.ts

@@ -55,7 +55,7 @@ export function getHostedSubgraphUrl(
 }
 
 /**
- * Try to query subgraphs from three differnt endpoints (hosted service, studio for development, studio in production), if applicable
+ * Try to query subgraphs from three different endpoints (hosted service, studio for development, studio in production), if applicable
  * @param hostedSubgraphUrl hosted subgrpah url
  * @param stuidoDevSubgraphUrl development url foro studio subgraph
  * @param studioProdSubgraphUrl production url foro studio subgraph

src/strategies/recusal-list/README.md

@@ -1,7 +1,7 @@
 # recusal-list
 
 This is strategy for disallowing certain address from voting due to conflict of interest or other reasons for recusal.
-You can pass any strategy as an optionnal parameter to combine the recusal with another one.
+You can pass any strategy as an optional parameter to combine the recusal with another one.
 
 Below is an example of parameters. The address list renotes which addresses to restrict. The strategy and its params defines the strategy to use if needed.
 

src/strategies/rep3-badges/README.md

@@ -6,7 +6,7 @@ Using the protocol, DAOs can give various types of badges to their members. Thes
 
 This architecture lets communities track and visualise their member activity and, on the other hand, lets community members build their portfolio of work through on-chain credentials. These naturally have a higher signalling value than more traditional types of portfolios like resumés.
 
-Badges given through the rep3 platform are also fully interoperable with several web3 tools, especially those that are used for gating resources behind a token. These badges, at a contract level, are custom implmentations of ERC-721 tokens. This is a deliberate decision to balance the trade-off between maintaining the integrity of these badges (w.r.t. the work they represent) and permitting key rotation by users.
+Badges given through the rep3 platform are also fully interoperable with several web3 tools, especially those that are used for gating resources behind a token. These badges, at a contract level, are custom implementations of ERC-721 tokens. This is a deliberate decision to balance the trade-off between maintaining the integrity of these badges (w.r.t. the work they represent) and permitting key rotation by users.
 
 The rest of this document details the technical specifications and integration process of our protocol. Please note that this document might be confusing to understand or even have some outdated parts. We are in the process of updating these as we begin to focus on protocol-level integrations in addition to focussing on tool adoption.