address feedback

src/_blog/aut-tls.md

@@ -33,7 +33,7 @@ If you're interested in trying it out, we have an example with go-libp2p and js-
 
 Browser-node connectivity is foundational to any libp2p based network or application looking to expand its user base, through web-based clients. Since the libp2p ecosystem exhibits a wide range of network topologies, we've identified a few use-cases that benefit from AutoTLS.
 
-Blockchains already relying on libp2p, of which are over 10, like [Ethereum](https://ethereum.org/en/developers/docs/nodes-and-clients/light-clients/#why-are-light-clients-important) and Filecoin could leverage AutoTLS for browser-based and mobile light clients, with the goal of helping to increase client side verification of transactions. By extension, AutoTLS would also help with [Ethereum's statelessness roadmap](https://ethereum.org/en/roadmap/statelessness/), by allowing a wider set of nodes to serve data to light clients. This would decrease the reliance on centralized RPC providers, and increase the decentralization of such networks.
+Blockchains using libp2p, such as Ethereum and Filecoin, could integrate AutoTLS and improve access to chain state for browser-based [light clients](https://ethereum.org/en/developers/docs/nodes-and-clients/light-clients/#why-are-light-clients-important) and wallets. This would promote client-side transaction and state verification. Though it remains to be seen how much of a benefit this will be, since blockchains will typically have both a wire-protocol for long-lived connections between nodes and frontend specific APIs for request/response style interactions from apps. But the core idea is that AutoTLS enables reliable browser-based clients to connect to libp2p nodes, regardless of the network topology.
 
 ![Chains using libp2p](../assets/autotls/networks-using-libp2p.jpg)