chore(docs): more readme updates

CONTRIBUTING.md

@@ -11,14 +11,14 @@ It should be considered as a guide to help you navigate the process.
 
 The [Telegram][dev-tg] is available for any concerns you may have that are not covered in this guide.
 
-If you contribute to this project, your contributions will be made to the project as follow: (a) contributions to the Rundler library (i.e. all code outside of the `bin` directory) will be licensed under the GNU Lesser General Public License v3.0, also included in our repository in the COPYING.LESSER file; and (b) contributions to the Rundler binaries (i.e. all code inside of the `bin` directory) will be licensed under the GNU General Public License v3.0, also included in our repository in the COPYING file.
+If you contribute to this project, your contributions will be made to the project as follows: (a) contributions to the Rundler library (i.e. all code outside of the `bin` directory) will be licensed under the GNU Lesser General Public License v3.0, also included in our repository in the COPYING.LESSER file; and (b) contributions to the Rundler binaries (i.e. all code inside of the `bin` directory) will be licensed under the GNU General Public License v3.0, also included in our repository in the COPYING file.
 
 ### Ways to contribute
 
 There are fundamentally three ways an individual can contribute:
 
 1. **By opening an issue:** For example, if you believe that you have uncovered a bug
-   in Rundler, creating a new issue in the issue tracker is the way to report it.
+   in Rundler, creating a new issue in the [issue tracker][gh-issues] is the way to report it.
 2. **By adding context:** Providing additional context to existing issues,
    such as screenshots and code snippets to help resolve issues.
 3. **By resolving issues:** Typically this is done in the form of either
@@ -30,7 +30,7 @@ There are fundamentally three ways an individual can contribute:
 
 ### Submitting a bug report
 
-When filing a new bug report in the issue tracker, you will be presented with a basic form to fill out.
+When filing a new bug report in the [issue tracker][gh-issues], you will be presented with a basic form to fill out.
 
 If you believe that you have uncovered a bug, please fill out the form to the best of your ability. Do not worry if you cannot answer every detail, just fill in what you can. Contributors will ask follow-up questions if something is unclear.
 
@@ -103,6 +103,7 @@ We follow the [conventional commits](https://www.conventionalcommits.org/en/v1.0
 
 From within GitHub, opening a new pull request will present you with a template that should be filled out. Please try your best at filling out the details, but feel free to skip parts if you're not sure what to put.
 
-[dev-tg]: https://t.me/rundler
+*Adapted from the [Reth contributing guide](https://github.com/paradigmxyz/reth/blob/main/CONTRIBUTING.md).*
 
-*Adapted from the [Reth contributing guide](https://github.com/paradigmxyz/reth/blob/main/CONTRIBUTING.md).*
+[dev-tg]: https://t.me/rundler
+[gh-issues]: https://github.com/alchemyplatform/rundler/issues/new/choose

README.md

@@ -29,13 +29,13 @@ Rundler is meant to power the ERC-4337 ecosystem with an implementation that use
 Our goals with Rundler:
 
 1. **ERC-4337 Specification Compliance**: Rundler strives to implement the full ERC-4337 specification and to maintain support as the specification changes and new onchain components are released. This includes new Entry Point contract support, support for the upcoming P2P mempool specification, support for alternative mempools, and more.
-2. **High Performance and Reliability**:  Rundler strives to power the most demanding workloads in cloud environments. Rust was chosen for its high performance and memory safety. Rundler's modular architecture lets providers choose to run the stateless components (RPC, builder) in a fully horizontally scalable manner connecting to the stateful components (mempool, p2p, event cache) via the network. Rundler's bundle builder is designed to be able to support the full gas throughput of the network its building for.
+2. **High Performance and Reliability**:  Rundler strives to power the most demanding workloads in cloud environments. Rust was chosen for its high performance and memory safety. Rundler's modular architecture lets providers choose to run the stateless components (RPC, builder) in a fully horizontally scalable manner connecting to the stateful components (mempool, p2p, event cache) via the network. Rundler's bundle builder is designed to be able to support the full gas throughput of the network it's building for.
 3. **Extendability/Chain Support**: ERC-4337 is designed to support any EVM chain. However, different EVM supporting networks have different rules around how they support things like gas usage, gas fees, precompiles, etc. Rundler is designed to be extendable and easily adapted to support any EVM chain.
 4. **Modularity**: Rundler is written in a modular manner, allowing its components to be run as a single integrated binary, or as a distributed system. Rundler also strives for its individual crates to be used to support future ERC-4337 tooling.
 
 ## Status
 
-Rundler is under active development. It is used in Alchemy's cloud to power its account abstraction APIs. However, it is rapidly being upgraded, features are being added, interfaces will have breaking changes, and the ERC-4337 spec is evolving from onchain learnings.
+Rundler is under active development. It is used in Alchemy's cloud to power Alchemy's Account Abstraction APIs account abstraction APIs. However, Rundler is rapidly being upgraded, features are being added, interfaces will have breaking changes, and the ERC-4337 spec is evolving from onchain learnings.
 
 The documentation is work in progress, and we are working to improve it. Please [reach out](#help) with any questions.