diff --git a/basic-k8s/go/readme.md b/basic-k8s/go/readme.md
index 315fb1b..df7cef1 100644
--- a/basic-k8s/go/readme.md
+++ b/basic-k8s/go/readme.md
@@ -6,17 +6,20 @@ Make sure you are inside `basic-k8s/go` directory.
 
 ### Do it yourself
 
-Apply the crd present in `deploy` folder.
+Apply the crd.
 ```bash
 kubectl apply -f ../deploy/crd.yaml
 ```
 
-Apply the controller for `Ping`. I am deploying it in `metacontroller` namespace. You can deploy it in any namespace. For that, you have to edit `controller.yaml`.
+Apply the controller for `Ping`. I am deploying it in `metacontroller` namespace. You can deploy it in any namespace.
 ```bash
 kubectl apply -f controller.yaml
 ```
 
 Wait for controller pod to come in running state.
+```bash
+kubectl get pod -n metacontroller
+```
 
 Create a ping cr. Find the sample `Ping` is [here](https://github.com/shovanmaity/metacontroller-by-example/blob/master/basic-k8s/deploy/ping.yaml).
 ```bash
@@ -30,7 +33,7 @@ spec:
 EOF
 ```
 
-Check `Pong` is created or not and validate the `spec.message`. `Pong` cr will be created in the same namespace in which `Ping` cr is present.
+Check the `Pong` cr and validate the message. `Pong` cr will be created in the same namespace in which `Ping` cr is present.
 ```bash
 kubectl get pong -A
 kubectl get pong -A -o=jsonpath='{range .items[*]}{@.spec.message}{"\n"}{end}'
diff --git a/basic-k8s/js/readme.md b/basic-k8s/js/readme.md
index fff5e91..8de1b66 100644
--- a/basic-k8s/js/readme.md
+++ b/basic-k8s/js/readme.md
@@ -6,17 +6,20 @@ Make sure you are inside `basic-k8s/js` directory.
 
 ### Do it yourself
 
-Apply the crd present in `deploy` folder.
+Apply the crd.
 ```bash
 kubectl apply -f ../deploy/crd.yaml
 ```
 
-Apply the controller for `Ping`. I am deploying it in `metacontroller` namespace. You can deploy it in any namespace. For that, you have to edit `controller.yaml`.
+Apply the controller for `Ping`. I am deploying it in `metacontroller` namespace. You can deploy it in any namespace.
 ```bash
 kubectl apply -f controller.yaml
 ```
 
 Wait for controller pod to come in running state.
+```bash
+kubectl get pod -n metacontroller
+```
 
 Create a ping cr. Find the sample `Ping` is [here](https://github.com/shovanmaity/metacontroller-by-example/blob/master/basic-k8s/deploy/ping.yaml).
 ```bash
@@ -30,7 +33,7 @@ spec:
 EOF
 ```
 
-Check `Pong` is created or not and validate the `spec.message`. `Pong` cr will be created in the same namespace in which `Ping` cr is present.
+Check the `Pong` cr and validate the message. `Pong` cr will be created in the same namespace in which `Ping` cr is present.
 ```bash
 kubectl get pong -A
 kubectl get pong -A -o=jsonpath='{range .items[*]}{@.spec.message}{"\n"}{end}'
diff --git a/basic-k8s/python/readme.md b/basic-k8s/python/readme.md
index 92f9252..d9e4a1c 100644
--- a/basic-k8s/python/readme.md
+++ b/basic-k8s/python/readme.md
@@ -6,17 +6,20 @@ Make sure you are inside `basic-k8s/python` directory.
 
 ### Do it yourself
 
-Apply the crd and controller present in `deploy` folder.
+Apply the crd and controller.
 ```bash
 kubectl apply -f ../deploy/crd.yaml
 ```
 
-Apply the controller for `Ping`. I am deploying it in `metacontroller` namespace. You can deploy it in any namespace. For that, you have to edit `controller.yaml`.
+Apply the controller for `Ping`. I am deploying it in `metacontroller` namespace. You can deploy it in any namespace.
 ```bash
 kubectl apply -f controller.yaml
 ```
 
 Wait for controller pod to come in running state.
+```bash
+kubectl get pod -n metacontroller
+```
 
 Create a ping cr. Find the sample `Ping` is [here](https://github.com/shovanmaity/metacontroller-by-example/blob/master/basic-k8s/deploy/ping.yaml).
 ```bash
@@ -30,7 +33,7 @@ spec:
 EOF
 ```
 
-Check `Pong` is created or not and validate the `spec.message`. `Pong` cr will be created in the same namespace in which `Ping` cr is present.
+Check the `Pong` cr and validate the message. `Pong` cr will be created in the same namespace in which `Ping` cr is present.
 ```bash
 kubectl get pong -A
 kubectl get pong -A -o=jsonpath='{range .items[*]}{@.spec.message}{"\n"}{end}'
diff --git a/basic/go/readme.md b/basic/go/readme.md
index 025359a..86858cf 100644
--- a/basic/go/readme.md
+++ b/basic/go/readme.md
@@ -15,7 +15,7 @@ spec:
         url: http://192.168.1.15:8080/sync
 ```
 
-Apply the crd and controller present in `deploy` folder.
+Apply the crd and controller.
 ```bash
 kubectl apply -f ../deploy/controller.yaml
 kubectl apply -f ../deploy/crd.yaml
@@ -38,7 +38,7 @@ spec:
 EOF
 ```
 
-Check `Pong` is created or not and validate the `spec.message`. `Pong` cr will be created in the same namespace in which `Ping` cr is present.
+Check the `Pong` cr and validate the message. `Pong` cr will be created in the same namespace in which `Ping` cr is present.
 ```bash
 kubectl get pong -A
 kubectl get pong -A -o=jsonpath='{range .items[*]}{@.spec.message}{"\n"}{end}'
diff --git a/basic/js/readme.md b/basic/js/readme.md
index 316ded3..f5cb6f6 100644
--- a/basic/js/readme.md
+++ b/basic/js/readme.md
@@ -15,7 +15,7 @@ spec:
         url: http://192.168.1.15:8080/sync
 ```
 
-Apply the crd and controller present in `deploy` folder.
+Apply the crd and controller.
 ```bash
 kubectl apply -f ../deploy/controller.yaml
 kubectl apply -f ../deploy/crd.yaml
@@ -39,7 +39,7 @@ spec:
 EOF
 ```
 
-Check `Pong` is created or not and validate the `spec.message`. `Pong` cr will be created in the same namespace in which `Ping` cr is present.
+Check the `Pong` cr and validate the message. `Pong` cr will be created in the same namespace in which `Ping` cr is present.
 ```bash
 kubectl get pong -A
 kubectl get pong -A -o=jsonpath='{range .items[*]}{@.spec.message}{"\n"}{end}'
diff --git a/basic/python/readme.md b/basic/python/readme.md
index dc3fefe..6224a0c 100644
--- a/basic/python/readme.md
+++ b/basic/python/readme.md
@@ -15,7 +15,7 @@ spec:
         url: http://192.168.1.15:8080/sync
 ```
 
-Apply the crd and controller present in `deploy` folder.
+Apply the crd and controller.
 ```bash
 kubectl apply -f ../deploy/controller.yaml
 kubectl apply -f ../deploy/crd.yaml
@@ -38,7 +38,7 @@ spec:
 EOF
 ```
 
-Check `Pong` is created or not and validate the `spec.message`. `Pong` cr will be created in the same namespace in which `Ping` cr is present.
+Check the `Pong` cr and validate the message. `Pong` cr will be created in the same namespace in which `Ping` cr is present.
 ```bash
 kubectl get pong -A
 kubectl get pong -A -o=jsonpath='{range .items[*]}{@.spec.message}{"\n"}{end}'
diff --git a/composite-controller/generate-selector/readme.md b/composite-controller/generate-selector/readme.md
index 9c452fd..4dc4565 100644
--- a/composite-controller/generate-selector/readme.md
+++ b/composite-controller/generate-selector/readme.md
@@ -13,11 +13,6 @@ Make sure you are inside `composite-controller/generate-selector` directory.
 
 ### Do it yourself
 
-Apply the crd.
-```bash
-kubectl apply -f deploy/crd.yaml
-```
-
 ### Case-1
 
 Edit the `deploy/case-1/controller.yaml` file and update the URL.
@@ -34,6 +29,11 @@ Apply the controller.
 kubectl apply -f deploy/case-1/controller.yaml
 ```
 
+Apply the crd.
+```bash
+kubectl apply -f deploy/crd.yaml
+```
+
 Create a ping cr using -
 ```bash
 cat <<EOF | kubectl apply -f -
@@ -77,6 +77,11 @@ Apply the controller.
 kubectl apply -f deploy/case-2/controller.yaml
 ```
 
+Apply the crd.
+```bash
+kubectl apply -f deploy/crd.yaml
+```
+
 Create a ping cr using -
 ```bash
 cat <<EOF | kubectl apply -f -
diff --git a/composite-controller/resync-period/readme.md b/composite-controller/resync-period/readme.md
index c0e3c0b..4e567cd 100644
--- a/composite-controller/resync-period/readme.md
+++ b/composite-controller/resync-period/readme.md
@@ -39,9 +39,7 @@ spec:
 EOF
 ```
 
-Try the below processes -
-
-- Check the logs of python file execution.
+Check the logs of python file execution.
 
 ### Cleanup
 
diff --git a/composite-controller/spec-selector/readme.md b/composite-controller/spec-selector/readme.md
index bd1c36a..ddc300f 100644
--- a/composite-controller/spec-selector/readme.md
+++ b/composite-controller/spec-selector/readme.md
@@ -75,7 +75,10 @@ Execute python file.
 python3 python/case-1/sync.py
 ```
 
-Check for pong cr `kubectl get pong -A`. You will not find any pong as we are not setting label in pong cr in python code `case-1/sync.py`.
+Check for pong cr. You will not find any pong as we are not setting label in pong cr in python code `case-1/sync.py`.
+```bash
+kubectl get pong -A
+```
 
 ### Case-2
 
@@ -84,7 +87,10 @@ Stop the python file execution and execute another python file
 python3 python/case-2/sync.py
 ```
 
-Check for pong cr `kubectl get pong -A`. You will find one pong.
+Check for pong cr. You will find one pong.
+```bash
+kubectl get pong -A
+```
 
 Run the below command and saw the output
 ```
@@ -113,7 +119,10 @@ kubectl get pong -A -o=jsonpath='{range .items[*]}{@.metadata.ownerReferences}{"
 kubectl get ping -A -o=jsonpath='{range .items[*]}{@.status.replicas}{"\n"}{end}'
 ```
 
-Remove the label from newly created pong cr `kubectl label pong shovan-tmp name-`.
+Remove the label from newly created pong cr
+```bash
+kubectl label pong shovan-tmp name-
+```
 
 Run the below command and saw the output
 ```
@@ -121,7 +130,10 @@ kubectl get pong -A -o=jsonpath='{range .items[*]}{@.metadata.ownerReferences}{"
 kubectl get ping -A -o=jsonpath='{range .items[*]}{@.status.replicas}{"\n"}{end}'
 ```
 
-Delete the new pong cr `kubectl delete pong shovan-tmp`.
+Delete the new pong cr
+```bash
+kubectl delete pong shovan-tmp
+```
 
 ### Case-3
 
@@ -130,9 +142,15 @@ Stop the python file execution and execute another python file
 python3 python/case-3/sync.py
 ```
 
-Check the pong cr `kubectl get pong -A`
+Check the pong cr
+```bash
+kubectl get pong -A
+```
 
-Check the ping cr's replicas `kubectl get ping -A -o=jsonpath='{range .items[*]}{@.status.replicas}{"\n"}{end}'`
+Check the ping cr's replicas
+```bash
+kubectl get ping -A -o=jsonpath='{range .items[*]}{@.status.replicas}{"\n"}{end}'
+```
 
 Create a new pong with same label
 ```bash
@@ -149,7 +167,10 @@ spec:
 EOF
 ```
 
-Check the ping cr's replicas `kubectl get ping -A -o=jsonpath='{range .items[*]}{@.status.replicas}{"\n"}{end}'`
+Check the ping cr's replicas
+```bash
+kubectl get ping -A -o=jsonpath='{range .items[*]}{@.status.replicas}{"\n"}{end}'
+```
 
 It will be 1, newly created pong cr will be deleted as python code in `case-3/ping.py` declines to list that cr.
 
diff --git a/composite-controller/sync-finalize-hook/readme.md b/composite-controller/sync-finalize-hook/readme.md
index b6567fb..c4f8ca0 100644
--- a/composite-controller/sync-finalize-hook/readme.md
+++ b/composite-controller/sync-finalize-hook/readme.md
@@ -71,11 +71,20 @@ spec:
 EOF
 ```
 
-Try the below processes -
+Get the `metadata.finalizers` of the ping cr.
+```bash
+kubectl get ping -o=jsonpath='{range .items[*]}{@.metadata.finalizers}{"\n"}{end}'
+```
 
-- Get the `metadata.finalizers` of the ping cr using `kubectl get ping -o=jsonpath='{range .items[*]}{@.metadata.finalizers}{"\n"}{end}'`.
-- Delete the `Ping` cr using `kubectl delete ping -A --all`.
-- List `Pong` cr using `kubectl get ping -A`.
+Delete the `Ping` cr.
+```bash
+kubectl delete ping -A --all
+```
+
+List `Pong` cr.
+```bash
+kubectl get ping -A
+```
 
 ### Cleanup
 
diff --git a/composite-controller/target-status/readme.md b/composite-controller/target-status/readme.md
index ce9e62d..0636126 100644
--- a/composite-controller/target-status/readme.md
+++ b/composite-controller/target-status/readme.md
@@ -1,5 +1,6 @@
 ### Concept
 
+A JSON object that will completely replace the status field within the target object. Leave unspecified or null to avoid changing status You can specify this in the response of sync hook.
 
 ### Prerequisite
 
@@ -39,7 +40,7 @@ spec:
 EOF
 ```
 
-Check the status of ping cr -
+Check the status of ping cr
 ```yaml
 kubectl get ping -A -o=jsonpath='{range .items[*]}{@.status}{"\n"}{end}'
 ```
diff --git a/composite-controller/update-strategy-inplace/readme.md b/composite-controller/update-strategy-inplace/readme.md
index a331c59..1203dc5 100644
--- a/composite-controller/update-strategy-inplace/readme.md
+++ b/composite-controller/update-strategy-inplace/readme.md
@@ -8,6 +8,8 @@ Make sure metacontroller is [installed](https://github.com/shovanmaity/metacontr
 
 Make sure you are inside `composite-controller/update-strategy-inplace` directory.
 
+### Do it yourself
+
 Edit the `deploy/controller.yaml` file and update the webhook URL.
 ```yaml
 spec:
@@ -40,10 +42,15 @@ spec:
 EOF
 ```
 
-Try the below processes -
+Get the `metadata.uid` of the pong cr.
+```bash
+kubectl get pong -o=jsonpath='{range .items[*]}{@.metadata.uid}{"\n"}{end}'
+```
 
-- Get the `metadata.uid` of the pong object using `kubectl get pong -o=jsonpath='{range .items[*]}{@.metadata.uid}{"\n"}{end}'`.
-- Edit the ping and change the `spec.name` then check `metadata.uid` of the pong object it should be same and message should contain updated name. Get the message using `kubectl get pong -o=jsonpath='{range .items[*]}{@.spec.message}{"\n"}{end}'`.
+Edit the ping and change the `spec.name` then check `metadata.uid` of the pong cr. It should be same and message should contain updated name.
+```bash
+kubectl get pong -o=jsonpath='{range .items[*]}{@.spec.message}{"\n"}{end}'
+```
 
 ### Cleanup
 
diff --git a/composite-controller/update-strategy-ondelete/readme.md b/composite-controller/update-strategy-ondelete/readme.md
index be38cbe..6b5cfc8 100644
--- a/composite-controller/update-strategy-ondelete/readme.md
+++ b/composite-controller/update-strategy-ondelete/readme.md
@@ -2,12 +2,14 @@
 
 Metacontroller allows define upgrade strategy for chieldren. For `OnDelete` - it does not update existing children unless they get deleted by some other agent.
 
-Make sure metacontroller is [installed](https://github.com/shovanmaity/metacontroller-by-example/tree/master/metacontroller).
-
 ### Prerequisite
 
+Make sure metacontroller is [installed](https://github.com/shovanmaity/metacontroller-by-example/tree/master/metacontroller).
+
 Make sure you are inside `composite-controller/update-strategy-ondelete` directory.
 
+### Do it yourself
+
 Edit the `deploy/controller.yaml` file and update the webhook URL.
 ```yaml
 spec:
@@ -17,8 +19,6 @@ spec:
         url: http://192.168.1.15:8080/sync
 ```
 
-### Do it yourself
-
 Apply the crd and controller.
 ```bash
 kubectl apply -f deploy/crd.yaml
@@ -42,10 +42,12 @@ spec:
 EOF
 ```
 
-Try the below processes -
+Edit the ping and change the `spec.name` then check the pong object it's message should not contain updated name
+```bash
+kubectl get pong -o=jsonpath='{range .items[*]}{@.spec.message}{"\n"}{end}'
+```
 
-- Edit the ping and change the `spec.name` then check the pong object it's message should not contain updated name. Get the message using `kubectl get pong -o=jsonpath='{range .items[*]}{@.spec.message}{"\n"}{end}'`.
-- Delete the pong object then check the pong object it's message should contain updated name.
+Delete the pong object then check the pong object it's message should contain updated name.
 
 ### Cleanup
 
diff --git a/composite-controller/update-strategy-recreate/readme.md b/composite-controller/update-strategy-recreate/readme.md
index 3c6bde9..96f9725 100644
--- a/composite-controller/update-strategy-recreate/readme.md
+++ b/composite-controller/update-strategy-recreate/readme.md
@@ -42,10 +42,15 @@ spec:
 EOF
 ```
 
-Try the below processes -
+Get the `metadata.uid` of the pong cr.
+```bash
+kubectl get pong -o=jsonpath='{range .items[*]}{@.metadata.uid}{"\n"}{end}'
+```
 
-- Get the `metadata.uid` of the pong object using `kubectl get pong -o=jsonpath='{range .items[*]}{@.metadata.uid}{"\n"}{end}'`.
-- Edit the ping and change the `spec.name` then check `metadata.uid` of the pong object it should not be same and message should contain updated name. Get the message using `kubectl get pong -o=jsonpath='{range .items[*]}{@.spec.message}{"\n"}{end}'`.
+Edit the ping and change the `spec.name` then check `metadata.uid` of the pong object it should not be same and message should contain updated name.
+```bash
+kubectl get pong -o=jsonpath='{range .items[*]}{@.spec.message}{"\n"}{end}'
+```
 
 ### Cleanup
 
diff --git a/decorator-controller/annotation-selector/readme.md b/decorator-controller/annotation-selector/readme.md
index ae3117d..13697e6 100644
--- a/decorator-controller/annotation-selector/readme.md
+++ b/decorator-controller/annotation-selector/readme.md
@@ -42,12 +42,24 @@ spec:
 EOF
 ```
 
-Try
+Get pong and there will be no pong.
+```bash
+kubectl get pong -A
+```
+
+Annotate the ping object.
+```bash
+kubectl annotate ping include="true" -A --all
+```
+
+Now get pong cr you will be able to get a pong cr.
+```bash
+kubectl get pong -A
+```
+
+Remove the annotation in the ping cr and then edit it`.spec.name` changes will not be reflected in the pong cr.
 
-- Get pong and there will be no pong. Then annotate the ping object according to your controller.
-- Now get pong object you will be able to get a pong cr.
-- Remove the annotation in the ping cr and then edit it(`.spec.name`) changes will not be reflected in the pong cr.
-- Add the annotation back and the adit the ping object(`.spec.name`) changes will be reflected in the pong cr.
+Add the annotation back and the adit the ping object`.spec.name` changes will be reflected in the pong cr.
 
 ### Cleanup
 
diff --git a/decorator-controller/label-selector/readme.md b/decorator-controller/label-selector/readme.md
index 6503a2f..a3314f2 100644
--- a/decorator-controller/label-selector/readme.md
+++ b/decorator-controller/label-selector/readme.md
@@ -42,12 +42,24 @@ spec:
 EOF
 ```
 
-Try
+Get pong and there will be no pong cr.
+```bash
+kubectl get pong -A
+```
+
+Label the ping cr.
+```bash
+kubectl label ping include="true" -A --all
+```
+
+Now get pong cr you will be able to get a pong cr.
+```bash
+kubectl get pong -A
+```
+
+Remove the label in the ping cr and then edit it`.spec.name` changes will not be reflected in the pong cr.
 
-- Get pong and there will be no pong. Then label the ping cr according to your controller file.
-- Now Get pong cr you will be able to get a pong cr.
-- Remove the label in the ping cr and then edit it(`.spec.name`) changes will not be reflected in the pong cr.
-- Add the label back and the adit the ping cr(`.spec.name`) changes will be reflected in the pong cr.
+Add the label back and the adit the ping cr`.spec.name` changes will be reflected in the pong cr.
 
 ### Cleanup
 
diff --git a/decorator-controller/resync-period/readme.md b/decorator-controller/resync-period/readme.md
index e8632fa..2ccf209 100644
--- a/decorator-controller/resync-period/readme.md
+++ b/decorator-controller/resync-period/readme.md
@@ -39,9 +39,7 @@ spec:
 EOF
 ```
 
-Try the below processes -
-
-- Check the logs of python file execution.
+Check the logs of python file execution.
 
 ### Cleanup
 
diff --git a/decorator-controller/sync-finalize-hook/readme.md b/decorator-controller/sync-finalize-hook/readme.md
index e737fd5..585431e 100644
--- a/decorator-controller/sync-finalize-hook/readme.md
+++ b/decorator-controller/sync-finalize-hook/readme.md
@@ -75,11 +75,20 @@ spec:
 EOF
 ```
 
-Try the below processes -
+Get the `metadata.finalizers` of the ping cr.
+```bash
+kubectl get ping -o=jsonpath='{range .items[*]}{@.metadata.finalizers}{"\n"}{end}'
+```
 
-- Get the `metadata.finalizers` of the ping cr using `kubectl get ping -o=jsonpath='{range .items[*]}{@.metadata.finalizers}{"\n"}{end}'`.
-- Delete the `Ping` cr using `kubectl delete ping -A --all`.
-- List `Pong` cr using `kubectl get ping -A`.
+Delete the `Ping` cr.
+```bash
+kubectl delete ping -A --all
+```
+
+List `Pong` cr.
+```bash
+kubectl get ping -A
+```
 
 ### Cleanup
 
diff --git a/decorator-controller/target-annotations/readme.md b/decorator-controller/target-annotations/readme.md
index 8f01e54..a1bd8a7 100644
--- a/decorator-controller/target-annotations/readme.md
+++ b/decorator-controller/target-annotations/readme.md
@@ -1,5 +1,6 @@
 ### Concept
 
+A map of key-value pairs for annotations to set on the target object. You can specify this in the response of sync hook.
 
 ### Prerequisite
 
@@ -41,7 +42,7 @@ spec:
 EOF
 ```
 
-Check the status of ping cr -
+Check the status of ping cr
 ```yaml
 kubectl get ping -A -o=jsonpath='{range .items[*]}{@.metadata.annotations}{"\n"}{end}'
 ```
diff --git a/decorator-controller/target-labels/readme.md b/decorator-controller/target-labels/readme.md
index 9fd799b..70d7a3a 100644
--- a/decorator-controller/target-labels/readme.md
+++ b/decorator-controller/target-labels/readme.md
@@ -1,5 +1,6 @@
 ### Concept
 
+A map of key-value pairs for labels to set on the target object. You can specify this in the response of sync hook.
 
 ### Prerequisite
 
@@ -41,7 +42,7 @@ spec:
 EOF
 ```
 
-Check the status of ping cr -
+Check the status of ping cr
 ```yaml
 kubectl get ping -A -o=jsonpath='{range .items[*]}{@.metadata.labels}{"\n"}{end}'
 ```
diff --git a/decorator-controller/target-status/readme.md b/decorator-controller/target-status/readme.md
index 81ce265..cee5029 100644
--- a/decorator-controller/target-status/readme.md
+++ b/decorator-controller/target-status/readme.md
@@ -1,5 +1,6 @@
 ### Concept
 
+A JSON object that will completely replace the status field within the target object. Leave unspecified or null to avoid changing status. You can specify this in the response of sync hook.
 
 ### Prerequisite
 
@@ -39,7 +40,7 @@ spec:
 EOF
 ```
 
-Check the status of ping cr -
+Check the status of ping cr
 ```yaml
 kubectl get ping -A -o=jsonpath='{range .items[*]}{@.status}{"\n"}{end}'
 ```
diff --git a/decorator-controller/update-strategy-inplace/readme.md b/decorator-controller/update-strategy-inplace/readme.md
index 29be079..20c9a60 100644
--- a/decorator-controller/update-strategy-inplace/readme.md
+++ b/decorator-controller/update-strategy-inplace/readme.md
@@ -42,10 +42,15 @@ spec:
 EOF
 ```
 
-Try the below processes -
+Get the `metadata.uid` of the pong cr.
+```bash
+kubectl get pong -o=jsonpath='{range .items[*]}{@.metadata.uid}{"\n"}{end}'
+```
 
-- Get the `metadata.uid` of the pong object using `kubectl get pong -o=jsonpath='{range .items[*]}{@.metadata.uid}{"\n"}{end}'`.
-- Edit the ping and change the `spec.name` then check `metadata.uid` of the pong object it should be same and message should contain updated name. Get the message using `kubectl get pong -o=jsonpath='{range .items[*]}{@.spec.message}{"\n"}{end}'`.
+Edit the ping and change the `spec.name` then check `metadata.uid` of the pong object it should be same and message should contain updated name.
+```bash
+kubectl get pong -o=jsonpath='{range .items[*]}{@.spec.message}{"\n"}{end}'
+```
 
 ### Cleanup
 
diff --git a/decorator-controller/update-strategy-ondelete/readme.md b/decorator-controller/update-strategy-ondelete/readme.md
index 8ac4bf2..091a703 100644
--- a/decorator-controller/update-strategy-ondelete/readme.md
+++ b/decorator-controller/update-strategy-ondelete/readme.md
@@ -42,10 +42,12 @@ spec:
 EOF
 ```
 
-Try the below processes -
+Edit the ping and change the `spec.name` then check the pong object it's message should not contain updated name.
+```bash
+kubectl get pong -o=jsonpath='{range .items[*]}{@.spec.message}{"\n"}{end}'
+```
 
-- Edit the ping and change the `spec.name` then check the pong object it's message should not contain updated name. Get the message using `kubectl get pong -o=jsonpath='{range .items[*]}{@.spec.message}{"\n"}{end}'`.
-- Delete the pong object then check the pong object it's message should contain updated name.
+Delete the pong object then check the pong object it's message should contain updated name.
 
 ### Cleanup
 
diff --git a/decorator-controller/update-strategy-recreate/readme.md b/decorator-controller/update-strategy-recreate/readme.md
index d922207..a9cc171 100644
--- a/decorator-controller/update-strategy-recreate/readme.md
+++ b/decorator-controller/update-strategy-recreate/readme.md
@@ -6,7 +6,7 @@ Metacontroller allows define upgrade strategy for chieldren. For `Recreate` - it
 
 Make sure metacontroller is [installed](https://github.com/shovanmaity/metacontroller-by-example/tree/master/metacontroller).
 
-Make sure you are inside `decorator-controller/update-strategy-ondelete` directory.
+Make sure you are inside `decorator-controller/update-strategy-recreate` directory.
 
 ### Do it yourself
 
@@ -42,10 +42,15 @@ spec:
 EOF
 ```
 
-Try the below processes -
+Get the `metadata.uid` of the pong cr.
+```bash
+kubectl get pong -o=jsonpath='{range .items[*]}{@.metadata.uid}{"\n"}{end}'
+```
 
-- Get the `metadata.uid` of the pong object using `kubectl get pong -o=jsonpath='{range .items[*]}{@.metadata.uid}{"\n"}{end}'`.
-- Edit the ping and change the `spec.name` then check `metadata.uid` of the pong object it should not be same and message should contain updated name. Get the message using `kubectl get pong -o=jsonpath='{range .items[*]}{@.spec.message}{"\n"}{end}'`.
+Edit the ping and change the `spec.name` then check `metadata.uid` of the pong object it should not be same and message should contain updated name.
+```bash
+kubectl get pong -o=jsonpath='{range .items[*]}{@.spec.message}{"\n"}{end}'
+```
 
 ### Cleanup