Update from SAP DITA CMS (squashed):

commit 23667b917db59f669b081433340b2bb8e4f3d3ee
Author: REDACTED
Date:   Tue Apr 1 10:10:04 2025 +0000

    Update from SAP DITA CMS 2025-04-01 10:10:04

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

commit fcec026308b52813c10d3db09a91022f3b07def1
Author: REDACTED
Date:   Tue Apr 1 09:00:46 2025 +0000

    Update from SAP DITA CMS 2025-04-01 09:00:46

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

commit 21d5e32a269ad5eb86ae2a5da0a87a0b896e7a30
Author: REDACTED
Date:   Tue Apr 1 07:27:57 2025 +0000

    Update from SAP DITA CMS 2025-04-01 07:27:57

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

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

Author: ditaccms-bot

REUSE.toml

@@ -1,4 +1,4 @@
-version = 1
+ersion = 1
 SPDX-PackageName = "btp-job-scheduling-service"
 SPDX-PackageSupplier = "Hördt Sylvia ([email protected])"
 SPDX-PackageDownloadLocation = "https://github.com/SAP-docs/btp-job-scheduling-service"

docs/20---Concepts/multitenancy-in-sap-job-scheduling-service-464b613.md

@@ -4,17 +4,32 @@
 
 The SAP Job Scheduling service allows invocation of job actions in the context of Platform-as-a-Service \(PaaS\) or Software-as-a-Service \(SaaS\) tenants.
 
-This means that a deployed multitenant application can create/view/edit/delete jobs in the context of tenants, which have subscribed to it. To support a multitenancy scenario, a multitenancy provider application must be deployed and bound to instances of both the SAP SaaS Provisioning service and the SAP Job Scheduling service and define the SAP Job Scheduling service as a dependency.
+This means that a deployed multitenant application can create, view, edit, and delete jobs in the context of tenants, which have subscribed to it.
+
+
+
+<a name="loio464b6130857c4bc98af21a0b528cd35a__section_gzb_qrd_r2c"/>
+
+## Prerequisites
+
+To support a multitenancy scenario, you must:
+
+1.  Deploy a multitenant application to a provider subaccount.
+
+2.  Bind the deployed application to instances of both the SAP SaaS Provisioning service and the SAP Job Scheduling service.
+
+3.  Define the SAP Job Scheduling service as a dependency.
+
 
 
 
 <a name="loio464b6130857c4bc98af21a0b528cd35a__section_l51_r1r_c5b"/>
 
-## Additional resources how to create a multitenancy scenario:
+## Additional Resources for Creating a Multitenancy Scenario
 
 
 
-### General understanding and concepts of Multitenancy:
+### General understanding and concepts of multitenancy:
 
 -   [SAP Help: Developing Multitenant Applications in the Cloud Foundry Environment](https://help.sap.com/docs/BTP/65de2977205c403bbc107264b8eccf4b/5e8a2b74e4f2442b8257c850ed912f48.html)
 
@@ -23,7 +38,7 @@ This means that a deployed multitenant application can create/view/edit/delete j
 
 
 
-### SAP Job Scheduling service-specific:
+### SAP Job Scheduling service-specific resources:
 
 -   [Job Scheduler in SAP Business Technology Platform: Overview](https://blogs.sap.com/2021/06/30/job-scheduler-in-sap-business-technology-platform-overview-of-blog-posts/)
 
@@ -36,9 +51,16 @@ This means that a deployed multitenant application can create/view/edit/delete j
 
 ## Subscriptions and Service Behavior
 
-If a SaaS tenant unsubscribes from the provided service which consumes the SAP Job Scheduling service, all corresponding jobs and schedules are deleted.
+The SAP Job Scheduling service provides an administration dashboard that you can access with space developer permissions. The administration dashboard shows the jobs of all subscribed SaaS tenants as well jobs created with the tenant of the multitenant application. A tenant-specific dashboard can be implemented by the multitenant application using the REST API of the SAP Job Scheduling service.
+
+When a single instance of the SAP Job Scheduling service is used by one multitenant application, and the SaaS tenant unsubscribes from that application, all corresponding jobs and schedules are deleted.
+
+When a single instance of the SAP Job Scheduling service is used by multiple multitenant applications, and one SaaS tenant subscribes to more than one of these multitenant applications:
+
+-   The data is shared among the applications the SaaS tenant has subscribed to.
+
+-   If you delete a subscription to one of these applications, the data in the SAP Job Scheduling service remains intact until all subscriptions are deleted.
 
-The SAP Job Scheduling service provides an administration dashboard that you can access with space developer permissions. The administration dashboard shows the jobs of all subscribed SaaS tenants as well jobs created with the tenant of the multitenancy application. A tenant-specific dashboard can be implemented by the multitenancy application using the REST API of the SAP Job Scheduling service.
 
 
 
@@ -50,7 +72,7 @@ The SAP Job Scheduling service provides an administration dashboard that you can
 
 -   Credentials bound to a SaaS tenant could be used to access SaaS tenant bound data only.
 
--   Credentials bound to the PaaS tenant are bound to the SAP Job Scheduling service instance. This means that the multitenancy provider application is allowed to create/read/edit/delete all jobs and schedules for the bound SAP Job Scheduling service instance without any restrictions of SaaS tenants.
+-   Credentials bound to the PaaS tenant are bound to the SAP Job Scheduling service instance. This means that the provider of the multitenant application is allowed to create, read, edit, and delete all jobs and schedules for the bound SAP Job Scheduling service instance without any restrictions of SaaS tenants.
 
 
 **Related Information**  

docs/create-a-service-instance-in-the-kyma-dashboard-224a49a.md

@@ -48,7 +48,7 @@ You've logged on to the SAP BTP cockpit. For more information, see [Navigate in
 
 ## Results
 
-Your service now has a service binding. To use it, it must be mounted within your application. For more information, see [Using SAP BTP Services in the Kyma Environment](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/ea4dd81e49254dd482d32e3c20f4477a.html "With the Kyma environment you can connect SAP BTP services to your cluster and manage them using the SAP BTP Operator module.") :arrow_upper_right:.
+Your service now has a service binding. To use it, it must be mounted within your application. For more information, see [Using SAP BTP Services in the Kyma Environment](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/ea4dd81e49254dd482d32e3c20f4477a.html "With the Kyma environment, you can connect SAP BTP services to your cluster and manage them using the SAP BTP Operator module.") :arrow_upper_right:.
 
 **Related Information**