diff --git a/docs/architecture.mdx b/docs/architecture.mdx
index 4fa4a9b50..53dde7071 100644
--- a/docs/architecture.mdx
+++ b/docs/architecture.mdx
@@ -34,7 +34,9 @@ The different microservices communicate via Kubernetes API server (see
The following diagram shows the architecture of the Odigos observability system.
-![Odigos Architecture](/images/Odigos_Arch.jpeg)
+
+
+
## Instrumentor
diff --git a/docs/backends/datadog.mdx b/docs/backends/datadog.mdx
index 370e61399..8fb9b6062 100644
--- a/docs/backends/datadog.mdx
+++ b/docs/backends/datadog.mdx
@@ -5,11 +5,16 @@ title: "Datadog"
## Obtaining an API Key
On the left sidebar, click on your username and then click on **Organization Settings**
-![](/backends/images/datadog1.png)
+
+
+
+
Click on **API Keys** and then click on **New Key** and give it a name.
-![](/backends/images/datadog2.png)
+
+
+
## Configuring the Datadog Backend
diff --git a/docs/backends/grafanacloud.mdx b/docs/backends/grafanacloud.mdx
index 763491963..29632c471 100644
--- a/docs/backends/grafanacloud.mdx
+++ b/docs/backends/grafanacloud.mdx
@@ -5,12 +5,18 @@ title: "Grafana Cloud"
Currently, Odigos supports Grafana Cloud as a three data source types: Prometheus, Loki, and Tempo.
All the connection details can be found at [grafana.com](grafana.com) under **My Account**
-![](/backends/images/grafanacloud1.png)
+
+
+
+
## Configuring Grafana Cloud managed Loki
Press **Details** under the Loki data source
-![](/backends/images/grafanacloud2.png)
+
+
+
+
Enter the following settings into Odigos UI:
@@ -21,7 +27,10 @@ Enter the following settings into Odigos UI:
## Configuring Grafana Cloud managed Prometheus
Press **Details** under the Prometheus data source
-![](/backends/images/grafanacloud3.png)
+
+
+
+
Insert into Odigos the following settings:
@@ -32,7 +41,10 @@ Insert into Odigos the following settings:
## Configuring Grafana Cloud managed Tempo
Press **Details** under the Tempo data source
-![](/backends/images/grafanacloud4.png)
+
+
+
+
Insert into Odigos the following settings:
diff --git a/docs/backends/honeycomb.mdx b/docs/backends/honeycomb.mdx
index 6e27d8169..bdfd4c3ee 100644
--- a/docs/backends/honeycomb.mdx
+++ b/docs/backends/honeycomb.mdx
@@ -7,7 +7,10 @@ title: "Honeycomb"
[Click here](https://ui.honeycomb.io/odigos/environments/test/api_keys) to go to Honeycomb API Keys page and click on **Create API Key**
Make sure the API Key is permitted to **Send Events** to Honeycomb.
-![](/backends/images/honeycomb.png)
+
+
+
+
## Configuring Honeycomb Backend
diff --git a/docs/backends/newrelic.mdx b/docs/backends/newrelic.mdx
index 9e902db2c..c8ed8288e 100644
--- a/docs/backends/newrelic.mdx
+++ b/docs/backends/newrelic.mdx
@@ -6,11 +6,15 @@ title: "New Relic"
On the left sidebar, click on your account name and select **API Keys** and then click on **Create a key**.
-![](/backends/images/newrelic1.png)
+
+
+
For key type select **Ingest - License**, give a name to your key and press **Create a key**.
-![](/backends/images/newrelic2.png)
+
+
+
## Configuring New Relic Backend
diff --git a/docs/backends/splunk.mdx b/docs/backends/splunk.mdx
index b2373dcd6..6e3a3e334 100644
--- a/docs/backends/splunk.mdx
+++ b/docs/backends/splunk.mdx
@@ -5,10 +5,16 @@ title: "Splunk"
## Obtaining Access Token
Go to **Settings** then **Access Tokens**. and click **Create New Token**
-![](/backends/images/splunk1.png)
+
+
+
+
Give the token a name and select **Ingest Token** for the authorization scope and click create.
-![](/backends/images/splunk2.png)
+
+
+
+
## Configuring the Splunk Backend
diff --git a/docs/instrumenting.mdx b/docs/instrumenting.mdx
index 3603e8fbc..c0b7dbf3a 100644
--- a/docs/instrumenting.mdx
+++ b/docs/instrumenting.mdx
@@ -8,7 +8,9 @@ sidebarTitle: "Generating Traces"
You should now see the following page:
-![Select target applications](/images/choose_apps.png)
+
+
+
Select all the applications in the `default` namespace and click `Next`.
@@ -20,7 +22,9 @@ Selecting **Apply for future apps** will automatically generate distributed trac
In the next step, you will be asked to select a destination for your traces.
Scroll down to the self hosted destinations and click on **Jaeger**.
-![Select Jaeger](/images/choose_jaeger.png)
+
+
+
#### Connection details