suse-edge · e-minguez · Oct 9, 2025 · Oct 9, 2025
diff --git a/asciidoc/edge-book/links.adoc b/asciidoc/edge-book/links.adoc
@@ -85,10 +85,10 @@
 // ============================================================================
 // SUSE Telco Cloud
 
-:link-atip-examples: https://github.com/suse-edge/atip/tree/{release-tag-atip}/telco-examples/edge-clusters
-:link-atip-performance-settings: https://github.com/suse-edge/atip/blob/{release-tag-atip}/telco-examples/edge-clusters/dhcp/eib/custom/files/performance-settings.sh
-:link-atip-sriov-auto-filler: https://github.com/suse-edge/atip/blob/{release-tag-atip}/telco-examples/edge-clusters/dhcp/eib/custom/files/sriov-auto-filler.sh
-:link-atip-sriov-operator-values: https://github.com/suse-edge/charts/blob/main/charts/sriov-network-operator/{version-sriov-upstream}/values.yaml
+:link-telco-cloud-examples: https://github.com/suse-edge/telco-cloud-examples/tree/{release-tag-telco-cloud}/telco-examples/edge-clusters
+:link-telco-cloud-performance-settings: https://github.com/suse-edge/telco-cloud-examples/blob/{release-tag-telco-cloud}/telco-examples/edge-clusters/dhcp/eib/custom/files/performance-settings.sh
+:link-telco-cloud-sriov-auto-filler: https://github.com/suse-edge/telco-cloud-examples/blob/{release-tag-telco-cloud}/telco-examples/edge-clusters/dhcp/eib/custom/files/sriov-auto-filler.sh
+:link-telco-cloud-sriov-operator-values: https://github.com/suse-edge/charts/blob/main/charts/sriov-network-operator/{version-sriov-upstream}/values.yaml
 
 // ============================================================================
 // MLM

diff --git a/asciidoc/edge-book/versions.adoc b/asciidoc/edge-book/versions.adoc
@@ -57,7 +57,7 @@
 // == Release Tags ==
 :release-tag-eib: release-1.3
 :release-tag-edge-charts: release-3.4
-:release-tag-atip: release-3.4
+:release-tag-telco-cloud: release-3.4
 :release-tag-fleet-examples: release-3.4.0
 :release-tag-rancher: v2.12.1
 

diff --git a/asciidoc/product/atip-automated-provision.adoc b/asciidoc/product/atip-automated-provision.adoc
@@ -56,7 +56,7 @@ The following sections describe the different directed network provisioning work
 [NOTE]
 ====
 The following sections show how to prepare the different scenarios for the directed network provisioning workflow using SUSE Telco Cloud.
