SAP-docs
diff --git a/‎docs/10-concepts/account-model-8ed4a70.md
Lines changed: 2 additions & 12 deletions b/‎docs/10-concepts/account-model-8ed4a70.md
Lines changed: 2 additions & 12 deletions
diff --git a/‎docs/10-concepts/apis-d1d1107.md
Lines changed: 0 additions & 16 deletions b/‎docs/10-concepts/apis-d1d1107.md
Lines changed: 0 additions & 16 deletions
diff --git a/‎docs/10-concepts/basic-concepts-4a0dd09.md
Lines changed: 0 additions & 40 deletions b/‎docs/10-concepts/basic-concepts-4a0dd09.md
Lines changed: 0 additions & 40 deletions
diff --git a/‎docs/10-concepts/basic-platform-concepts-73beb06.md
Lines changed: 2 additions & 2 deletions b/‎docs/10-concepts/basic-platform-concepts-73beb06.md
Lines changed: 2 additions & 2 deletions
diff --git a/‎docs/10-concepts/bringing-your-corporate-identity-provider-for-platform-users-feature-set-b-8980b91.md
Lines changed: 2 additions & 2 deletions b/‎docs/10-concepts/bringing-your-corporate-identity-provider-for-platform-users-feature-set-b-8980b91.md
Lines changed: 2 additions & 2 deletions
@@ -92,9 +92,9 @@ Optionally, you can also enable the following features in your directories:
 
 [Manage the Account Explorer Hierarchy \[Feature Set B\]](../50-administration-and-ops/manage-the-account-explorer-hierarchy-feature-set-b-2e2a5b6.md "Create an account structure by creating a hierarchy of directories and subaccounts using the SAP BTP cockpit. Add, move, and delete subaccounts and directories in your structure.")
 
-[Configure Entitlements and Quotas for Directories \[Feature Set B\]](../50-administration-and-ops/configure-entitlements-and-quotas-for-directories-feature-set-b-37f8871.md "Assign entitlements to directories by adding service plans and distribute the quotas available in your global account to your directories using the SAP BTP cockpit.")
+[Configure Entitlements and Quotas for Directories \[Feature Set B\]](../50-administration-and-ops/configure-entitlements-and-quotas-for-directories-feature-set-b-37f8871.md "Distribute entitlements that are available in your global account to directories by adding service plans and their allowed quotas by using the SAP BTP cockpit.")
 
