Use xref links

docs/modules/ROOT/pages/how-to-guides/managing-applications/proc-managing_applications.adoc

@@ -13,7 +13,7 @@ Cloning an application involves replicating the application's code and configura
 
 .**Prerequisite**
 
-* You have the link:https://redhat-appstudio.github.io/docs.appstudio.io/Documentation/main/getting-started/roles_permissions/[maintainer role] or greater in the original workspace where the embargoed issue was identified.
+* You have the xref:getting-started/roles_permissions/[maintainer role] or greater in the original workspace where the embargoed issue was identified.
 * You have downloaded the link:https://github.com/redhat-appstudio/rhtap-cli/releases[RHTAP CLI].
 
 .**Procedure**
@@ -23,8 +23,8 @@ Cloning an application involves replicating the application's code and configura
 +
 NOTE: Creating a private fork of the public link:https://docs.github.com/en/repositories/creating-and-managing-repositories/duplicating-a-repository[GitHub repository] is not possible.
 
-. link:https://redhat-appstudio.github.io/docs.appstudio.io/Documentation/main/how-to-guides/managing-workspaces/proc_creating_a_team_workspace/[Submit a request for a new workspace] dedicated to work on the embargoed issue. This workspace will serve as the private environment for cloning the affected application. Don't expose information about the vulnerability in your choice of a name for the workspace. If you had previously created a private workspace and is no longer in use for another embargoed process, you can re-use it as long as you re-restrict the User Access appropriately. Your personal workspace can also be used; make sure to review User Access.
-. Log in to the original workspace where the application was previously being developed using the `oc` CLI tool. (See link:https://redhat-appstudio.github.io/docs.appstudio.io/Documentation/main/getting-started/getting_started_in_cli/[Getting started with CLI].) Append `/workspaces/<original-tenant-workspace>` to the AppStudio API url used in the `oc login` command to target a particular workspace other than your default user workspace.
+. xref:how-to-guides/managing-workspaces/proc-creating_a_team_workspace.adoc[Submit a request for a new workspace] dedicated to work on the embargoed issue. This workspace will serve as the private environment for cloning the affected application. Don't expose information about the vulnerability in your choice of a name for the workspace. If you had previously created a private workspace and is no longer in use for another embargoed process, you can re-use it as long as you re-restrict the User Access appropriately. Your personal workspace can also be used; make sure to review User Access.
+. Log in to the original workspace where the application was previously being developed using the `oc` CLI tool. (See xref:getting-start/getting_started_in_cli/[Getting started with CLI].) Append `/workspaces/<original-tenant-workspace>` to the AppStudio API url used in the `oc login` command to target a particular workspace other than your default user workspace.
 . To export records the application from the original workspace with details changed to refer to your new private workspace, run the following command:
 
 +