From a4d1e849370c67dfae4cc34b01bd23d14b5ed821 Mon Sep 17 00:00:00 2001
From: Simon Brown <1009874+simonbrowndotje@users.noreply.github.com>
Date: Sun, 6 Oct 2024 14:51:26 +0100
Subject: [PATCH] .

---
 index.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/index.md b/index.md
index 8baec71..d3efe4f 100644
--- a/index.md
+++ b/index.md
@@ -75,13 +75,13 @@ which is the wrapper for a software architecture model and views.
 With this in mind, Structurizr workspaces can be created in the following ways:
 
 1. Manually authored:
-   - Using the [Structurizr DSL](/dsl) ([example](https://github.com/structurizr/examples/blob/main/dsl/getting-started/workspace.dsl)).
-   - Using [Structurizr for Java](/java) ([example](https://github.com/structurizr/examples/blob/main/java/src/main/java/com/structurizr/example/GettingStarted.java)) or one of the ports for [.NET, Python, PHP, TypeScript, etc](/community#authoring-tools).
+   - Using the [Structurizr DSL](/dsl).
+   - Using [Structurizr for Java](/java).
 2. Reverse-engineered:
    - Using [Structurizr for Java](/java) or one of the ports for [.NET, Python, PHP, TypeScript, etc](/community#authoring-tools) to write a program to reverse-engineer model information from source code, deployment scripts, your live deployment environment, logs, traces, telemetry data, etc).
 3. Hybrid approach:
    - Use the Structurizr DSL to define software systems and containers, and reverse-engineer component level details via code.
-   - Use code to reverse-engineer a system catalog from Backstage ([example](https://github.com/structurizr/examples/tree/main/enterprise#example-3)), ServiceNow, etc and have teams add container and component level detail via the Structurizr DSL.
+   - Use code to reverse-engineer a system catalog from Backstage, ServiceNow, etc and have teams add container and component level detail via the Structurizr DSL.
 
 ## Rendering tool independent