docs: fix grammar in src/ethereum/forks (exceptions, requests, eoa_delegation, dao) #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Dec 31, 2025

repo_subpaths_for_grammar_check.md

-Original file line number
+Diff line change
@@ Expand Up @@
     ## src/ethereum/forks - Misc
-    - [ ] `src/ethereum/forks/*/exceptions.py`, `requests.py`, `vm/eoa_delegation.py`, `dao.py` (~40 files)
+    - [x] `src/ethereum/forks/*/exceptions.py`, `requests.py`, `vm/eoa_delegation.py`, `dao.py` (~40 files)
     ## src/ethereum (non-forks)
@@ Expand Down @@

src/ethereum/forks/amsterdam/requests.py

-Original file line number
+Diff line change
@@ -1,5 +1,5 @@
     """
-    Requests were introduced in EIP-7685 as a a general purpose framework for
+    Requests were introduced in EIP-7685 as a general purpose framework for
     storing contract-triggered requests. It extends the execution header and
     body with a single field each to store the request information.
     This inherently exposes the requests to the consensus layer, which can
@@ Expand Down @@

src/ethereum/forks/bpo1/requests.py

-Original file line number
+Diff line change
@@ -1,5 +1,5 @@
     """
-    Requests were introduced in EIP-7685 as a a general purpose framework for
+    Requests were introduced in EIP-7685 as a general purpose framework for
     storing contract-triggered requests. It extends the execution header and
     body with a single field each to store the request information.
     This inherently exposes the requests to the consensus layer, which can
@@ Expand Down @@

src/ethereum/forks/bpo2/requests.py

-Original file line number
+Diff line change
@@ -1,5 +1,5 @@
     """
-    Requests were introduced in EIP-7685 as a a general purpose framework for
+    Requests were introduced in EIP-7685 as a general purpose framework for
     storing contract-triggered requests. It extends the execution header and
     body with a single field each to store the request information.
     This inherently exposes the requests to the consensus layer, which can
@@ Expand Down @@

src/ethereum/forks/bpo3/requests.py

-Original file line number
+Diff line change
@@ -1,5 +1,5 @@
     """
-    Requests were introduced in EIP-7685 as a a general purpose framework for
+    Requests were introduced in EIP-7685 as a general purpose framework for
     storing contract-triggered requests. It extends the execution header and
     body with a single field each to store the request information.
     This inherently exposes the requests to the consensus layer, which can
@@ Expand Down @@

src/ethereum/forks/bpo4/requests.py

-Original file line number
+Diff line change
@@ -1,5 +1,5 @@
     """
-    Requests were introduced in EIP-7685 as a a general purpose framework for
+    Requests were introduced in EIP-7685 as a general purpose framework for
     storing contract-triggered requests. It extends the execution header and
     body with a single field each to store the request information.
     This inherently exposes the requests to the consensus layer, which can
@@ Expand Down @@

src/ethereum/forks/bpo5/requests.py

-Original file line number
+Diff line change
@@ -1,5 +1,5 @@
     """
-    Requests were introduced in EIP-7685 as a a general purpose framework for
+    Requests were introduced in EIP-7685 as a general purpose framework for
     storing contract-triggered requests. It extends the execution header and
     body with a single field each to store the request information.
     This inherently exposes the requests to the consensus layer, which can
@@ Expand Down @@

src/ethereum/forks/osaka/requests.py

-Original file line number
+Diff line change
@@ -1,5 +1,5 @@
     """
-    Requests were introduced in EIP-7685 as a a general purpose framework for
+    Requests were introduced in EIP-7685 as a general purpose framework for
     storing contract-triggered requests. It extends the execution header and
     body with a single field each to store the request information.
     This inherently exposes the requests to the consensus layer, which can
@@ Expand Down @@

Provide feedback