From da95de7ca284102b2e20ad8eac19e4a92523d987 Mon Sep 17 00:00:00 2001 From: str0k3 Date: Fri, 3 Jan 2025 11:34:19 +0100 Subject: [PATCH] Fix typo and grammar --- docs/sap-ai-core/manage-resource-groups-8aae6cb.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/sap-ai-core/manage-resource-groups-8aae6cb.md b/docs/sap-ai-core/manage-resource-groups-8aae6cb.md index 98ba70e..202c472 100644 --- a/docs/sap-ai-core/manage-resource-groups-8aae6cb.md +++ b/docs/sap-ai-core/manage-resource-groups-8aae6cb.md @@ -39,9 +39,9 @@ A resource group may also be referred to as an instance. ## Resource Group Level Resources -Executables at tenant level are shared across all resource groups. In contrast, runtime entities such as executions, deployments, configurations, and artifacts belong to a specific resource group and cannot be shared across resource groups. Similarly, generic secrets created within a resource group and be used only for workloads within that group. +Executables at the tenant level are shared across all resource groups. In contrast, runtime entities such as executions, deployments, configurations, and artifacts belong to a specific resource group and cannot be shared across resource groups. Similarly, generic secrets created within a resource group can be used only for workloads within that group. -You can register an object store at resource-group level by setting the resource group header. We recommend that you do not use the same object store bucket with the same IAM user for multiple resource groups. +You can register an object store at the resource-group level by setting the resource group header. We recommend that you do not use the same object store bucket with the same IAM user for multiple resource groups. Example resource group mappings are outlined in the figure below: