Fixed typos and spelling issues for intro pages

learn/intro/frequently-asked-questions.md

@@ -73,21 +73,21 @@ It is possible to migrate your Charon node to another machine running the same c
 
 Currently, the minimum is 4 operators with a threshold of 3.
 
-The threshold (aka quorum) corresponds to the minimum numbers of operators that need to be active for the validator(s) to be able to perform its duties. It is defined by the following formula `n-(ceil(n/3)-1)`. We strongly recommend using this default threshold in your DKG as it maximises liveness while maintaining BFT safety. Setting a 4 out of 4 cluster for example, would make your validator more vulnerable to going offline instead of less vulnerable. You can check the recommended threshold values for a cluster [here](https://docs.obol.org/learn/intro/key-concepts#distributed-validator-threshold).
+The threshold (aka quorum) corresponds to the minimum number of operators that need to be active for the validator(s) to be able to perform its duties. It is defined by the following formula `n-(ceil(n/3)-1)`. We strongly recommend using this default threshold in your DKG as it maximises liveness while maintaining BFT safety. Setting a 4 out of 4 cluster for example, would make your validator more vulnerable to going offline instead of less vulnerable. You can check the recommended threshold values for a cluster [here](https://docs.obol.org/learn/intro/key-concepts#distributed-validator-threshold).
 
 ### Obol Splits[​](https://docs.obol.org/learn/intro/faq#obol-splits) <a href="#obol-splits" id="obol-splits"></a>
 
 #### What are Obol Splits?[​](https://docs.obol.org/learn/intro/faq#what-are-obol-splits) <a href="#what-are-obol-splits" id="what-are-obol-splits"></a>
 
-Obol Splits refers to a collection of composable smart contracts that enable the splitting of validator rewards and/or principal in a non-custodial, trust-minimised manner. Obol Splits contains integrations to enable DVs within Lido, Eigenlayer, and in future a number of other LSPs.
+Obol Splits refers to a collection of composable smart contracts that enable the splitting of validator rewards and/or principal in a non-custodial, trust-minimised manner. Obol Splits contains integrations to enable DVs within Lido, Eigenlayer, and in the future a number of other LSPs.
 
 #### Are Obol Splits non-custodial?[​](https://docs.obol.org/learn/intro/faq#are-obol-splits-non-custodial) <a href="#are-obol-splits-non-custodial" id="are-obol-splits-non-custodial"></a>
 
 Yes. Unless you were to decide to [deploy an editable splitter contract](https://docs.obol.org/learn/intro/faq#can-i-change-the-percentages-in-a-split), Obol Splits are immutable, non-upgradeable, non-custodial, and oracle-free.
 
 #### Can I change the percentages in a split?[​](https://docs.obol.org/learn/intro/faq#can-i-change-the-percentages-in-a-split) <a href="#can-i-change-the-percentages-in-a-split" id="can-i-change-the-percentages-in-a-split"></a>
 
-Generally Obol Splits are deployed in an immutable fashion, meaning you cannot edit the percentages after deployment. However, if you were to choose to deploy a _controllable_ splitter contract when creating your Split, then yes, the address you select as controller can update the split percentages arbitrarily. A common pattern for this use case is to use a Gnosis SAFE as the controller address for the split, giving a group of entities (usually the operators and principal provider) the ability to update the percentages if need be. A well known example of this pattern is the [Protocol Guild](https://protocol-guild.readthedocs.io/en/latest/03-onchain-architecture.html).
+Generally, Obol Splits are deployed in an immutable fashion, meaning you cannot edit the percentages after deployment. However, if you were to choose to deploy a _controllable_ splitter contract when creating your Split, then yes, the address you select as controller can update the split percentages arbitrarily. A common pattern for this use case is to use a Gnosis SAFE as the controller address for the split, giving a group of entities (usually the operators and principal provider) the ability to update the percentages if need be. A well-known example of this pattern is the [Protocol Guild](https://protocol-guild.readthedocs.io/en/latest/03-onchain-architecture.html).
 
 #### How do Obol Splits work?[​](https://docs.obol.org/learn/intro/faq#how-do-obol-splits-work) <a href="#how-do-obol-splits-work" id="how-do-obol-splits-work"></a>
 
@@ -111,9 +111,9 @@ No. Any address can trigger the contracts to move the funds, they do not need to
 
 #### Are there any edge cases I should be aware of when using Obol Splits?[​](https://docs.obol.org/learn/intro/faq#are-there-any-edge-cases-i-should-be-aware-of-when-using-obol-splits) <a href="#are-there-any-edge-cases-i-should-be-aware-of-when-using-obol-splits" id="are-there-any-edge-cases-i-should-be-aware-of-when-using-obol-splits"></a>
 
-The most important decision is to be aware of whether or not the Split contract you are using has been set up with editability. If a splitter is editable, you should understand what the address that can edit the split does. Is the editor an EOA? Who controls that address? How secure is their seed phrase? Is it a smart contract? What can that contract do? Can the controller contract be upgraded? etc. Generally, the safest thing in Obol's perspective is not to have an editable splitter, and if in future you are unhappy with the configuration, that you exit the validator and create a fresh cluster with new settings that fit your needs.
+The most important decision is to be aware of whether or not the Split contract you are using has been set up with editability. If a splitter is editable, you should understand what the address that can edit the split does. Is the editor an EOA? Who controls that address? How secure is their seed phrase? Is it a smart contract? What can that contract do? Can the controller contract be upgraded? etc. Generally, the safest thing in Obol's perspective is not to have an editable splitter, and if in the future you are unhappy with the configuration, that you exit the validator and create a fresh cluster with new settings that fit your needs.
 
-Another aspect to be aware of is how the splitting of principal from rewards works using the Optimistic Withdrawal Recipient contract. There are edge cases relating to not calling the contracts periodically or ahead of a withdrawal, activating more validators than the contract was configured for, and a worst case mass slashing on the network. Consult the documentation on the contract [here](https://docs.obol.org/learn/intro/obol-splits#optimistic-withdrawal-recipient), its audit [here](https://docs.obol.org/adv/security/smart_contract_audit), and follow up with the core team if you have further questions.
+Another aspect to be aware of is how the splitting of principal from rewards works using the Optimistic Withdrawal Recipient contract. There are edge cases relating to not calling the contracts periodically or ahead of a withdrawal, activating more validators than the contract was configured for, and a worst-case mass slashing on the network. Consult the documentation on the contract [here](https://docs.obol.org/learn/intro/obol-splits#optimistic-withdrawal-recipient), its audit [here](https://docs.obol.org/adv/security/smart_contract_audit), and follow up with the core team if you have further questions.
 
 ### Debugging Errors in Logs[​](https://docs.obol.org/learn/intro/faq#debugging-errors-in-logs) <a href="#debugging-errors-in-logs" id="debugging-errors-in-logs"></a>
 

learn/intro/key-concepts.md

@@ -12,7 +12,7 @@ This page outlines a number of the key concepts behind the various technologies
 
 A distributed validator is an Ethereum proof-of-stake validator that runs on more than one node/machine. This functionality is possible with the use of **Distributed Validator Technology** (DVT).
 
-Distributed validator technology removes some of the single points of failure in validation. Should <33% of the participating nodes in a DV cluster go offline, the remaining active nodes can still come to consensus on what to sign and can produce valid signatures for their staking duties. This is known as Active/Active redundancy, a common pattern for minimizing downtime in mission critical systems.
+Distributed validator technology removes some of the single points of failure in validation. Should <33% of the participating nodes in a DV cluster go offline, the remaining active nodes can still come to consensus on what to sign and can produce valid signatures for their staking duties. This is known as Active/Active redundancy, a common pattern for minimising downtime in mission-critical systems.
 
 ## Distributed Validator Node
 
@@ -26,7 +26,7 @@ In the above example, the stack includes Geth, Lighthouse, Charon and Teku.
 
 <figure><img src="../../.gitbook/assets/image (2) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
-An execution client (formerly known as an Eth1 client) specializes in running the EVM and managing the transaction pool for the Ethereum network. These clients provide execution payloads to consensus clients for inclusion into blocks.
+An execution client (formerly known as an Eth1 client) specialises in running the EVM and managing the transaction pool for the Ethereum network. These clients provide execution payloads to consensus clients for inclusion into blocks.
 
 Examples of execution clients include:
 
@@ -38,7 +38,7 @@ Examples of execution clients include:
 
 <figure><img src="../../.gitbook/assets/image (3) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
-A consensus client's duty is to run the proof of stake consensus layer of Ethereum, often referred to as the beacon chain.
+A consensus client's duty is to run the proof-of-stake consensus layer of Ethereum, often referred to as the beacon chain.
 
 Examples of Consensus clients include:
 
@@ -83,15 +83,15 @@ A distributed validator cluster is a collection of distributed validator nodes c
 
 <figure><img src="../../.gitbook/assets/image (7) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
-A distributed validator key is a group of BLS private keys, that together operate as a threshold key for participating in proof of stake consensus.
+A distributed validator key is a group of BLS private keys which together operate as a threshold key for participating in proof-of-stake consensus.
 
 ### Distributed Validator Key Share
 
 One piece of the distributed validator private key.
 
 ### Distributed Validator Threshold
 
-The number of nodes in a cluster that needs to be online and honest for their distributed validators to be online is outlined in the following table.
+The number of nodes in a cluster that need to be online and honest for their distributed validators to be online is outlined in the following table.
 
 | Cluster Size | Threshold | Note                                          |
 | :----------: | :-------: | --------------------------------------------- |

learn/intro/launchpad.md

@@ -6,15 +6,15 @@ description: A dapp to securely create Distributed Validators alone or with a gr
 
 In order to activate an Ethereum validator, 32 ETH must be deposited into the official deposit contract. Distributed validators are no different.
 
-The vast majority of users that created validators to date have used the [~~**Eth2**~~** Staking Launchpad**](https://launchpad.ethereum.org/), a public good open source website built by the Ethereum Foundation alongside participants who later went on to found Obol. This tool has been wildly successful in the safe and educational creation of a significant number of validators on the Ethereum mainnet.
+The vast majority of users that created validators to date have used the [~~**Eth2**~~** Staking Launchpad**](https://launchpad.ethereum.org/), a public good open-source website built by the Ethereum Foundation alongside participants who later went on to found Obol. This tool has been wildly successful in the safe and educational creation of a significant number of validators on the Ethereum mainnet.
 
-To facilitate the generation of distributed validator keys amongst remote users with high trust, the Obol Network developed and maintains a website that enables a group of users to come together and create these threshold keys: **The DV Launchpad**.
+To facilitate the generation of distributed validator keys amongst remote users with high-trust, the Obol Network developed and maintains a website that enables a group of users to come together and create these threshold keys: **The DV Launchpad**.
 
 <figure><img src="../../.gitbook/assets/image (16) (1) (1).png" alt=""><figcaption></figcaption></figure>
 
 ## Getting started
 
-For more information on running Charon in a UI friendly way through the DV Launchpad, take a look at our [Quickstart Guides](../../run-a-dv/start/quickstart_overview.md).
+For more information on running Charon in a UI-friendly way through the DV Launchpad, take a look at our [Quickstart Guides](../../run-a-dv/start/quickstart_overview.md).
 
 ## DV Launchpad Links
 
@@ -44,6 +44,6 @@ An operator can be part of multiple clusters. Clusters, and cluster invites, are
 
 ## Use the Explorer
 
-Clicking "explore" on the top right of the launchpad brings you to the explorer view. It shows information about every DV cluster and operator being tracked by Obol. You can search for a cluster or operator by name, or filter based on badge or protocol type.
+Clicking "explore" on the top-right of the launchpad brings you to the explorer view. It shows information about every DV cluster and operator being tracked by Obol. You can search for a cluster or operator by name, or filter based on badge or protocol type.
 
 <figure><img src="../../.gitbook/assets/image (19) (1).png" alt=""><figcaption></figcaption></figure>

learn/intro/obol-collective.md

@@ -6,13 +6,13 @@ description: The Obol Collective
 
 ## What is the Obol Collective?
 
-The Obol Collective is the largest Decentralized Operator Ecosystem. We provides the technology, opportunities, and community to scale decentralized infrastructure networks. The list of Obol Collective participants includes 50+ staking protocols, client teams, software tools, education & community projects, professional node operators, home operators, and stakers, including names like EigenLayer, Lido, EtherFi, Figment, Bitcoin Suisse, Stakewise, Nethermind, Blockdaemon, Chorus One, DappNode, and many more. Learn more at [Obol.org](https://obol.org).
+The Obol Collective is the largest Decentralised Operator Ecosystem. We provide the technology, opportunities, and community to scale decentralised infrastructure networks. The list of Obol Collective participants includes 50+ staking protocols, client teams, software tools, education & community projects, professional node operators, home operators, and stakers, including names like EigenLayer, Lido, EtherFi, Figment, Bitcoin Suisse, Stakewise, Nethermind, Blockdaemon, Chorus One, DappNode, and many more. Learn more at [Obol.org](https://obol.org).
 
 <figure><img src="../../.gitbook/assets/DecentralizedOperatorEcosystem.png" alt=""><figcaption></figcaption></figure>
 
 ## Scaling Infrastructure Networks
 
-Obol is focused on scaling consensus by providing permissionless access to Distributed Validators (DVs), which offer not only protection against client issues and key mismanagement, but also byzantine fault tolerance. We believe that distributed validators should and will make up a large portion of mainnet validator configurations, with the transition of the Ethereum community to DVs enabling a new trust paradigm.
+Obol is focused on scaling consensus by providing permissionless access to Distributed Validators (DVs), which offer not only protection against client issues and key mismanagement, but also Byzantine fault tolerance. We believe that distributed validators should and will make up a large portion of mainnet validator configurations, with the transition of the Ethereum community to DVs enabling a new trust paradigm.
 
 The Distributed Validator middleware client, Charon, boosts the security, resilience, and decentralisation of the Ethereum validator network by enabling “squad staking”. The Collective is fueled by Obol’s economic model, which directs funding to ecosystem projects via retroactive funding - a positive flywheel to accelerate adoption of DVs and scale infrastructure networks like Ethereum.
 

learn/intro/obol-incentives.md

@@ -33,7 +33,7 @@ You can participate by:
 
 ### Is existing stake eligible?
 
-* If you are staking yourself directly on Obol DVs and/or Squad Staking, your stake is 100% eligible for rewards. Please note, you must opt into [1% for Decentralization](https://blog.obol.org/1-percent-for-decentralisation/) to qualify for Obol Incentives.
+* If you are staking yourself directly on Obol DVs and/or Squad Staking, your stake is 100% eligible for rewards. Please note, you must opt into [1% for Decentralisation](https://blog.obol.org/1-percent-for-decentralisation/) to qualify for Obol Incentives.
 * If you are staking with a partner protocol, it's best to review the details of that partner at Obol.org/incentives. Only ETH staked on Obol DVs with qualified partners qualify for Obol Incentives and not all partners are created equal.
 
 ***
@@ -97,7 +97,7 @@ Higher effectiveness & uptime = more incentives.
 
 ### Can I withdraw my staked ETH at any time?
 
-Yes, you can withdraw at anytime but you **stop accruing incentives** upon withdrawal.
+Yes, you can withdraw at any time but you **stop accruing incentives** upon withdrawal.
 
 * If you are staking with a partner, they may choose to set penalties for early withdrawals but this is not common.
 * If you are running your own distributed validator, there is no penalty for withdrawing or exiting.