From 7229634704eac09a012c8c7277ff6ec81a246ec9 Mon Sep 17 00:00:00 2001
From: Gwen Blum <19484478+gwenblum@users.noreply.github.com>
Date: Fri, 5 Jul 2024 10:18:37 +0200
Subject: [PATCH] Update README.md

---
 .../README.md                                                   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/285-auto-instrument-app-with-riverbed-apm-on-openshift/README.md b/285-auto-instrument-app-with-riverbed-apm-on-openshift/README.md
index fcf2012..16f32af 100644
--- a/285-auto-instrument-app-with-riverbed-apm-on-openshift/README.md
+++ b/285-auto-instrument-app-with-riverbed-apm-on-openshift/README.md
@@ -163,7 +163,7 @@ oc patch deployment -n cookbook-app yourapp -p '{"spec": {"template":{"metadata"
 > For more details about automatic instrumentation, please refer to the readme page of the [Riverbed Operator](https://github.com/riverbed/riverbed-operator).
 
 > [!TIP]
-> The APM instrumentation annotation can also be added directly to the manifest file, for example [app/yourapp-with-apm.yaml](app/yourapp-with-apm.yaml) is annotated, and based on the original manifest [app/yourapp.yaml](app/yourapp.yaml). Then the manifest with APM can be applied:
+> The APM instrumentation annotation can also be added directly to the manifest file of the app. For example with the demo app, [app/yourapp-with-apm.yaml](app/yourapp-with-apm.yaml) is annotated to enable APM instrumentation - the file is based on the original manifest [app/yourapp.yaml](app/yourapp.yaml) without annotation. Then the manifest can be applied to the cluster as usual:
 > ```shell
 > # Deploy YourApp (with APM)
 > oc apply -f https://raw.githubusercontent.com/Aternity/Tech-Community/main/285-auto-instrument-app-with-riverbed-apm-on-openshift/app/yourapp-with-apm.yaml