diff --git a/CHANGELOG.md b/CHANGELOG.md
index bffd2ca39a6..fce6c915d6b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,5 @@
+- Clarified the instructions that needs to run in container 
+  (bsc#1252680)
 - Improved CLM procedure in Adminstration Guide (bsc#1230876)
 - Added troubleshooting section for mass duplicate machine_id
 - Improved recommendation in Large Deployments Guide
diff --git a/modules/client-configuration/pages/registration-bootstrap.adoc b/modules/client-configuration/pages/registration-bootstrap.adoc
index 769a2ccad7b..bb8295608d7 100644
--- a/modules/client-configuration/pages/registration-bootstrap.adoc
+++ b/modules/client-configuration/pages/registration-bootstrap.adoc
@@ -1,10 +1,11 @@
 [[registering.clients.bootstrap]]
 = Register Clients With a Bootstrap Script
-:revdate: 2025-06-11
+:revdate: 2025-06-10
 :page-revdate: {revdate}
 
 == Introduction
 
+
 Registering clients with a bootstrap script gives you control over parameters, and can help if you have to register a large number of clients at once.
 
 To register clients using a bootstrap script, we recommend you create a template bootstrap script to begin, which can then be copied and modified.
@@ -29,7 +30,7 @@ Additional considerations:
 ifeval::[{uyuni-content} == true]
 
 [IMPORTANT]
-.GPG Keys and Uyuni Client Tools
+.GPG keys and Uyuni client tools
 ====
 The GPG key used by Uyuni Client Tools is not trusted by default.
 When you create your bootstrap script, add a path to the file containing the public key fingerprint with the [systemitem]``ORG_GPG_KEY`` parameter.
@@ -47,6 +48,11 @@ After migrating from an older version of {productname} to a newer version, we st
 
 endif::[]
 
+[IMPORTANT]
+====
+To access a shell inside the server container run [literal]``mgrctl term`` on the container host. 
+From there, one can run the CLI tools as usual.
+====
 
 
 [[registering.clients.bootstrap.mgr-bootstrap]]
@@ -59,6 +65,15 @@ The arguments [option]``--activation-keys`` and [option]``--script``, are the on
 On the {productname} Server, as root at the command line execute it with the mandatory arguments.
 Replace [systemitem]``<ACTIVATION_KEY`` and [systemitem]``<EDITED_NAME>`` with your values:
 
+. From the command prompt of the {productname} container host, run the following command as the root user to enter the server container:
+
++
+----
+mgrctl term
+----
++
+. Execute the following command (adjust the values as needed)
++
 ----
 mgr-bootstrap --activation-keys=<ACTIVATION_KEY> --script=bootstrap-<EDITED_NAME>.sh
 ----
@@ -80,6 +95,7 @@ mgr-boostrap --hostname <PROXY_FQDN>
 
 This command will create a new bootstrap script with default name [literal]``bootstrap.sh`` and it will overwrite the existing [literal]``bootstrap.sh`` file which is used for the Server.
 
+
 * To specify a different script, use the following comamnd:
 
 +
@@ -100,7 +116,7 @@ You can use the {productname} {webui} to create an editable bootstrap script.
 
 // 2022-10-26, ke: In step 2, check whether we can use {productname} macro.
 
-.Procedure: Creating a Bootstrap Script
+.Procedure: Creating a bootstrap script
 [role=procedure]
 _____
 
@@ -154,6 +170,14 @@ For more information about activation keys, see xref:client-configuration:activa
 [role=procedure]
 _____
 
+. From the command prompt of the {productname} container host, run the following command as the root user to enter the server container:
++
+
+----
+mgrctl term
+----
++
+
 . On your {productname} Server, as root at the command line change to the bootstrap directory with:
 
 +
@@ -211,6 +235,7 @@ Using environment variables allows dynamic input at runtime and makes it easier
 
 _____
 
+
 [NOTE]
 ====
 By default, bootstrap script will try to install [package]``venv-salt-minion`` if it is available in the bootstrap repository and [package]``salt-minion`` if there is no {salt} bundle in the bootstrap repository.
@@ -231,8 +256,15 @@ When you have finished creating your script, you can use it to register clients.
 [role=procedure]
 _____
 
-. On the {productname} Server, log in as root.
-  At the command prompt, and change to the bootstrap directory:
+. From the command prompt of the {productname} container host, run the following command as the root user to enter the server container:
++
+
+----
+mgrctl term
+----
++
+
+. On the {productname} Server, change to the bootstrap directory:
 
 +