TON Proxy page: mention that TON Sites can also be opened through a public HTTPS gateway #2344

The TON Proxy page (/foundations/web3/ton-proxy) explains how to open a TON Site by running rldp-http-proxy locally and pointing the browser's HTTP proxy at it. That is the right reference for running a proxy, but a reader who only wants to look at a .ton site has no lighter option on the page. Earlier versions of the docs mentioned a public gateway for that; the restructured pages no longer do.

Proposal: one short subsection under "Forward proxy (client-side)":

Without installing anything

Public HTTPS gateways run a TON Proxy for you and serve TON Sites at ordinary web addresses: <name>.ton opens as https://<name>.ton.website. A gateway sees the requests it forwards, so for anything sensitive, run your own proxy as described above.

Notes:

• ton.website serves every .ton name, .adnl addresses (<address>.adnl.website) and TON Storage sites, and keeps a weekly-checked directory of TON Sites at https://ton.website/. It is free to use and needs no account or wallet.
• I maintain ton.website. Happy to word it as "for example, ton.website" or to list other public gateways alongside it if you know of any.
• The privacy sentence is there on purpose: a gateway is a third party in the path, unlike a local proxy.

Would a PR with this subsection be welcome?