diff --git a/documentation/blog/2025-07-10-try-out-securecodebox-as-a-service.md b/documentation/blog/2025-07-10-try-out-securecodebox-as-a-service.md
index 6928660ef..240794290 100644
--- a/documentation/blog/2025-07-10-try-out-securecodebox-as-a-service.md
+++ b/documentation/blog/2025-07-10-try-out-securecodebox-as-a-service.md
@@ -16,7 +16,7 @@ description: We are launching secureCodeBox as a Service so that you can try it
 image: /img/blog/2025-07-10-scbaas-form.jpg
 ---
 
-Have you ever wanted to try out _secureCodeBox_ but don't have a Kubernetes cluster on hand? We have a solution for that: [secureCodeBox as a Service][scbaas].
+Have you ever wanted to try out _secureCodeBox_ but don't have a Kubernetes cluster on hand? We have a solution for that: [secureCodeBox as a Service](https://scb.iteratec.de).
 
 ![secureCodeBox as a Service initial form](/img/blog/2025-07-10-scbaas-form.jpg)
 
@@ -32,7 +32,7 @@ But one of the major concerns we often heard in the past was:
 
 Setting up a Kubernetes cluster is a major concern if you're not used to it. What seems to be a no-brainer for DevOps Engineers may be show-stopper for e.g. security engineers, pentesters, CISOs, Product Owners, etc. who just want to try it out.
 
-That's the reason why we decided last year to start building [secureCodeBox as a service][scbaas], and now it's in a state where we can put it in front of the public. For that, we set up a dedicated Kubernetes cluster and developed a simple Web UI to interface with secureCodeBox. So you don't need to mess around with `kubectl` on command line 🤗
+That's the reason why we decided last year to start building [secureCodeBox as a service](https://scb.iteratec.de), and now it's in a state where we can put it in front of the public. For that, we set up a dedicated Kubernetes cluster and developed a simple Web UI to interface with secureCodeBox. So you don't need to mess around with `kubectl` on command line 🤗
 
 At the moment, we do a [very basic cascading scan](https://scb.iteratec.de/about):
 
@@ -58,6 +58,4 @@ Also, we require you to accept a very lightweight [terms of use](https://scb.ite
 
 ## Why Hosted on a Company Domain?
 
-Maybe you recognized that [secureCodeBox as a service][scbaas] is hosted under a company domain of the [iteratec GmbH](https://www.iteratec.com). _iteratec_ is the main sponsor of _secureCodeBox_. The reason why we host the service there instead under the open source project's domain is for legal reasons. Since we're located in Germany, and we have something called the "Hackerparagraph" (you can be sued for scanning if not permitted by the owner of the scanned systems). To prevent the individual maintainers or maybe the [OWASP](https://www.owasp.org) getting sued, we needed a legal entity to be in charge and as a legal party for the terms of use. Of course, we asked a lawyer. 😉
-
-[scbaas]: https://scb.iteratec.de
+Maybe you recognized that [secureCodeBox as a service](https://scb.iteratec.de) is hosted under a company domain of the [iteratec GmbH](https://www.iteratec.com). _iteratec_ is the main sponsor of _secureCodeBox_. The reason why we host the service there instead under the open source project's domain is for legal reasons. Since we're located in Germany, and we have something called the "Hackerparagraph" (you can be sued for scanning if not permitted by the owner of the scanned systems). To prevent the individual maintainers or maybe the [OWASP](https://www.owasp.org) getting sued, we needed a legal entity to be in charge and as a legal party for the terms of use. Of course, we asked a lawyer. 😉