wording

deploy/quotas.yaml

@@ -2,10 +2,10 @@
 # Copy this file to quotas.yaml to enable quota enforcement.
 # If quotas.yaml doesn't exist, quotas are disabled (unlimited for all users).
 
-# Berths define quota tiers using nautical crew ranks.
-# Each berth has a quota limit specified in human-readable format.
+# Tiers define quota levels using nautical crew ranks.
+# Each tier has a quota limit specified in human-readable format.
 # Supported units: B, KB, MB, GB, TB, PB (case-insensitive)
-berths:
+tiers:
   # Entry-level crew - suitable for new or casual users
   deckhand:
     quota: 5GB
@@ -18,18 +18,18 @@ berths:
   quartermaster:
     quota: 100GB
 
-  # You can add custom berths with any name:
+  # You can add custom tiers with any name:
   # unlimited_crew:
   #   quota: 1TB
 
 defaults:
-  # Default berth assigned to new crew members who don't have an explicit berth.
-  # This berth must exist in the berths section above.
-  new_crew_berth: deckhand
+  # Default tier assigned to new crew members who don't have an explicit tier.
+  # This tier must exist in the tiers section above.
+  new_crew_tier: deckhand
 
 # Notes:
-# - The hold captain (owner) always has unlimited quota regardless of berths.
-# - Crew members can be assigned a specific berth in their crew record.
-# - If a crew member's berth doesn't exist in config, they fall back to the default.
+# - The hold captain (owner) always has unlimited quota regardless of tiers.
+# - Crew members can be assigned a specific tier in their crew record.
+# - If a crew member's tier doesn't exist in config, they fall back to the default.
 # - Quota is calculated per-user by summing unique blob sizes (deduplicated).
 # - Quota is checked when pushing manifests (after blobs are already uploaded).