rename scaling file

apps/docs/content/alpine/how-to/create.mdx

@@ -161,7 +161,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb"
 S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ"
 ```
 
-The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
+The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
 
 #### Description of description.yaml parameters
 

apps/docs/content/bun/how-to/create.mdx

@@ -165,7 +165,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb"
 S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ"
 ```
 
-The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
+The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
 
 #### Description of description.yaml parameters
 

apps/docs/content/clickhouse/overview.mdx

@@ -23,7 +23,7 @@ Our ClickHouse implementation features optimized default settings designed for a
 
 ### Resource Allocation
 
-Zerops automatically allocates resources to your ClickHouse service based on demand within the limits defined in your [automatic scaling configuration](/features/scaling-ha).
+Zerops automatically allocates resources to your ClickHouse service based on demand within the limits defined in your [automatic scaling configuration](/features/scaling).
 
 ## High Availability and Deployment Modes
 

apps/docs/content/deno/how-to/create.mdx

@@ -160,7 +160,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb"
 S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ"
 ```
 
-The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
+The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
 
 #### Description of description.yaml parameters
 

apps/docs/content/dotnet/how-to/create.mdx

@@ -161,7 +161,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb"
 S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ"
 ```
 
-The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
+The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
 
 #### Description of description.yaml parameters
 

apps/docs/content/elixir/how-to/create.mdx

@@ -160,7 +160,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb"
 S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ"
 ```
 
-The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
+The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
 
 #### Description of description.yaml parameters
 

apps/docs/content/features/pipeline.mdx

@@ -323,12 +323,12 @@ For [manual deployments](#manual-deploy-using-zerops-cli) using Zerops CLI, the
 Zerops uses the stored artifact to deploy identical versions of your application whenever a new container starts:
 
 - During new application version deployments
-- When applications [scale horizontally](/features/scaling-ha#horizontal-scaling-runtime-services-linux-containers-and-docker)
+- When applications [scale horizontally](/features/scaling#horizontal-scaling-runtime-services-linux-containers-and-docker)
 - When runtime containers fail and new containers start automatically
 
 ### First deploy
 
-For initial deployments, Zerops starts one or more runtime containers based on your service [auto scaling settings](/features/scaling-ha).
+For initial deployments, Zerops starts one or more runtime containers based on your service [auto scaling settings](/features/scaling).
 
 Zerops executes these steps for each new container:
 

apps/docs/content/gleam/how-to/create.mdx

@@ -161,7 +161,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb"
 S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ"
 ```
 
-The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
+The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
 
 #### Description of description.yaml parameters
 

apps/docs/content/go/how-to/create.mdx

@@ -161,7 +161,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb"
 S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ"
 ```
 
-The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
+The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
 
 #### Description of description.yaml parameters
 

apps/docs/content/homepage.mdx

@@ -168,7 +168,7 @@ Zerops has fully automatic horizontal and vertical scaling with configuration st
 
 You won't ever overprovision or underprovision your resources and your services will always have the exact resources they need. There won't be any cutting corners like sharing too few CPU cores between too many services. You will be able to rely on professional, reliable and highly available database setups with auto-repairing abilities that will scale along with your applications.
 
-<Button variant="secondary"><Link href="/features/scaling-ha">Read more about autoscaling and high availability</Link></Button>
+<Button variant="secondary"><Link href="/features/scaling">Read more about autoscaling and high availability</Link></Button>
 
 :::
 

apps/docs/content/java/how-to/create.mdx

@@ -161,7 +161,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb"
 S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ"
 ```
 
-The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
+The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
 
 #### Description of description.yaml parameters
 

apps/docs/content/keydb/how-to/create.mdx

@@ -55,7 +55,7 @@ Deployment mode cannot be changed after service creation.
 :::tip Learn More
 For detailed scaling configuration, deployment mode details, and troubleshooting, see:
 - [How Zerops scales KeyDB](/keydb/how-to/scale) - Database-specific scaling guide
-- [Automatic Scaling and High Availability](/features/scaling-ha) - Complete technical details
+- [Automatic Scaling and High Availability](/features/scaling) - Complete technical details
 :::
 
 ## Create KeyDB using zCLI

apps/docs/content/keydb/how-to/scale.mdx

@@ -9,7 +9,7 @@ import ResourceTable from '/src/components/ResourceTable';
 Zerops automatically scales your KeyDB service based on actual database usage. When your database needs more power, resources increase. When demand drops, resources scale down to reduce costs.
 
 :::tip Read More