-[Configure Entitlements and Quotas for Subaccounts](../50-administration-and-ops/configure-entitlements-and-quotas-for-subaccounts-5ba357b.md "Assign entitlements to subaccounts by adding service plans and distribute the quotas available in your global account to your subaccounts using the SAP BTP cockpit.")
+[Configure Entitlements and Quotas for Subaccounts](../50-administration-and-ops/configure-entitlements-and-quotas-for-subaccounts-5ba357b.md "Distribute the entitlements that are available in your global account by adding service plans and their allowed quotas to your subaccounts using the SAP BTP cockpit.")
 
 [Getting a Global Account](../20-getting-started/getting-a-global-account-d61c281.md#loiod61c2819034b48e68145c45c36acba6e "SAP BTP offers two types of global accounts: Trial accounts (completely free of charge) and enterprise accounts. Within an enterprise account, you can use both free and paid plans.")
 
@@ -176,24 +176,18 @@ Labels are made up of a *label name* \(also referred to as a *key*\) and up to 1
 
 Types of Labels
 
-
-
 </th>
 <th valign="top">
 
 Examples
 
-
-
 </th>
 </tr>
 <tr>
 <td valign="top">
 
 Single-value labels are useful for labels that have an identifier, or for labels with fixed lists.
 
-
-
 </td>
 <td valign="top">
 
@@ -219,8 +213,6 @@ Single-value labels are useful for labels that have an identifier, or for labels
 
 Multi-value labels make them useful for labels that typically have more than one value assigned to them.
 
-
-
 </td>
 <td valign="top">
 
@@ -240,8 +232,6 @@ Labels can also be assigned with a name only and no value. In such cases, the la
 
 Note that currently for service instances, labels must have at least value.
 
-
-
 </td>
 <td valign="top">
 
 
@@ -23,67 +23,51 @@ SAP BTP enables you to consume APIs and publish your own ones through the follow
 
 Offering
 
-
-
 </th>
 <th valign="top">
 
 Description
 
-
-
 </th>
 </tr>
 <tr>
 <td valign="top">
 
 **[SAP BTP on SAP Business Accelerator Hub](https://api.sap.com/products/SAPCloudPlatform/overview)**
 
-
-
 </td>
 <td valign="top">
 
 The SAP Business Accelerator Hub provides you with one central repository for browsing and accessing APIs from SAP and selected partners. Test APIs and try out mock data in your systems.
 
 It is also the official place where REST and OData REST API references are published.
 
-
-
 </td>
 </tr>
 <tr>
 <td valign="top">
 
 **[SAP BTP API Management](https://help.sap.com/viewer/p/SAP_CLOUD_PLATFORM_API_MANAGEMENT)**
 
-
-
 </td>
 <td valign="top">
 
 API Management allows you to build, manage, publish, and monetize your own APIs within one secure and scalable environment.
 
-
-
 </td>
 </tr>
 <tr>
 <td valign="top">
 
 **SDKs**
 
-
-
 </td>
 <td valign="top">
 
 The software development kits \(SDKs\) available for SAP BTP offer APIs to, for example, accelerate enterprise app development.
 
 For an overview on the available SDKs, see [Tools](tools-abcae5b.md).
 
-
-
 </td>
 </tr>
 </table>
 
@@ -18,159 +18,119 @@ This table explains basic concepts relating to the Kyma environment. It aims to
 
 Concept
 
-
-
 </th>
 <th valign="top">
 
 Description
 
-
-
 </th>
 </tr>
 <tr>
 <td valign="top">
 
 Kyma cluster
 
-
-
 </td>
 <td valign="top">
 
 A Kubernetes cluster provisioned with the latest version of the open-source project "Kyma". You can enable such a cluster on a given subaccount through the SAP BTP cockpit. After creating a Kyma environment instance on your subaccount, the cluster is provisioned automatically through Gardener on your chosen cloud service provider. To access the cluster, you must have appropriate roles assigned to your subaccount.
 
-
-
 </td>
 </tr>
 <tr>
 <td valign="top">
 
 Kyma module
 
-
-
 </td>
 <td valign="top">
 
 An extension to the Kyma environment that can be enabled, disabled or re-configured at runtime.
 
-
-
 </td>
 </tr>
 <tr>
 <td valign="top">
 
 Role
 
-
-
 </td>
 <td valign="top">
 
 Access to every cluster is managed by the roles assigned. Roles give the assigned users a different level of permissions suitable for different purposes. For more information, read [Assign Roles in the Kyma Environment](../50-administration-and-ops/assign-roles-in-the-kyma-environment-148ae38.md).
 
-
-
 </td>
 </tr>
 <tr>
 <td valign="top">
 
 Namespace
 
-
-
 </td>
 <td valign="top">
 
 Namespaces are used to organize objects in a cluster and provide a way to divide cluster resources. This way, several users can share a cluster but have access only to resources within the Namespace they have permissions for. This allows for increasing the security and organization of your cluster by dividing it into smaller units. Access to Namespaces in the Kyma environment depends on your permissions. SAP BTP users with the KymaRuntimeNamespaceAdmins role are entitled to create Namespaces, while users with the KymaRuntimeNamespaceDeveloper role can only list and edit Kubernetes and Kyma-specific resources scoped to specific Namespaces.
 
-
-
 </td>
 </tr>
 <tr>
 <td valign="top">
 
 Service operator
 
-
-
 </td>
 <td valign="top">
 
 A service operator is a piece of software that provides a set of all necessary resources \(such as CustomResourceDefinitions and controllers\) needed to provision third-party services in your Kubernetes cluster.
 
-
-
 </td>
 </tr>
 <tr>
 <td valign="top">
 
 Binding
 
-
-
 </td>
 <td valign="top">
 
 The connection you create between a service instance and an SAP solution so that they can communicate with each other. You can also bind a service instance to any workload running in the Kyma environment, such as a Function or a microservice.
 
-
-
 </td>
 </tr>
 <tr>
 <td valign="top">
 
 Credentials / Secrets
 
-
-
 </td>
 <td valign="top">
 
 Sensitive data necessary for an SAP solution to call the service, connect to it, and authenticate it. Depending on whether you use Kyma Dashboard or kubectl to create the binding between a service instance and an SAP solution, the Kubernetes Secret object that contains these credentials is either created automatically or you need to create it manually.
 
-
-
 </td>
 </tr>
 <tr>
 <td valign="top">
 
 Function
 
-
-
 </td>
 <td valign="top">
 
 A simple code snippet that you can run without provisioning or managing servers. It implements the exact business logic you define. A Function is based on the Function custom resource and can be written in either Node.js or Python. A Function can perform a business logic of its own. You can also bind it to an instance of a service and configure it to be triggered whenever it receives a particular event type from the service or a call is made to the service's API. Functions are executed only if they are triggered by an event or an API call.
 
-
-
 </td>
 </tr>
 <tr>
 <td valign="top">
 
 Microservice
 
-
-
 </td>
 <td valign="top">
 
 An architectural variant for extensions or applications, where you separate the tasks into smaller pieces that interact with each other as loosely coupled, independently deployable units of code. A failing microservice should not cause your whole application to fail. Microservices are packed in a container that is always running; it's idling if there is no load. The microservice should always be reachable even when the Pods move around. Microservices typically communicate through APIs.
 
-
-
 </td>
 </tr>
 </table>
 
@@ -2,7 +2,7 @@
 
 # Basic Platform Concepts
 
-SAP BTP offers users the ability to turn data into business value, compose end-to-end business processes, and build and extend SAP applications.
+SAP BTP offers users the ability to turn data into business value, compose end-to-end business processes, and build and extend SAP applications quickly.
 
 
 
@@ -172,7 +172,7 @@ When you purchase an enterprise account, you’re entitled to use a specific set
 
 -   An **entitlement** is your right to provision and consume a resource. In other words, entitlements are **the service plans** that you're entitled to use.
 
--   A **quota** represents the numeric quantity that defines the maximum allowed consumption of a resource. In other words, **how much** of a service plan you're entitled to use.
+-   A **quota** represents the numeric quantity of a service plan that you're entitled to consume in your global account and its subaccounts.
 
 
 For more information, see [Entitlements and Quotas](entitlements-and-quotas-00aa2c2.md).
 
@@ -26,9 +26,9 @@ The following figure illustrates the architecture required for platform users. T
 
 In the preceding figure, you enable trust between the SAP BTP global account and your corporate identity provider over your tenant of SAP Cloud Identity Services - Identity Authentication. For each global account, you choose the Identity Authentication tenant to use as the identity provider for platform users. For the platform identify provider, you can have up to three Identity Authentication tenants per global account. Multiple global accounts can share the same Identity Authentication tenant. When you log on to a platform resource, such as the cockpit, you indicate the Identity Authentication tenant that you want to log on with. For example, to log on to the cockpit, copy a URL parameter from the cockpit to identify the tenant:
 
-<code>https://<i class="varname">&lt;cockpit_region&gt;</i>.cockpit.btp.cloud.sap/cockpit/?idp=<i class="varname">&lt;tenant&gt;</i>.accounts.ondemand.com</code>
+<code>https://cockpit.btp.cloud.sap/cockpit/?idp=<i class="varname">&lt;tenant&gt;</i>.accounts.ondemand.com</code>
 
-For example: `https://emea.cockpit.btp.cloud.sap/cockpit/?idp=cidppuxhm.accounts.ondemand.com`
+For example: `https://cockpit.btp.cloud.sap/cockpit/?idp=cidppuxhm.accounts.ondemand.com`
 
 Once you’ve logged on, the cockpit displays any global accounts and subaccounts of which your platform user is a member.