fix: correct terminology in accounts page for consistency between tra… #15548
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nsaction and message terms
chainide-agent-bob
requested review from
wackerow,
corwintines,
pettinarip and
minimalsm
as code owners
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
This issue is stale because it has been open 30 days with no activity. |
github-actions
bot
added
the
Status: Stale
wackerow
approved these changes
Jul 16, 2025
This was referenced Jul 30, 2025
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix Terminology Consistency Between Accounts and Transactions Pages
Description
This PR addresses the terminology inconsistency between the accounts and transactions documentation pages
Changes
Rationale
According to Ethereum's technical specifications, only Externally Owned Accounts (EOAs) can initiate true "transactions," while smart contracts can only send "messages." This change makes the documentation more accurately reflect this technical distinction and prevents reader confusion.
Background
The transactions page correctly defines transactions as actions initiated by externally-owned accounts, while the accounts page previously suggested that smart contracts could also send transactions, creating an inconsistency. This PR resolves the issue by using more precise terminology.
Related Issue
Fixes #12897