diff --git a/README.md b/README.md
index 56a8b91..f94beed 100644
--- a/README.md
+++ b/README.md
@@ -1,7 +1,21 @@
 # Jaeger Demo
+Jaeger is a distributed tracing system. It is used for monitoring and troubleshooting microservices-based distributed systems. It is compatible with OpenTracing and OpenTelemetry.
+
+This demo demonstrates a system consisting of 4 services that return a list of albums and their details. The services are written in Go and the demo is deployed to a Kubernetes cluster using Helm.
+
+In this example we will use Jaeger with Elasticsearch v7 as the storage backend.
 
 ## Getting Started
 
+### Prerequisites
+
+- [Docker](https://docs.docker.com/get-docker/)
+- [Kind](https://kind.sigs.k8s.io/docs/user/quick-start/)
+- [Helm](https://helm.sh/docs/intro/install/)
+- [Kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/)
+- [Curl](https://curl.se/download.html)
+- [Go](https://golang.org/doc/install)
+
 ### Prepare The Cluster
 
 #### Cluster Creation
@@ -33,6 +47,8 @@ EOF
 
 #### Ingress Controller For Accessing Services
 
+Install ingress controller for accessing services in the cluster:
+
 ```bash
 kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/main/deploy/static/provider/kind/deploy.yaml
 ```
@@ -42,7 +58,9 @@ kubectl wait --namespace ingress-nginx \
   --selector=app.kubernetes.io/component=controller \
   --timeout=90s
 ```
-#### Jaeger with Elasticsearch v7
+#### Deploying Jaeger with Elasticsearch v7
+
+We will start the Jaeger and Elasticsearch v7 using Helm.
 
 ```bash
 helm repo add jaegertracing https://jaegertracing.github.io/helm-charts
@@ -63,19 +81,40 @@ helm -n default install --wait jaeger jaegertracing/jaeger \
 
 ### Deploy Our Application
 
+By default domain name is `enesonus-127-0-0-1.nip.io`. You can change it by setting `ingress.domain` parameter.
 ```bash
 helm install --wait jaeger-demo oci://ghcr.io/enesonus/jaeger-demo/jaeger-demo --version 0.2.2 \
   --set ingress.domain=enesonus-127-0-0-1.nip.io
 ```
+After this command we will have 4 services running in our cluster. These are:
+* Public Service: Returns details of the album with the given id
+* Price Service: Returns the price of an album with the given id
+* Title Service: Returns the title of an album with the given id
+* Artist Service: Returns the artist name of an album with the given id
+
+### Accessing The Application
 
-### Access The Application
+Now our domain name is `enesonus-127-0-0-1.nip.io`. We can access our application using this domain name.
 
 ```bash
-curl '127.0.0.1:8080/album?id=1'
+curl 'enesonus-127-0-0-1.nip.io/album?id=1'
+```
+This should return an album (id=1) with title, price and artist name. An example is:
+
+```json
+{ 
+  "id":"1", 
+  "title":"Blue Train",
+  "artist":"John Coltrane",
+  "price":56.99
+}
 ```
-
 ## Query Traces
 
 ### Query Traces Using Jaeger UI
 
-Go to http://jaeger-127-0-0-1.nip.io and query traces!
\ No newline at end of file
+We can query traces using Jaeger UI.
+Go to http://jaeger-127-0-0-1.nip.io and query traces!
+Here is a sample trace:
+
+![img_1.png](pics/img_1.png)
\ No newline at end of file
diff --git a/pics/img_1.png b/pics/img_1.png
new file mode 100644
index 0000000..fde401a
Binary files /dev/null and b/pics/img_1.png differ