-For examples of the different configurations options for deployment (incl. air-gapped environments, DHCP and DHCP-less networks, private container registries, etc.), see the {link-atip-examples}[SUSE Telco Cloud repository].
+For examples of the different configurations options for deployment (incl. air-gapped environments, DHCP and DHCP-less networks, private container registries, etc.), see the {link-telco-cloud-examples}[SUSE Telco Cloud repository].
 ====
 
 [#single-node]
@@ -198,7 +198,7 @@ mkdir -p /opt/performance-settings
 cp performance-settings.sh /opt/performance-settings/
 ----
 
-The content of `custom/files/performance-settings.sh` is a script that can be used to configure the system for performance tuning and can be downloaded from the following {link-atip-performance-settings}[link].
+The content of `custom/files/performance-settings.sh` is a script that can be used to configure the system for performance tuning and can be downloaded from the following {link-telco-cloud-performance-settings}[link].
 
 [#add-custom-script-sriov]
 ===== SR-IOV script
@@ -215,7 +215,7 @@ mkdir -p /opt/sriov
 cp sriov-auto-filler.sh /opt/sriov/sriov-auto-filler.sh
 ----
 
-The content of `custom/files/sriov-auto-filler.sh` is a script that can be used to configure the system for SR-IOV and can be downloaded from the following {link-atip-sriov-auto-filler}[link].
+The content of `custom/files/sriov-auto-filler.sh` is a script that can be used to configure the system for SR-IOV and can be downloaded from the following {link-telco-cloud-sriov-auto-filler}[link].
 
 [NOTE]
 ====
@@ -446,7 +446,7 @@ mkdir -p /opt/performance-settings
 cp performance-settings.sh /opt/performance-settings/
 ----
 
-The content of `custom/files/performance-settings.sh` is a script that can be used to configure the system for performance tuning and can be downloaded from the following {link-atip-performance-settings}[link].
+The content of `custom/files/performance-settings.sh` is a script that can be used to configure the system for performance tuning and can be downloaded from the following {link-telco-cloud-performance-settings}[link].
 
 [#add-custom-script-sriov2]
 ===== SR-IOV script
@@ -463,7 +463,7 @@ mkdir -p /opt/sriov
 cp sriov-auto-filler.sh /opt/sriov/sriov-auto-filler.sh
 ----
 
-The content of `custom/files/sriov-auto-filler.sh` is a script that can be used to configure the system for SR-IOV and can be downloaded from the following https://github.com/suse-edge/atip/blob/{release-tag-atip}/telco-examples/edge-clusters/dhcp/eib/custom/files/sriov-auto-filler.sh[link].
+The content of `custom/files/sriov-auto-filler.sh` is a script that can be used to configure the system for SR-IOV and can be downloaded from the following https://github.com/suse-edge/telco-cloud-examples/blob/{release-tag-telco-cloud}/telco-examples/edge-clusters/dhcp/eib/custom/files/sriov-auto-filler.sh[link].
 
 ===== Custom files for air-gap scenarios
 
@@ -535,7 +535,7 @@ $ ./edge-load-oci-artefacts.sh -ad edge-release-oci-tgz-20240705 -r myregistry:5
 
 . Preload with the rest of the images required for SR-IOV:
 +
-.. In this case, we must include the `sr-iov container images for telco workloads (e.g. as a reference, you could get them from {link-atip-sriov-operator-values}[helm-chart values])
+.. In this case, we must include the `sr-iov container images for telco workloads (e.g. as a reference, you could get them from {link-telco-cloud-sriov-operator-values}[helm-chart values])
 +
 [,shell]
 ----
@@ -1515,7 +1515,7 @@ As for the previous example, replace the following variables with actual values,
 
 [NOTE]
 ====
-* You can refer to https://github.com/suse-edge/atip/tree/main/telco-examples/edge-clusters[SUSE Telco Cloud examples repo] for more complex examples, including IPv6 only and dual-stack configurations.
+* You can refer to https://github.com/suse-edge/telco-cloud-examples/tree/main/telco-examples/edge-clusters[SUSE Telco Cloud examples repo] for more complex examples, including IPv6 only and dual-stack configurations.
 * Single-stack IPv6 deployments are in tech preview status and not yet officially supported.
 ====
 

diff --git a/asciidoc/product/atip-features.adoc b/asciidoc/product/atip-features.adoc
@@ -230,7 +230,7 @@ There is another script that can be used to tune the CPU configuration, which ba
 * Set the isolated CPUs latency to the lowest possible value.
 * Delay the vmstat updates to 300 seconds.
 
-The script is available at https://raw.githubusercontent.com/suse-edge/atip/refs/heads/{release-tag-atip}/telco-examples/edge-clusters/dhcp-less/eib/custom/files/performance-settings.sh[SUSE Telco Cloud Examples repository].
+The script is available at https://raw.githubusercontent.com/suse-edge/telco-cloud-examples/refs/heads/{release-tag-telco-cloud}/telco-examples/edge-clusters/dhcp-less/eib/custom/files/performance-settings.sh[SUSE Telco Cloud Examples repository].
 
 [#cni-configuration]
 === CNI Configuration

diff --git a/asciidoc/product/atip-management-cluster.adoc b/asciidoc/product/atip-management-cluster.adoc
@@ -142,7 +142,7 @@ The image `{micro-base-image-iso}` must be downloaded from the https://scc.suse.
 
 You should check the SHA256 checksum of the image to ensure it has not been tampered with. The checksum can be found in the same location where the image was downloaded.
 
-An example of the directory structure can be found in the https://github.com/suse-edge/atip[SUSE Edge GitHub repository under the "telco-examples" folder].
+An example of the directory structure can be found in the https://github.com/suse-edge/telco-cloud-examples[SUSE Edge GitHub repository under the "telco-examples" folder].
 ====
 
 [#mgmt-cluster-image-definition-file]
@@ -1379,4 +1379,4 @@ global:
 
 where `$\{MGMT_CLUSTER_HOSTNAME\}` should be a Fully Qualified Domain Name resolving to your host IP addresses.
 
-For more information visit https://github.com/suse-edge/atip/tree/main/telco-examples/mgmt-cluster/dual-stack[SUSE Edge GitHub repository under the "dual-stack" folder], where an example directory structure can be found.
+For more information visit https://github.com/suse-edge/telco-cloud-examples/tree/main/telco-examples/mgmt-cluster/dual-stack[SUSE Edge GitHub repository under the "dual-stack" folder], where an example directory structure can be found.