diff --git a/tutorial/content/labs/instrumentation/automatic/_index.md b/tutorial/content/labs/instrumentation/automatic/_index.md
index e9ca387..75d2abd 100644
--- a/tutorial/content/labs/instrumentation/automatic/_index.md
+++ b/tutorial/content/labs/instrumentation/automatic/_index.md
@@ -5,25 +5,15 @@ draft = false
 weight = 2
 +++
 
-{{< figure src="images/otel_architecture_instrumentation.drawio.svg" width=700 caption="placeholder" >}}
-
 As illustrated by the previous labs, manual instrumentation of an application using the API and SDK can be a labor-intensive process.
-The effort and time required to re-instrument a code base is an often deterrent to getting started.
-While one factor is the financial cost, the prospect of extensive code modifications and having to learn (yet) another telemetry framework (for multiple languages) is often overwhelming to developers.
-Luckily, you are reading this, so we can assume that you are open to change!
+The effort and time required to re-instrument a code base are often deterrents to getting started.
+While one factor is the financial cost, the prospect of extensive code modifications and having to learn another telemetry framework is often overwhelming to developers.
 Moreover, choosing what and knowing how to instrument is often anything but trivial and can take considerable experience.
-Adopting new technologies tends to be (relatively) easy green field environments.
+Adopting new technologies tends to be (relatively) easy in green field environments.
 In reality, things often get more complicated in the face of large amounts of legacy code.
 One factor may simply be the volume of code that needs to be instrumented.
 Another obstacle is that good instrumentation often requires understanding of the application.
 However, it may be the case that the original author of a piece of code is no longer around.
 In summary, even though OpenTelemetry promises to "instrument once and never again", for some, the cost will still be too high.
-Recognizing these burdens, OpenTelemetry tries to simplify the user experience of adoption.
-For example, it is designed to integrate well with pre-existing solutions and allows for incremental migration strategies.
-This section explores the mechanisms OpenTelemetry provides for producing telemetry with zero code changes.
-This is where instrumentation libraries and auto-instrumentation come in.
-
-  - can be used to get started quickly with observability
-  - collects predefined metrics, traces and logs within a library or framework
-  - added after the fact by injecting an agent (or already included inside the library or framework)
-  - requires close to zero code changes
\ No newline at end of file
+Recognizing these burdens, OpenTelemetry tries to simplify adoption as much as possible and allows incremental migration strategies.
+This section explores how OpenTelemetry uses instrumentation libraries and auto-instrumentation to generate predefined metrics, traces and logs with close to zero code changes.
\ No newline at end of file