diff --git a/xos/configurations/cord/README-VTN.md b/xos/configurations/cord/README-VTN.md
index 4ec01e8..b51bae7 100644
--- a/xos/configurations/cord/README-VTN.md
+++ b/xos/configurations/cord/README-VTN.md
@@ -92,16 +92,16 @@
 
 Testing service composition
 
-1) Change the private network template's 'Access' field from None to Direct
-2) Create a Service, Service-A
-3) Enter Slice Admin for Slice-1 and assign it to Service-A
-4) Create a Service, Service-B
-5) Enter Slice Admin for Slice-2 and assign it to Service-B
-6) Enter Service Admin for Service-B, Go to Tenancy Tab
-7) In the 'Provided Tenants' section of Service-B, create a Tenant with Subsciber-Service=Serivce-A. 
-8) Start the VTN Observer. It will send a REST request to VTN app.
-9) Launch tcpdump in one of Slice-2's instances
-10) From Slice-1, start pinging the instance in Slice-2 where you launched tcpdump
-11) You should see the pings arrive and responses sent out. Note that the ping responses will not reach Slice-1, since VTN traffic is unidirectional.
-12) Delete the Tenancy relation you created in Step #7. The ping traffic should no longer appear in the tcpdump.
+1. Change the private network template's 'Access' field from None to Direct
+2. Create a Service, Service-A
+3. Enter Slice Admin for Slice-1 and assign it to Service-A
+4. Create a Service, Service-B
+5. Enter Slice Admin for Slice-2 and assign it to Service-B
+6. Enter Service Admin for Service-B, Go to Tenancy Tab
+7. In the 'Provided Tenants' section of Service-B, create a Tenant with Subsciber-Service=Serivce-A. 
+8. Start the VTN Observer. It will send a REST request to VTN app.
+9. Launch tcpdump in one of Slice-2's instances
+10. From Slice-1, start pinging the instance in Slice-2 where you launched tcpdump
+11. You should see the pings arrive and responses sent out. Note that the ping responses will not reach Slice-1, since VTN traffic is unidirectional.
+12. Delete the Tenancy relation you created in Step #7. The ping traffic should no longer appear in the tcpdump.