From 924b3dffcff19f5ecc97f8cdd878a709c21bd8d1 Mon Sep 17 00:00:00 2001
From: Mara Kiefer <8320933+mnkiefer@users.noreply.github.com>
Date: Mon, 16 Oct 2023 20:57:18 +0200
Subject: [PATCH] Update README.md

Co-authored-by: sjvans <30337871+sjvans@users.noreply.github.com>
---
 README.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 3efb78d..6bf54d3 100644
--- a/README.md
+++ b/README.md
@@ -23,7 +23,10 @@ npm add @cap-js/change-tracking
 Next, we need to identify what should be change-tracked by annotating respective entities and elements in our model with the `@changelog` annotation. Following the [best practice of separation of concerns](https://cap.cloud.sap/docs/guides/domain-modeling#separation-of-concerns), we do so in a separate file _srv/change-tracking.cds_:
 
 ```cds
-using { sap.capire.incidents as my } from './processor-service';
+using {
+  sap.capire.incidents as my,
+  ProcessorService
+} from './processor-service';
 
 annotate my.Incidents with @title: 'Incidents';
 annotate my.Conversations with @title: 'Conversations';