From 7d1d965b8477d0fc0ecbea031de301d413533d12 Mon Sep 17 00:00:00 2001
From: Rob Austin <rob.austin@boundedbuffer>
Date: Mon, 13 Oct 2014 13:10:51 +0100
Subject: [PATCH] added Lock contention

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 0c595d110..bcbbbb674 100644
--- a/README.md
+++ b/README.md
@@ -844,7 +844,6 @@ about 115 K Chronicle Map lookups per second.
 If you see the following warning :
 
 ``` java 
-
 WARNING:net.openhft.lang.io.AbstractBytes tryLockNanosLong0
 WARNING: Thread-2, to obtain a lock took 0.129 seconds
 ``` 
@@ -860,11 +859,12 @@ So, If you set a large number of actual segments, this will reduce your lock con
 
 See the example below to see how to set the number of segments :
 
+``` java 
 ChronicleMap<Long, String> map = ChronicleMapBuilder.of(Long.class, String.class)
    .entries(100)
    .actualSegments(100)    // set your number of segments here
    .create();
-
+```  
  
 Reducing lock contention will make this warning message go away, but this message maybe more of a symptom 
 of a general problem with what the system is doing, so you may experience a delay anyway.