-For complete scaling details across all services, see [Automatic Scaling and High Availability](/features/scaling-ha).
+For complete scaling details across all services, see [Automatic Scaling and High Availability](/features/scaling).
 :::
 
 ## How KeyDB scaling works
@@ -77,7 +77,7 @@ Consider increasing these values if your database experiences memory-related iss
 </figure>
 
 :::info Read More
-For detailed technical parameters and scaling behavior, see [Automatic Scaling and High Availability](/features/scaling-ha#resource-scaling-behavior).
+For detailed technical parameters and scaling behavior, see [Automatic Scaling and High Availability](/features/scaling#resource-scaling-behavior).
 :::
 
 ## Monitor usage
@@ -97,7 +97,7 @@ For complete technical specifications including:
 - Scaling increments and steps
 - Detailed scaling behavior patterns
 
-See [Resource Scaling Behavior](/features/scaling-ha#resource-scaling-behavior) in the general scaling documentation.
+See [Resource Scaling Behavior](/features/scaling#resource-scaling-behavior) in the general scaling documentation.
 
 ## Common issues
 

apps/docs/content/mariadb/how-to/create.mdx

@@ -64,7 +64,7 @@ Deployment mode cannot be changed after service creation.
 :::tip Learn More
 For detailed scaling configuration, deployment mode details, and troubleshooting, see:
 - [How Zerops scales MariaDB](/mariadb/how-to/scale) - Database-specific scaling guide
-- [Automatic Scaling and High Availability](/features/scaling-ha) - Complete technical details
+- [Automatic Scaling and High Availability](/features/scaling) - Complete technical details
 :::
 
 ## Create MariaDB using zCLI

apps/docs/content/mariadb/how-to/scale.mdx

@@ -9,7 +9,7 @@ import ResourceTable from '/src/components/ResourceTable';
 Zerops automatically scales your MariaDB service based on actual database usage. When your database needs more power, resources increase. When demand drops, resources scale down to reduce costs.
 
 :::tip Read More
-For complete scaling details across all services, see [Automatic Scaling and High Availability](/features/scaling-ha).
+For complete scaling details across all services, see [Automatic Scaling and High Availability](/features/scaling).
 :::
 
 ## How MariaDB scaling works
@@ -81,7 +81,7 @@ Consider increasing these values if your database experiences memory-related iss
 </figure>
 
 :::info Read More
-For detailed technical parameters and scaling behavior, see [Automatic Scaling and High Availability](/features/scaling-ha#resource-scaling-behavior).
+For detailed technical parameters and scaling behavior, see [Automatic Scaling and High Availability](/features/scaling#resource-scaling-behavior).
 :::
 
 ## Monitor usage
@@ -101,7 +101,7 @@ For complete technical specifications including:
 - Scaling increments and steps
 - Detailed scaling behavior patterns
 
-See [Resource Scaling Behavior](/features/scaling-ha#resource-scaling-behavior) in the general scaling documentation.
+See [Resource Scaling Behavior](/features/scaling#resource-scaling-behavior) in the general scaling documentation.
 
 ## Common issues
 

apps/docs/content/mariadb/tech-details/cluster.mdx

@@ -3,7 +3,7 @@ title: Asynchronous behaviour of MariaDB cluster
 description: Learn how you can work with asynchronous behaviour of mariadb cluster in Zerops.
 ---
 
-The following description applies only to the [highly available mode](/features/scaling-ha#highly-available-ha-mode) of the MariaDB service.
+The following description applies only to the [highly available mode](/features/scaling#highly-available-ha-mode) of the MariaDB service.
 
 ## Description of MariaDB cluster
 

apps/docs/content/mariadb/tech-details/limitations.mdx

@@ -3,7 +3,7 @@ title: Limitations of MariaDB cluster
 description: Get to know the limitations of mariadb cluster in Zerops.
 ---
 
-The following description applies only to the [highly available mode](/features/scaling-ha#highly-available-ha-mode) of the MariaDB service.
+The following description applies only to the [highly available mode](/features/scaling#highly-available-ha-mode) of the MariaDB service.
 
 #### InnoDB only
 

apps/docs/content/nodejs/how-to/create.mdx

@@ -160,7 +160,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb"
 S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ"
 ```
 
-The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
+The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
 
 #### Description of description.yaml parameters
 

apps/docs/content/php/how-to/create.mdx

@@ -157,7 +157,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb"
 S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ"
 ```
 
-The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
+The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
 
 #### Description of description.yaml parameters
 

apps/docs/content/postgresql/how-to/create.mdx

@@ -58,7 +58,7 @@ Deployment mode cannot be changed after service creation.
 :::tip Learn More
 For detailed scaling configuration, deployment mode details, and troubleshooting, see:
 - [How Zerops scales PostgreSQL](/postgresql/how-to/scale) - Database-specific scaling guide
-- [Automatic Scaling and High Availability](/features/scaling-ha) - Complete technical details
+- [Automatic Scaling and High Availability](/features/scaling) - Complete technical details
 :::
 
 ## Create PostgreSQL using zCLI
@@ -139,9 +139,9 @@ services:
 
 The YAML file describes your future project infrastructure. The project will contain two PostgreSQL services.
 
-The hostname of the first service will be set to `postgresql1`. The [high availability](/features/scaling-ha#highly-available-ha-mode) mode will be chosen and the custom [auto scaling configuration](/postgresql/how-to/scale) will be set.
+The hostname of the first service will be set to `postgresql1`. The [high availability](/features/scaling#highly-available-ha-mode) mode will be chosen and the custom [auto scaling configuration](/postgresql/how-to/scale) will be set.
 
-The hostname of the second service will be set to `postgresql2`. The [single container](/features/scaling-ha#single-container-mode) mode will be chosen and the default [auto scaling configuration](/postgresql/how-to/scale) will be set.
+The hostname of the second service will be set to `postgresql2`. The [single container](/features/scaling#single-container-mode) mode will be chosen and the default [auto scaling configuration](/postgresql/how-to/scale) will be set.
 
 #### Description of description.yaml parameters
 
@@ -349,7 +349,7 @@ services:
     mode: NON_HA
 ```
 
-The YAML file describes the list of one or more services that you want to add to your existing project. In the example above, one PostgreSQL service in the [single container](/features/scaling-ha#single-container-mode) with default [auto scaling](/postgresql/how-to/scale) configuration will be added to your project. The hostname of the new service will be set to `postgresql1`.
+The YAML file describes the list of one or more services that you want to add to your existing project. In the example above, one PostgreSQL service in the [single container](/features/scaling#single-container-mode) with default [auto scaling](/postgresql/how-to/scale) configuration will be added to your project. The hostname of the new service will be set to `postgresql1`.
 
 The content of the `services:` section of `import.yaml` is identical to the [project description file](#create-a-project-description-file). The `import.yaml` never contains the `project:` section because the project already exists.
 

apps/docs/content/postgresql/how-to/scale.mdx

@@ -9,7 +9,7 @@ import ResourceTable from '/src/components/ResourceTable';
 Zerops automatically scales your PostgreSQL service based on actual database usage. When your database needs more power, resources increase. When demand drops, resources scale down to reduce costs.
 
 :::tip Read More
-For complete scaling details across all services, see [Automatic Scaling and High Availability](/features/scaling-ha).
+For complete scaling details across all services, see [Automatic Scaling and High Availability](/features/scaling).
 :::
 
 ## How PostgreSQL scaling works
@@ -85,7 +85,7 @@ Consider increasing these values if your database experiences memory-related iss
 </figure>
 
 :::info Read More
-For detailed technical parameters and scaling behavior, see [Automatic Scaling and High Availability](/features/scaling-ha#resource-scaling-behavior).
+For detailed technical parameters and scaling behavior, see [Automatic Scaling and High Availability](/features/scaling#resource-scaling-behavior).
 :::
 
 ## Monitor usage
@@ -105,7 +105,7 @@ For complete technical specifications including:
 - Scaling increments and steps
 - Detailed scaling behavior patterns
 
-See [Resource Scaling Behavior](/features/scaling-ha#resource-scaling-behavior) in the general scaling documentation.
+See [Resource Scaling Behavior](/features/scaling#resource-scaling-behavior) in the general scaling documentation.
 
 ## Common issues
 

apps/docs/content/python/how-to/create.mdx

@@ -161,7 +161,7 @@ S3_ACCESS_KEY_ID="P8cX1vVVb"
 S3_ACCESS_SECRET="ogFthuiLYki8XoL73opSCQ"
 ```
 
-The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling-ha#single-container-mode)(/features/scaling-ha#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
+The hostname of the PostgreSQL service will be set to "db". The [single container](/features/scaling#single-container-mode)(/features/scaling#deployment-modes-databases-and-shared-storage) mode will be chosen and the default auto [scaling configuration](/postgresql/how-to/scale#configure-scaling) will be set.
 
 #### Description of description.yaml parameters