fix #993 better fields breaking changes documentation

Author: Mpdreamz

docs/contents/breaking-changes.md

@@ -90,6 +90,7 @@ Prior to Elasticsearch 1.0, you could specify to return only certain fields and
     }
     ...
 
+
 In many case this could be mapped to the type of DTO you give search (i.e in `.Search<DTO>()`). Elasticsearch 1.0 now always returns the fields as arrays.
 
     ...
@@ -99,7 +100,11 @@ In many case this could be mapped to the type of DTO you give search (i.e in `.S
     }
     ...
 
-NEST 1.0 still supports this, but is now a bit more verbose in how it supports mapping the fields back:
+Previously, Documents was a collection of T with just the specified fields filled in, other fields would be null of have their default value. Now, Documents is an empty collection.
+
+Previously, DocumentsWithMetaData -> Fields would be an instance of T with just the specified fields filled in, other fields would be null or have their default value. Now, Hits -> Fields is (backed by) a dictionary containing only the specified fields.
+
+NEST 1.0 still supports fields, but is now a bit more verbose in how it supports mapping the fields back:
 
 
     var fields = _client.Get<DTO>(g => g