General improvements

docs/contributing/documentation/writing-style-guide.md

@@ -114,7 +114,7 @@ The examples below use dollars, but the same rules apply to all global currencie
 
 - When directly referring to the creation, destruction, or manipulation of a token (particularly as it relates to tooling) or when referencing the token as a currency, in an instructional or conversational setting, or as a conceptual product of the Foundation or its systems:
   - Use the proper prefix if necessary and capitalized TLA version: `wETH`
-  - **Example:** “wETH is a token that represents Ether 1:1 and conforms to the ERC20 token standard.”
+  - **Example:** “wETH is a token that represents Ether 1:1 and conforms to the ERC-20 token standard.”
 - Similarly, when referring to exchange pairs:
   - Use: `wETH/DAI`
 

docs/contributing/governance/governance-and-operations.md

@@ -8,7 +8,7 @@ Multi-DAO refers to the fluid number of decentralized autonomous organizations (
 
 - **YFI holders** vote for changes to the protocol or the governance structure
 - **yTeams** focus on specific aspects of the protocol or relevant operations
-- **Multisig** members execute or veto any on-chain decisions
+- **Multisig** members execute or veto any onchain decisions
 
 Token holders have an ultimate say over what yTeams exist, who is part of the Multisig, and the limitations of each group's operational control. The term 'constrained delegation' originates from token holders delegating specific powers to various groups building and managing yearn.
 
@@ -81,11 +81,11 @@ Each yTeam is assigned specific decision-making powers, defined by YIP-61:
 
 ### Multisig
 
-Decisions issued by yTeams will be executed on-chain by the Multisig until a more decentralized system is approved for implementation. In the meantime, the [Multisig](/developers/security/multisig#members) controls the following:
+Decisions issued by yTeams will be executed onchain by the Multisig until a more decentralized system is approved for implementation. In the meantime, the [Multisig](/developers/security/multisig#members) controls the following:
 
 | Power               | Description                                                                                                                                           |
 | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Execution Power     | The power to execute decisions made by YFI holders and yTeams on-chain                                                                                |
+| Execution Power     | The power to execute decisions made by YFI holders and yTeams onchain                                                                                |
 | Veto Power          | This power allows the Multisig to veto any decision and ideally should not be needed                                                                  |
 | Transitionary Power | A temporary power enabling the Multisig to operate under the mandate of YIP-41 until the set of decision-making powers covers all needed transactions |
 
@@ -94,7 +94,7 @@ Decisions issued by yTeams will be executed on-chain by the Multisig until a mor
 Yearn continuously paves the way towards an ideal balance of DAO decentralization and productivity. The current phase of efforts implements changes mainly on the social layer. In the future, we will be moving towards software implementations such as:
 
 - Multisig consensus mechanisms that allow each yTeam to have execution power
-- Move from proxy voting to on-chain voting
+- Move from proxy voting to onchain voting
 - tokenize decision-making powers as NFTs
 - Utilize [Coordinape](https://coordinape.com/) for things like budget allocation and compensation
 

docs/contributing/governance/proposal-process.md

@@ -1,6 +1,6 @@
 # Proposal Process
 
-[veYFI](/contributing/governance/veyfi) token holders control the Yearn ecosystem through off-chain proposals and votes via [Snapshot](https://snapshot.org/#/s:veyfi.eth). Proposals that generate majority support (>50% of the vote) are implemented by a 9-member multi-signature wallet, and 6 out of 9 wallet signers must sign for a change to be implemented. The [members of the multi-signature wallet](/developers/security/multisig#members) were voted in by YFI holders and are subject to change from future governance votes.
+[veYFI](/contributing/governance/veyfi) token holders control the Yearn ecosystem through offchain proposals and votes via [Snapshot](https://snapshot.org/#/s:veyfi.eth). Proposals that generate majority support (>50% of the vote) are implemented by a 9-member multi-signature wallet, and 6 out of 9 wallet signers must sign for a change to be implemented. The [members of the multi-signature wallet](/developers/security/multisig#members) were voted in by YFI holders and are subject to change from future governance votes.
 
 ## Discussion
 
@@ -34,7 +34,7 @@ Getting as much feedback as possible from the various communication channels is
 
 ### Making a proposal
 
-Anyone can post a proposal on the forum for discussion within the community. If it's promoted to off-chain votation (via [Snapshot](https://snapshot.org/#/ybaby.eth)), only someone holding 1 veYFI can submit it to Snapshot. If your proposal made it to off-chain votation and you don't have enough veYFI, mods will help you through this stage.
+Anyone can post a proposal on the forum for discussion within the community. If it's promoted to offchain votation (via [Snapshot](https://snapshot.org/#/ybaby.eth)), only someone holding 1 veYFI can submit it to Snapshot. If your proposal made it to offchain votation and you don't have enough veYFI, mods will help you through this stage.
 
 The default template for proposals can be found on [GitHub](https://github.com/yearn/YIPS/blob/master/yip-X.md) + on the [forum](https://gov.yearn.fi), if you post under "proposals" or "discussion" it will auto-fill in the template as well.
 
@@ -51,9 +51,9 @@ The default template for proposals can be found on [GitHub](https://github.com/y
 
 - Holding [veYFI](/contributing/governance/veyfi) enables you to vote on Yearn's [Snapshot](https://snapshot.org/#/ybaby.eth) page
 
-#### What’s the difference between voting for a poll on the forum and an off-chain vote?
+#### What’s the difference between voting for a poll on the forum and an offchain vote?
 
-- A poll gauges the sentiment of what the community is feeling on the proposal while an off-chain vote (via [Snapshot](https://snapshot.org/#/ybaby.eth)) will be binding and will take effect if it passes.
+- A poll gauges the sentiment of what the community is feeling on the proposal while an offchain vote (via [Snapshot](https://snapshot.org/#/ybaby.eth)) will be binding and will take effect if it passes.
 
 ## Implementation
 

docs/contributing/governance/veYFI-comp-summary.md

@@ -1,10 +1,10 @@
 ---
-rpcCalls:  
+rpcCalls:
   - name: 'dYFI Redemption'
     chain: '1'
     address: '0x7dC3A74F0684fc026f9163C6D5c3C99fda2cf60a'
     abiName: 'dyfiRedemptionABI'
-    methods:  
+    methods:
       - 'discount'
       - 'get_latest_price'
       - name: 'eth_required'

docs/contributing/governance/veyfi.md

@@ -1,10 +1,10 @@
 ---
-rpcCalls:  
+rpcCalls:
   - name: 'dYFI Redemption'
     chain: '1'
     address: '0x7dC3A74F0684fc026f9163C6D5c3C99fda2cf60a'
     abi: 'dyfiRedemptionABI'
-    methods:  
+    methods:
       - 'discount'
       - 'get_latest_price'
       - name: 'eth_required'
@@ -59,7 +59,7 @@ veYFI incorporates [YIP-56: Buyback and Build](https://gov.yearn.fi/t/yip-56-buy
     - **x** = `veYFI_supply / YFI_supply`
     <br />
 
-  :::yearn[Current On-Chain Values]
+  :::yearn[Current Onchain Values]
 
   - The current redemption discount is: <ContractData contract='dYFI Redemption' methodName='discount' decimals={18} />
   - Current Spot Price of YFI/ETH: <ContractData contract='dYFI Redemption' methodName='get_latest_price' decimals={18} />

docs/contributing/introduction.md

@@ -2,8 +2,8 @@
 
 ![image](/img/dao-pages/here-we-are-cropped.jpg)
 
-Yearn is a collective of developers, users, thinkers, and doers all working toward making the best suite of on-chain, decentralized, yield products. There are no bosses or interns, no board of directors or HR department, only those who contribute to, participate in, and explore Yearn. Yearn started as an experiment with a week long release of YFI and continues as an experiment today.
+Yearn is a collective of developers, users, thinkers, and doers all working toward making the best suite of onchain, decentralized, yield products. There are no bosses or interns, no board of directors or HR department, only those who contribute to, participate in, and explore Yearn. Yearn started as an experiment with a week long release of YFI and continues as an experiment today.
 
 ## Governance
 
-The Yearn ecosystem is controlled by YFI token holders who submit and vote on off-chain proposals that govern the ecosystem. Proposals that generate majority support \(>50% of the vote\) are implemented by a 9-member multi-signature wallet. Changes must be signed by 6 out of the 9 wallet signers to be implemented. The members of the multi-signature wallet were voted in by YFI holders and are subject to change from future governance votes. Please refer to the [multisig documentation](/developers/security/multisig) for the list of multisig signers. For more info about the governance process, please consult the [multisig members list](/developers/security/multisig) and [YIP-61: Governance 2.0](https://gov.yearn.fi/t/yip-61-governance-2-0/10460).
+The Yearn ecosystem is controlled by YFI token holders who submit and vote on offchain proposals that govern the ecosystem. Proposals that generate majority support \(>50% of the vote\) are implemented by a 9-member multi-signature wallet. Changes must be signed by 6 out of the 9 wallet signers to be implemented. The members of the multi-signature wallet were voted in by YFI holders and are subject to change from future governance votes. Please refer to the [multisig documentation](/developers/security/multisig) for the list of multisig signers. For more info about the governance process, please consult the [multisig members list](/developers/security/multisig) and [YIP-61: Governance 2.0](https://gov.yearn.fi/t/yip-61-governance-2-0/10460).

docs/contributing/operations/decision-making.md

@@ -3,16 +3,16 @@
 ## Types of Decisions
 
 
-There are two key dimensions of decision-making at yearn: on- or off-chain; gated or un-gated.
+There are two key dimensions of decision-making at yearn: on- or offchain; gated or un-gated.
 
--   On-chain decisions are executed via transactions on the blockchain.
--   Off-chain decisions are executed in various ways off of the blockchain.
+-   Onchain decisions are executed via transactions on the blockchain.
+-   Offchain decisions are executed in various ways off of the blockchain.
 -   Gated decisions require specific permissions.
 -   Un-gated decisions can be made by anyone, they are permissionless.
 
 Here are some examples for the four categories of decisions that emerge from this space:
 
-|    |on-chain|off-chain|
+|    |onchain|offchain|
 |----|--------|---------|
 |gated|add a strategy to a vault|merge a pr|
 ||transfer money from the treasury|decide on a logo|
@@ -21,17 +21,17 @@ Here are some examples for the four categories of decisions that emerge from thi
 ||execute a signed multisig tx|write a new docs page|
 ||create a new vault|propose a YIP|
 
-[Gov 2.0](https://gov.yearn.fi/t/yip-61-governance-2-0) clarifies who holds decision-making power for our most critical kinds of decisions: on-chain gated decisions. But what about the other kinds? Who decides how off-chain gated decisions are made? Are there any guidelines for un-gated decisions or are they totally open? The rest of this document aims to clarify these questions.
+[Gov 2.0](https://gov.yearn.fi/t/yip-61-governance-2-0) clarifies who holds decision-making power for our most critical kinds of decisions: onchain gated decisions. But what about the other kinds? Who decides how offchain gated decisions are made? Are there any guidelines for un-gated decisions or are they totally open? The rest of this document aims to clarify these questions.
 
 ## Gated Decisions
 
-### On-Chain
+### Onchain
 
-All possible gated on-chain decisions are organized by Gov 2.0 into discrete and transferable objects called 'Decision-Making Powers' or just 'powers' for short. These powers are objects --- abstractions just above the specific transactions that embody the actual decisions. As we use this new system, we can decide to make these objects more or less granular. Currently YFI holders have the 'Manage Powers' decision-making power, so changes to each power is decided via YFI vote. But, YFI holders could vote to delegate the 'Manage Powers' power, or a subset of it, to a yTeam in the future.
+All possible gated onchain decisions are organized by Gov 2.0 into discrete and transferable objects called 'Decision-Making Powers' or just 'powers' for short. These powers are objects --- abstractions just above the specific transactions that embody the actual decisions. As we use this new system, we can decide to make these objects more or less granular. Currently YFI holders have the 'Manage Powers' decision-making power, so changes to each power is decided via YFI vote. But, YFI holders could vote to delegate the 'Manage Powers' power, or a subset of it, to a yTeam in the future.
 
-### Off-Chain
+### Offchain
 
-Currently gated off-chain decision-making powers are held by various members of the yearn core team and there is no overarching process defined to organize them. Here is an incomplete list of domains with off-chain gates to be organized in the future:
+Currently gated offchain decision-making powers are held by various members of the yearn core team and there is no overarching process defined to organize them. Here is an incomplete list of domains with offchain gates to be organized in the future:
 
 -   yearn twitter account admin
 -   various yearn frontend admin
@@ -124,9 +124,9 @@ He makes the site and shares internally, and now it's yearn-official.
 
 5) Conflict Resolution (optional)
 
-Daniel's decision causes some conflict inside yearn. There has been no process to decide what is yearn-official in the off-chain space, so Daniel had the power to use the advice process and make a decision on it. No one is questioning that, but Philbert is strongly against the new site being yearn-official so he decides to start the conflict resolution process with Daniel about this decision.
+Daniel's decision causes some conflict inside yearn. There has been no process to decide what is yearn-official in the offchain space, so Daniel had the power to use the advice process and make a decision on it. No one is questioning that, but Philbert is strongly against the new site being yearn-official so he decides to start the conflict resolution process with Daniel about this decision.
 
-During the process (described below), Daniel and Philbert talk it through and together decide to update the site to add yWaifu content, which was the main cause of Philbert's tension. And through talking, they came up with a proposal for a new gate on deciding what's yearn-official off-chain. They do the advice process on it and then implement it.
+During the process (described below), Daniel and Philbert talk it through and together decide to update the site to add yWaifu content, which was the main cause of Philbert's tension. And through talking, they came up with a proposal for a new gate on deciding what's yearn-official offchain. They do the advice process on it and then implement it.
 
 ## The Conflict Resolution Process
 

docs/developers/addresses/v3-contracts.md

@@ -54,7 +54,7 @@ Core contracts are the base generic contracts that can be used by anyone who wan
 
 ### Periphery Contracts
 
-All generic periphery contracts and factories can be retrieved on chain from the `AddressProvider` Contract:
+All generic periphery contracts and factories can be retrieved onchain from the `AddressProvider` Contract:
 
 | Name / ENS |  Periphery Contract Address |
 | ---------------------- | ---------------------- |
@@ -74,7 +74,7 @@ For a more complete list of all available periphery contracts visit the [Periphe
 
 ## Yearn Specific Addresses
 
-Yearn Specific contracts and roles, as well as the most up to date V3 registry can be retrieved on chain from the Role Manager.
+Yearn Specific contracts and roles, as well as the most up to date V3 registry can be retrieved onchain from the Role Manager.
 
 To find individual vaults, use the V3 Registry below or refer to https://yearn.fi/v3
 

docs/developers/building-on-yearn.md

@@ -53,7 +53,7 @@ Check out the [Frontend Integrations](front-end-development) section of this doc
 
 ## Data Analysis
 
-Yearn aims to provide more insights into our products to our customers and partners through analyzing the on-chain and off-chain data. Given that all Yearn protocol data is publicly stored on-chain, there are lots of insights to be gained from analyzing these transactions.
+Yearn aims to provide more insights into our products to our customers and partners through analyzing the onchain and offchain data. Given that all Yearn protocol data is publicly stored onchain, there are lots of insights to be gained from analyzing these transactions.
 
 **Dune Analytics**- Query contract data and generate dashboards with SQL
 

docs/developers/data-services/kong.md

@@ -54,7 +54,7 @@ query MainnetVaults {
 REST: https://kong.yearn.fi/api/rest/list/vaults/:chainId
 REST Example: https://kong.yearn.fi/api/rest/list/vaults/1
 
-#### List Yearn v2 vaults on all chains
+#### List Yearn V2 vaults on all chains
 
 ```graphql
 query GetV2VaultAddresses {

docs/developers/data-services/ydaemon.md

@@ -148,15 +148,18 @@ migrable (string)
 chainIDs (string)
 
 - Default: All supported chains
-- Valid values: Comma-separated chain IDs: 1, 10, 137, 250, 8453, 42161
+- Valid values: Comma-separated chain IDs: 1, 10, 100, 137, 146, 250, 8453, 42161, 747474
 - Example: "1,137,42161"
 - Supported chains:
   - 1 = Ethereum
   - 10 = Optimism
+  - 100 = Gnosis
   - 137 = Polygon
+  - 146 = Sonic
   - 250 = Fantom
   - 8453 = Base
   - 42161 = Arbitrum
+  - 747474 = Katana
 
 humanized (boolean)
 
@@ -182,7 +185,7 @@ GET /{chainID}/reports/{address}             # Harvest reports for strategy
 ```
 GET /{chainID}/vaults/harvests/{addresses}   # Harvest history for vaults
 GET /{chainID}/earned/{address}/{vaults}     # Earnings per vault per user
-GET /{chainID}/earned/{address}              # All earnings for user on chain
+GET /{chainID}/earned/{address}              # All earnings for user onchain
 GET /earned/{address}                        # All earnings for user (all chains)
 ```
 
@@ -270,7 +273,7 @@ yDaemon aggregates data from multiple sources:
 
 1. **Yearn Subgraph**: Base data source for vault and strategy information
 2. **Yearn Meta**: Configuration and metadata (risk scores, descriptions, icons)
-3. **Yearn Lens Oracle**: On-chain price data for tokens and vaults
+3. **Yearn Lens Oracle**: Onchain price data for tokens and vaults
 4. **Blockchain RPC**: Direct chain queries via Tenderly and other providers
 5. **Curve API**: Pool and gauge information for Curve vaults
 6. **External Price Feeds**: Gamma, Pendle, and other protocol-specific data

docs/developers/data-services/yearn-data.md

@@ -11,7 +11,7 @@ Kong's Yearn index covers the v3 and v2 vault ecosystems:
 - Regular contract snapshots of each registry, vault, strategy, trade handler, accountant, and debt allocator.
 - Full event history for each of the above (*with limited history on transfers, deposits, withdraws, and approves).
 - Snapshot hooks for computing vault-strategies relationships, debts, fees, and rewards.
-- Snapshot hooks for integrating off-chain risk and meta data.
+- Snapshot hooks for integrating offchain risk and meta data.
 - Event hooks for tracking new vaults and strategies, computing spot harvest APRs, and pricing transfers.
 - Timeseries hooks for computing APY and TVL.