docs: updates to long-lived environment and billing docs (#12948)

* docs: updates to long-lived environment and billing docs

* updated faq

www/apps/cloud/app/billing-usage/page.mdx

@@ -103,10 +103,7 @@ To view your organization's usage:
 You'll find two sections at the top of the Billing settings:
 
 - **Current plan**: The plan your organization is currently subscribed to and when the next billing date is.
-- **Usage limits**: The usage limits for your current plan. The **Usage** column indicates how much your organization has used so far, and the **Included** column indicates the limits of your current plan. You'll mainly find the following usage limits:
-    - **Seats**: The number of users that can be added to your organization.
-    - **Projects**: The number of projects that can be created in your organization.
-    - Other add-ons may be listed based on your plan.
+- **Usage limits**: A breakdown of your plan and resources usage. You can see the pricing of your plan and any other add-ons, such as additional projects.
 
 ![Usage limits sections in the Billing settings](https://res.cloudinary.com/dza7lstvk/image/upload/v1750241792/Cloud/CleanShot_2025-06-18_at_13.16.23_2x_k7eeay.png)
 

www/apps/cloud/app/environments/long-lived/page.mdx

@@ -65,12 +65,10 @@ The created environment will appear in the [project's dashboard](../../projects/
 
 ### Trigger Environment Deployment
 
-After creating the environment, you need to trigger its deployment by pushing a commit to the environment's branch (in this example, `staging`).
+After creating the environment, Medusa will automatically trigger a deployment for the environment using the associated branch (for example, `staging`). This includes:
 
-The first time you push a commit, Medusa will:
-
-- Deploy the environment from the associated branch.
-- Set up the database and resources for the environment. These are different from the resources of other environments.
+- Deploying the environment from the associated branch.
+- Setting up the database and resources for the environment. These are different from the resources of other environments.
 
 After that, Medusa will automatically deploy the environment whenever you push a new commit to the associated branch.
 

www/apps/cloud/app/faq/page.mdx

@@ -51,3 +51,11 @@ You can deploy projects like marketplaces, B2B, subscription-based stores, and m
 ## Does Cloud create new Medusa projects for each deployment?
 
 No, Medusa does not create new Medusa projects for your deployments. Instead, it deploys your existing Medusa project from your GitHub repository.
+
+---
+
+## Can I use a static IP address for my Medusa project on Cloud?
+
+No, Medusa does not provide a static IP address for your Medusa project on Cloud. However, you can use a proxy that has a static IP address to connect to your Medusa project.
+
+Contact support for help with setting up a proxy for your Medusa project.

www/apps/cloud/generated/edit-dates.mjs

@@ -11,12 +11,12 @@ export const generatedEditDates = {
   "app/s3/page.mdx": "2025-06-25T07:57:24.832Z",
   "app/draft-order-plugin/page.mdx": "2025-06-25T07:57:14.898Z",
   "app/loyalty-plugin/page.mdx": "2025-06-26T11:11:02.320Z",
-  "app/billing-usage/page.mdx": "2025-06-25T07:57:03.206Z",
+  "app/billing-usage/page.mdx": "2025-07-14T11:09:25.451Z",
   "app/logs/page.mdx": "2025-06-19T07:44:38.336Z",
   "app/update-medusa/page.mdx": "2025-06-25T07:57:30.170Z",
   "app/connect-storefront/page.mdx": "2025-06-25T07:47:00.499Z",
   "app/environments/environment-variables/page.mdx": "2025-06-25T07:42:53.521Z",
-  "app/environments/long-lived/page.mdx": "2025-06-25T07:55:24.283Z",
+  "app/environments/long-lived/page.mdx": "2025-07-14T11:01:54.536Z",
   "app/environments/preview/page.mdx": "2025-06-25T08:00:00.839Z",
-  "app/faq/page.mdx": "2025-06-25T08:00:26.853Z"
+  "app/faq/page.mdx": "2025-07-14T11:44:58.587Z"
 }