Update README.md

README.md

@@ -131,12 +131,10 @@ The `CosmosEntityName` will be used to make the object identifiable for Cosmosna
 
 Once you set this up you can add individual CosmosStores with shared collections.
 
-Something worths noting is that because you will use this to share objects partitioning will be virtually impossible. For that reason the `id` will be used as a partition key by default as it is the only property that will be definately shared between all objects.
-
 ### Restrictions
 Because of the way the internal `id` property of Cosmosdb works, there is a mandatory restriction made.
 You cannot have a property named Id or a property with the attribute `[JsonProperty("id")]` without it being a string.
-A cosmos id need to exist somehow on your entity model. For that reason if it isn't part of your entity you can just extend the `CosmosEntity` class.
+A cosmos id needs to exist somehow on your entity model. For that reason if it isn't part of your entity you can just extend the `CosmosEntity` class.
 
 It is **HIGHLY RECOMMENDED** that you decorate your Id property with the `[JsonProperty("id")]` attribute to prevent any unexpected behaviour.
 
@@ -241,5 +239,3 @@ If you already have initialised `TelemetryConfiguration` for your application th
 | UpdateRangeAsync |1129ms|
 | UpsertRangeAsync |1034ms|
 | RemoveRangeAsync | 899ms |
-
-