Updated definitions of AVS

docs/developers/avs-developer-guide.md

@@ -4,16 +4,16 @@ title: AVS Overview
 ---
 
 
-## What is an Actively Validated Service (AVS)?
+## What is an Autonomous Verifiable Service (AVS)?
 
 
-An Actively Validated Service (AVS) on EigenLayer is a decentralized service built on Ethereum that provides custom validation mechanisms of off-chain operations. Please see the [Intro to EigenLayer](https://docs.eigenlayer.xyz/eigenlayer/overview/) for background context on the broader EigenLayer ecosystem.
+An Autonomous Verifiable Service (AVS) on EigenLayer is a decentralized service built on Ethereum that provides custom verification mechanisms of off-chain operations. Please see the [Intro to EigenLayer](https://docs.eigenlayer.xyz/eigenlayer/overview/) for background context on the broader EigenLayer ecosystem.
 
-An AVS is composed of on-chain contracts for validation and an off-chain network of Operators. Operators execute the service on behalf of the AVS and then post evidence of their execution on-chain to the AVS contracts. Tasks can be initiated via on-chain contracts, off-chain via direct communication with the Operators, or via a task aggregator entity.
+An AVS is composed of on-chain contracts for verification and an off-chain network of Operators. Operators execute the service on behalf of the AVS and then post evidence of their execution on-chain to the AVS contracts. Tasks can be initiated via on-chain contracts, off-chain via direct communication with the Operators, or via a task aggregator entity.
 
-The design of the off-chain execution and on-chain validation is entirely flexible based on the needs of the AVS developer. 
-- If the Operators perform tasks properly, the AVS can distribute rewards.
-- If the Operators perform tasks maliciously, their delegate stake can be slashed by the AVS, and the Operator can be removed from the Operator set. 
+The design of the off-chain execution and on-chain verification is entirely flexible based on the needs of the AVS developer. 
+- If the Operators perform tasks properly, the AVS can autonomously distribute rewards.
+- If the Operators perform tasks maliciously, their delegate stake can be slashed autonomously by the AVS, and the Operator can be removed from the Operator set. 
 
  Please see the original EigenLayer whitepaper [EigenLayer: The Restaking Collective](/docs/eigenlayer/overview/whitepaper.md) for further background on AVS design.
 
@@ -22,7 +22,7 @@ The design of the off-chain execution and on-chain validation is entirely flexib
 
 ## Why Build an AVS?
 
-Launching new Web3 projects requires substantial time and effort to bootstrap capital and operators. Builders should focus on their core product differentiators rather than bootstrapping economic security. Building an Actively Validated Service (AVS) on EigenLayer offers enhanced security, decentralization, and cost efficiency by utilizing Ethereum’s staking mechanism through restaking. This allows developers to focus more on their product’s core value and innovation without the significant overhead of setting up a new consensus mechanism or validator networks from scratch.
+Launching new Web3 projects requires substantial time and effort to bootstrap capital and operators. Builders should focus on their core product differentiators rather than bootstrapping economic security. Building an Autonomous Verifiable Service (AVS) on EigenLayer offers enhanced security, decentralization, and cost efficiency by utilizing Ethereum’s staking mechanism through restaking. This allows developers to focus more on their product’s core value and innovation without the significant overhead of setting up a new consensus mechanism or validator networks from scratch.
 
 The key benefits of building an AVS on EigenLayer include:
 - Security via Restaking: leverage Ethereum’s staking mechanism to secure your service.
@@ -34,7 +34,7 @@ The key benefits of building an AVS on EigenLayer include:
 
 ## What Can You Build as an AVS?
 
-The scope of AVS design is broad. It includes **any off-chain service** that can be validated on-chain. This flexibility allows AVS developers to design custom validation mechanisms suited to the unique requirements of their service. The only requirement is that some evidence for the off-chain service’s execution is posted on-chain to enable validation of the service.
+The scope of AVS design is broad. It includes **any off-chain service** that can be verified on-chain. This flexibility allows AVS developers to design custom verification mechanisms suited to the unique requirements of their service. The only requirement is that some evidence for the off-chain service’s execution is posted on-chain to enable verification of the service.
 
 Examples of these services include rollup services, co-processors, cryptography services, zk Proof services, and more.
 

docs/eigenlayer/overview/key-terms.md

@@ -5,7 +5,7 @@ sidebar_position: 2
 
 
 
-- **Actively Validated Services (AVS):**  a service built externally to EigenLayer that requires active validation by a set of Operators. An AVS deploys its service manager to interact with EigenLayer core contracts that allow for Operator registration to Operator Sets, slashing, and rewards distribution. Once registered, an Operator agrees to run the AVS’s off-chain code.
+- **Actively Validated Services (AVS):**  a service built externally to EigenLayer that requires verification by a set of Operators. An AVS deploys its service manager to interact with EigenLayer core contracts that allow for Operator registration to Operator Sets, slashing, and rewards distribution. Once registered, an Operator agrees to run the AVS’s off-chain code.
 
 - **Allocation / Deallocation:** an in-protocol commitment of security to an AVS’s Operator Set by an Operator. The act of allocating demarcates portions of an Operator’s delegated stake as Unique Stake, making it slashable by a single AVS. Deallocation is the same process in reverse, subject to additional time delays that ensure AVSs can appropriately slash for tasks that have occurred in the past.