DOC-1629: Fix single sourcing and cross repo tags (#1329)

Co-authored-by: micheleRP <[email protected]>

Author: Feediver1

modules/manage/pages/schema-reg/schema-reg-authorization.adoc

@@ -257,14 +257,22 @@ User `jane` now has global `read` and `write` access to the Schema Registry and
 
 === Create a role with Schema Registry ACLs
 
+ifdef::env-cloud[]
+You can combine Schema Registry ACLs with xref:security:authorization/rbac/rbac_dp.adoc[role-based access control (RBAC)] to create reusable roles. This approach simplifies permission management when you need to assign the same set of permissions to multiple users.
+endif::[]
+
+ifndef::env-cloud[]
 You can combine Schema Registry ACLs with xref:manage:security/authorization/rbac.adoc[role-based access control (RBAC)] to create reusable roles. This approach simplifies permission management when you need to assign the same set of permissions to multiple users.
+endif::[]
 
 This example creates a role called `SoftwareEng` and assigns it ACLs for both topic and Schema Registry access:
 
+ifndef::env-cloud[]
 [NOTE]
 ====
 Redpanda recommends using the topic naming strategy for Schema Registry subjects, where subjects follow the pattern `<topicName>-key` or `<topicName>-value`. For details, see xref:manage:schema-reg/schema-id-validation.adoc#set-subject-name-strategy-per-topic[Set subject name strategy per topic].
 ====
+endif::[]
 
 [,bash]
 ----
@@ -344,6 +352,7 @@ User:alice  *     TOPIC          bar            LITERAL                READ
 The `Not found` error occurs in the request: `12:17:33.935 DEBUG sending request {"method": "POST", "URL: "http://127.0.0.1:8081/security/acls", "has_bearer": false, 
 "has_basic_auth": false}`, meaning that the endpoint is not available (because you are using an older Redpanda version). You must upgrade to the current version of Redpanda.
 
+ifndef::env-cloud[]
 This next error occurs when the user tries to create two ACLs, one for a topic and one for a registry-subject:
 
 [bash]
@@ -364,6 +373,7 @@ User:mary  *     TOPIC          private        LITERAL                READ
 ----
 
 The `Invalid license: not present` error indicates that the user is trying to create an ACL for a resource that requires a license, but no license is present. See xref:get-started:licensing/overview.adoc[Licensing overview] for details on how to obtain a license.
+endif::[]
 
 == Suggested reading