Update from SAP DITA CMS (squashed):

commit d1ed831927cac70b8c40496ac131a3cf85d12eb0
Author: REDACTED
Date:   Tue Oct 14 16:22:44 2025 +0000

    Update from SAP DITA CMS 2025-10-14 16:22:44

    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loio2080d0faf9d84ce6aa14caa4caa32935
    Language: en-US
    Builddable map: 0fcfe38e11674227bb0a8d014337319b.ditamap

commit 1df97ebbcddc0dd1e8d602ff1a6be5a3a861cc28
Author: REDACTED
Date:   Tue Oct 14 16:00:57 2025 +0000

    Update from SAP DITA CMS 2025-10-14 16:00:57

    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loio2080d0faf9d84ce6aa14caa4caa32935
    Language: en-US
    Builddable map: 0fcfe38e11674227bb0a8d014337319b.ditamap

commit 20ce07683202749143d143e319ff4825f6e9899e
Author: REDACTED
Date:   Tue Oct 14 12:22:40 2025 +0000

    Update from SAP DITA CMS 2025-10-14 12:22:40

    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap

##################################################
[Remaining squash message was removed before commit...]

Author: ditaccms-bot

docs/20-getting-started/creating-an-abap-system-50b32f1.md

@@ -225,7 +225,7 @@ For more information about creating service instances, see [Create Service Insta
     </td>
     <td valign="top">
 
-    The **HANA Cloud disk size** refers to the disk size in GB of the SAP HANA Cloud database used by the ABAP environment service instance. If the parameter is set to `auto`, the SAP HANA Cloud storage size is set to the minimal value `40 * size_of_persistence + 40`. The maximum allowed value is `120 * size_of_persistence + 40`. If you set a higher value, it will consume 0.002 HANA compute units \(HCU\) for any GB exceeding the minimal default size of the persistence disk. Therefore, the HCU ratio of additional storage disk to RAM is 1 : 31.25 per GB \(as 1 HCU = 16 GB\).
+    The **HANA Cloud disk size** refers to the disk size in GB of the SAP HANA Cloud database used by the ABAP environment service instance. If the parameter is set to `auto`, the SAP HANA Cloud storage size is set to the minimal value `40 * size_of_persistence + 40`. The maximum allowed value is `240 * size_of_persistence + 40`. If you set a higher value, it will consume 0.002 HANA compute units \(HCU\) for any GB exceeding the minimal default size of the persistence disk. Therefore, the HCU ratio of additional storage disk to RAM is 1 : 31.25 per GB \(as 1 HCU = 16 GB\).
 
     </td>
     </tr>

docs/20-getting-started/updating-an-abap-system-7890ffa.md

@@ -30,18 +30,99 @@ After you have created an ABAP environment instance, you can change the followin
 
 
 > ### Note:  
-> The updates of these properties are done without any downtime, or - in case of updating the HANA memory or disk size - with near zero downtime \(meaning that the database is not accessible for a few seconds only\).
+> The updates are done with zero downtime, except for the HANA database resizing, which is performed with near zero downtime. This means that the database is inaccessible for only a few seconds.
 
-To **change the initial admin**, you have to use the *Maintain Employees* SAP Fiori app. See [Maintain Employees](../50-administration-and-ops/maintain-employees-e882b0f.md).
+> ### Tip:  
+> To **change the initial admin**, you have to use the *Maintain Employees* SAP Fiori app. See [Maintain Employees](../50-administration-and-ops/maintain-employees-e882b0f.md).
 
 > ### Restriction:  
-> A downsizing of the HANA Cloud memory size is only possible down to the minimum amount of memory required for a stable performance of the HANA Cloud database. Before the memory size is decreased, an SQL query \(as described on [SAP HANA Database Downsizing](https://help.sap.com/docs/hana-cloud/sap-hana-cloud-administration-guide/sap-hana-database-downsizing)\) is automatically run on the database to make sure the downsizing is possible based on the already consumed memory.
+> The following restrictions apply when resizing the HANA Cloud database:
 > 
-> The HANA Cloud memory size cannot be decreased while a system is stopped. To decrease the HANA Cloud memory size of a stopped instance, the instance has to be started via the `Landscape Portal` first.
+> -   Memory downsizing is limited to the minimum amount of memory required for a stable performance of the database. Before the memory size is decreased, an automatic SQL query \(as described in [SAP HANA Database Downsizing](https://help.sap.com/docs/hana-cloud/sap-hana-cloud-administration-guide/sap-hana-database-downsizing)\) verifies that sufficient memory is available before downsizing.
 > 
-> The HANA Cloud disk size can currently only be increased, and not decreased.
+> -   The memory size cannot be decreased while a system is stopped. To decrease the memory size of a stopped instance, the instance has to be started via the `Landscape Portal` first.
 > 
-> Both the HANA Cloud memory and the disk size can only be resized once every 24 hours.
+> -   The disk size can only be increased, not decreased.
+> 
+> -   Both memory and disk size can only be resized once every 24 hours.
+
+
+
+### Interdependencies Between HANA Cloud Memory and Disk Sizes
+
+****
+
+
+<table>
+<tr>
+<th valign="top">
+
+ 
+
+</th>
+<th valign="top">
+
+When increasing memory
+
+</th>
+<th valign="top">
+
+When decreasing memory
+
+</th>
+</tr>
+<tr>
+<td valign="top">
+
+**Disk size = auto**
+
+</td>
+<td valign="top">
+
+If the current disk size is below the new minimum, it's automatically increased.
+
+</td>
+<td valign="top" rowspan="2">
+
+The disk size stays at its current value, even if it exceeds the new maximum disk size.
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+**Disk size unchanged \(fixed value\)**
+
+</td>
+<td valign="top">
+
+The disk size must be at least equal to the new minimum disk size.
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+**Disk size increased**
+
+</td>
+<td valign="top" colspan="2">
+
+The new disk size must be within the new minimum-maximum range.
+
+</td>
+</tr>
+</table>
+
+> ### Note:  
+> The minimum and maximum disk sizes \(`size_of_persistence_disk`\) are defined by the memory size \(`size_of_persistence`\) as follows:
+> 
+> -   `min(size_of_persistence_disk) = 40 * size_of_persistence + 40`
+> 
+> -   `max(size_of_persistence_disk) = 240 * size_of_persistence + 40`
+> 
+> 
+> Each GB above the \(new\) minimum disk size consumes 0.002 HANA compute units \(HCU\) of your quota.
 
 
 

docs/30-development/applications-0540211.md

@@ -98,9 +98,9 @@ The timeout parameters follow the following descending order of priority:
     >         task-execution-timeout:120 
     > ```
 
-3.  **Global-Level Parameters:** 
+3.  **Top-Level Parameters:** 
 
-    If neither a command-line option nor a module-level parameter are provided, the global parameters are used. Global parameters are applicable to all applications.
+    If neither a command-line option nor a module-level parameter are provided, the top-level parameters are used. Top-level parameters are applicable to all applications.
 
     > ### Example:  
     > ```

docs/30-development/blue-green-deployment-of-multitarget-applications-772ab72.md

@@ -2,18 +2,18 @@
 
 # Blue-Green Deployment of Multitarget Applications
 
-Use the blue-green deployment technique by running two identical production environments, allowing seamless updates without downtime for Cloud Foundry Multitarget applications.
+Use the blue-green deployment technique by running two identical production environments, allowing seamless updates without downtime for Cloud Foundry multitarget applications.
 
 > ### Restriction:  
 > Blue-green deployment is supported only for Cloud Foundry applications. It is not supported for bound services, such as service instances and their configuration, workflow content, and HTML5 repository content, among others. Live and idle applications are bound to the same service instances.
 
 By using the blue-green deployment technique, you can update the system without downtime and with reduced risk. During the process, you can perform tests and validation of the new application version using productive data. A classical blue-green deployment of stateless applications, which are modeled as an MTA, is supported.
 
-In the context of Multitarget applications, you have the following options for using blue-green deployment:
+In the context of multitarget applications, you have the following options for using blue-green deployment:
 
 -   [Legacy Blue-Green Deployment](legacy-blue-green-deployment-764308c.md) - where the production environments are called “blue” and “green”
 -   [Blue-Green Deployment Strategy](blue-green-deployment-strategy-7c83810.md) - where the production environments are called “live” and “idle”
--   [\(Experimental\) Incremental Blue-Green Deployment Strategy](experimental-incremental-blue-green-deployment-strategy-2e4dfed.md) - an alternative to the standard blue-green deployment strategy, where the "idle" application is incrementally scaled up to the desired instance count while the "live" application instances are gradually stopped
+-   [Incremental Blue-Green Deployment Strategy](incremental-blue-green-deployment-strategy-2e4dfed.md) - an alternative to the standard blue-green deployment strategy, where the "idle" application is incrementally scaled up to the desired instance count while the "live" application instances are gradually stopped
 
 **Related Information**  
 

docs/30-development/blue-green-deployment-strategy-7c83810.md

@@ -2,7 +2,7 @@
 
 # Blue-Green Deployment Strategy
 
-Use the current blue-green deployment of Multitarget applications.
+Use the current blue-green deployment of multitarget applications.
 
 
 
@@ -39,6 +39,9 @@ If you have already executed successful deployments using the [Legacy Blue-Green
 
 1.  Deploy your updated MTA in idle state by executing the command `cf deploy <your-mta-archive-v2> --strategy blue-green`.
 
+    > ### Note:  
+    > If you want to have the opportunity to perform a rollback after the blue-green deployment, you need to back up your MTA by adding the command line option `--backup-previous-version`. For more information, see [\(Experimental\) Rollback of Multitarget Applications](experimental-rollback-of-multitarget-applications-d612be9.md).
+
     The first action is that all MTA services are updated.
 
     This creates:
@@ -48,7 +51,7 @@ If you have already executed successful deployments using the [Legacy Blue-Green
         > ### Note:  
         > The new application version is launched on all instances defined in the MTA deployment descriptor. During the testing phase or when the deployment is paused for user verification, the application temporarily requires double the usual resources \(instances\). This is because both the old and the new versions of the application are running concurrently. If the testing phase is skipped or if the deployment continues without delay, the resource usage will be optimized sooner.
         > 
-        > If you are looking for a more resource-efficient deployment approach, see [\(Experimental\) Incremental Blue-Green Deployment Strategy](experimental-incremental-blue-green-deployment-strategy-2e4dfed.md). However, keep in mind that this approach requires more time than the standard blue-green deployment strategy.
+        > If you are looking for a more resource-efficient deployment approach, see [Incremental Blue-Green Deployment Strategy](incremental-blue-green-deployment-strategy-2e4dfed.md). However, keep in mind that this approach requires more time than the standard blue-green deployment strategy.
 
     -   temporary routes to the idle applications
 
@@ -103,11 +106,11 @@ For more detailed information and example results of the blue-green deployment p
 **Related Information**  
 
 
-[Blue-Green Deployment of Multitarget Applications](blue-green-deployment-of-multitarget-applications-772ab72.md "Use the blue-green deployment technique by running two identical production environments, allowing seamless updates without downtime for Cloud Foundry Multitarget applications.")
+[Blue-Green Deployment of Multitarget Applications](blue-green-deployment-of-multitarget-applications-772ab72.md "Use the blue-green deployment technique by running two identical production environments, allowing seamless updates without downtime for Cloud Foundry multitarget applications.")
 
-[Legacy Blue-Green Deployment](legacy-blue-green-deployment-764308c.md "Use the legacy blue-green deployment strategy of Multitarget applications.")
+[Legacy Blue-Green Deployment](legacy-blue-green-deployment-764308c.md "Use the legacy blue-green deployment strategy of multitarget applications.")
 
-[\(Experimental\) Incremental Blue-Green Deployment Strategy](experimental-incremental-blue-green-deployment-strategy-2e4dfed.md "Use the incremental blue-green deployment strategy to save resources by incrementally deploying the new version of your Multitarget application.")
+[Incremental Blue-Green Deployment Strategy](incremental-blue-green-deployment-strategy-2e4dfed.md "Use the incremental blue-green deployment strategy to save resources by incrementally deploying the new version of your multitarget application.")
 
 [Multitarget Application Commands for the Cloud Foundry Environment](../50-administration-and-ops/multitarget-application-commands-for-the-cloud-foundry-environment-65ddb1b.md "A list of additional commands to deploy multitarget applications (MTA) to the Cloud Foundry environment.")
 

docs/30-development/develop-9464e3a.md

@@ -78,16 +78,7 @@ Business configuration plays a major role in SaaS solutions. It refers to a pred
 
 To maintain these configuration options, you have to create dedicated apps using the ABAP RESTful Application Programming Model. See [Create a Business Configuration App for Factory Calendar Using the ABAP RESTful Application Programming Model](https://developers.sap.com/mission.abap-dev-factory-calendar.html).
 
-Using the business configurations API, you can register business configurations. These business configurations are then displayed in the list of all maintainable business configurations in the SAP Fiori app Maintain Business Configurations, if the user has the necessary authorizations for the service of the business configuration. See [Business Configuration Maintenance Object Cloud Platform API](business-configuration-maintenance-object-cloud-platform-api-508d406.md).
-
-
-
-### Translation
-
-To translate your custom developments into other languages, you can use the [Maintain Translations](https://help.sap.com/docs/btp/sap-business-technology-platform/maintain-translations?version=Cloud) app.
-
-> ### Note:  
-> To add additional languages, you need to create a new add-on product version.
+Using the business configurations API, you can register business configurations. These business configurations are then displayed in the list of all maintainable business configurations in the SAP Fiori App Maintain Business Configurations, if the user has the necessary authorizations for the service of the business configuration. See [Business Configuration Maintenance Object Cloud Platform API](business-configuration-maintenance-object-cloud-platform-api-508d406.md).