docs(bandwidth): drop the price and the allowance table

services/compute/bandwidth.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Bandwidth Allowances and Billing"
 sidebarTitle: "Bandwidth"
-description: "Learn how outbound internet traffic from SC Compute is measured, how each team's pooled monthly allowance works, what traffic above it costs, and where to see your usage."
+description: "Learn how outbound internet traffic from SC Compute is measured, how each team's pooled monthly allowance works, how traffic above it is charged, and where to see your usage."
 ---
 
 Every compute comes with a monthly allowance of outbound internet traffic. The allowances of all the computes in a team are added together into one pool, and you only pay for traffic above that pool.
@@ -19,25 +19,13 @@ Traffic is measured on the server that hosts your compute, not inside the comput
 
 ## Allowance per Specification
 
-Each specification includes a monthly allowance:
-
-| vCPU | RAM | Monthly allowance |
-|------|-----|-------------------|
-| 1 | 512 MB | 115 GB |
-| 1 | 1 GB | 235 GB |
-| 1 | 2 GB | 470 GB |
-| 2 | 4 GB | 900 GB |
-| 4 | 8 GB | 1,800 GB |
-| 8 | 16 GB | 3,600 GB |
-| 16 | 32 GB | 7,200 GB |
-
-The allowance for each specification is also shown in the **Bandwidth** column when you create a compute. 1 GB is 1,000,000,000 bytes.
+Each specification includes a monthly allowance, and bigger specifications include more. You can see the allowance for each specification in the **Bandwidth** column when you create a compute. 1 GB is 1,000,000,000 bytes.
 
 ## How the Team Allowance Works
 
 **The allowance is pooled per team.** Every compute adds its allowance to one team-wide amount, and your bill depends on the team's total traffic against that amount. One busy compute can use the allowance of quieter ones.
 
-**Part of a month counts for part of the allowance.** A compute adds its allowance for the share of the month it exists. For example, a 1 vCPU / 2 GB compute created halfway through a 30-day month adds about 235 GB, not 470 GB. A compute you destroy keeps the share it built up until it was destroyed.
+**Part of a month counts for part of the allowance.** A compute adds its allowance for the share of the month it exists. For example, a compute created halfway through a 30-day month adds about half of its monthly allowance. A compute you destroy keeps the share it built up until it was destroyed.
 
 **Stopped computes still count.** A stopped compute is still billed, so it keeps adding to the allowance.
 
@@ -47,7 +35,7 @@ The allowance for each specification is also shown in the **Bandwidth** column w
 
 ## Price
 
-Traffic above your team's allowance costs **38 RWF per GB**.
+Traffic above your team's allowance is charged per GB. You can see the current price per GB in the **Bandwidth** tab of your team's billing overview.
 
 ## How It Is Charged
 

services/compute/overview.mdx

@@ -73,7 +73,7 @@ The **Stopped** state still incurs charges because resources remain reserved. To
 
 ## Bandwidth
 
-Each compute includes a monthly allowance of outbound internet traffic, and the allowances of all the computes in a team are pooled. Inbound traffic and traffic between your computes are free. You only pay for outbound traffic above the team's allowance. See [Bandwidth](/services/compute/bandwidth) for the allowance per specification and how charges work.
+Each compute includes a monthly allowance of outbound internet traffic, and the allowances of all the computes in a team are pooled. Inbound traffic and traffic between your computes are free. You only pay for outbound traffic above the team's allowance. See [Bandwidth](/services/compute/bandwidth) for how the allowance and charges work.
 
 ---