docs: mark per-host request transforms as public beta

docs/network/internet-access.mdx

@@ -18,7 +18,7 @@
 const sandbox = await Sandbox.create({ allowInternetAccess: true })
 
 // Create sandbox without internet access
 const isolatedSandbox = await Sandbox.create({ allowInternetAccess: false })
 ```
 ```python Python
 from e2b import Sandbox
@@ -34,7 +34,7 @@
 When internet access is disabled, the sandbox cannot make outbound network connections, which provides an additional layer of security for sensitive code execution.
 
 <Note>
 Setting `allowInternetAccess` / `allow_internet_access` to a falsy value is equivalent to setting `network.denyOut` / `network.deny_out` to `['0.0.0.0/0']` (denying all traffic).
 </Note>
 
 ## Fine-grained network control
@@ -49,18 +49,18 @@
 ```js JavaScript & TypeScript
 import { Sandbox } from 'e2b'
 
 // Deny all traffic except specific IPs
 const sandbox = await Sandbox.create({
   network: {
     denyOut: ({ allTraffic }) => [allTraffic], // allTraffic === '0.0.0.0/0'
     allowOut: ['1.1.1.1', '8.8.8.0/24']
   }
 })
 
 // Deny specific IPs only
 const restrictedSandbox = await Sandbox.create({
   network: {
     denyOut: ['8.8.8.8']
   }
 })
 ```
@@ -90,7 +90,7 @@
 
 ### Domain-based filtering
 
 You can allow traffic to specific domains by specifying hostnames in `allowOut` / `allow_out`. When using domain-based filtering, you must deny all other traffic in `denyOut` / `deny_out`. Domains are not supported in the deny lists.
 
 <CodeGroup>
 ```js JavaScript & TypeScript
@@ -99,7 +99,7 @@
 // Allow only traffic to google.com
 const sandbox = await Sandbox.create({
   network: {
     allowOut: ['google.com'],
     denyOut: ({ allTraffic }) => [allTraffic]
   }
 })
@@ -118,7 +118,7 @@
 </CodeGroup>
 
 <Note>
 When any domain is used, the default nameserver `8.8.8.8` is automatically allowed to ensure proper DNS resolution.
 </Note>
 
 You can also use wildcards to allow all subdomains of a domain:
@@ -130,7 +130,7 @@
 // Allow traffic to any subdomain of mydomain.com
 const sandbox = await Sandbox.create({
   network: {
     allowOut: ['*.mydomain.com'],
     denyOut: ({ allTraffic }) => [allTraffic]
   }
 })
@@ -154,7 +154,7 @@
 ```js JavaScript & TypeScript
 import { Sandbox } from 'e2b'
 
 // Allow traffic to specific domains and IPs
 const sandbox = await Sandbox.create({
   network: {
     allowOut: ['api.example.com', '*.github.com', '8.8.8.8'],
@@ -221,8 +221,11 @@
 ### Per-host request transforms
 
 <Note>
-Per-host request transforms are currently in private beta.
-If you'd like access, please reach out to us at [support@e2b.dev](mailto:support@e2b.dev).
+Per-host request transforms are currently in public beta. You can start using them right away, no need to request access.
+
+Please keep in mind that this feature is still in active development, and the features and ways of interacting with it might change during this period.
+
+If you have any questions or feedback, please [reach out to us](https://e2b.dev/dashboard?support=true). Any input is greatly appreciated.
 </Note>
 
 You can register per-host rules under `network.rules` to apply transforms (for example, inject HTTP headers) on outbound requests matching a host. Rules are keyed by host and registering one does **not** grant egress on its own — the host must still be referenced via `allowOut` / `allow_out`.