Update search-howto-index-one-to-many-blobs.md

Author: jborsecnik

articles/search/search-howto-index-one-to-many-blobs.md

@@ -132,9 +132,9 @@ id, temperature, pressure, timestamp
 2, 120, 3,"2013-05-11T00:00:00Z" 
 ```
 
-Notice that each document contains the `id` field, which is defined as the 'key' field in the index. In such a case, even though a document-unique `AzureSearch_DocumentKey` will be generated, it won't be used as the 'key' for the document. Rather, the value of the `id` field will be mapped to the 'key' field
+Notice that each document contains the `id` field, which is defined as the "key" field in the index. In such a case, even though a document-unique `AzureSearch_DocumentKey` will be generated, it won't be used as the "key" for the document. Rather, the value of the `id` field will be mapped to the "key" field
 
-Similar to the example above, this mapping will _not_ result in 4 documents showing up in the index, because the `id` field is not unique _across blobs_. When this is the case, any json entry that specifies an `id` will result in a merge on the existing document instead of an upload of a new document, and the state of the index will reflect the latest read entry with the specified `id`.
+Similar to the example above, this mapping will _not_ result in four documents showing up in the index, because the `id` field is not unique _across blobs_. When this is the case, any json entry that specifies an `id` will result in a merge on the existing document instead of an upload of a new document, and the state of the index will reflect the latest read entry with the specified `id`.
 
 ## Next steps