Clarifying statements in sub paddock order.

Author: tonykgill

pasturekey.md

@@ -928,9 +928,9 @@ We recommend that you supply a "name" or similar field in each Feature's
 properties object to identify the returned statistics for each
 sub-paddock.
 
-We prefer that you don't supply the following fields in the properties object.
-However, if you do, we keep your values, with the exception of
-status, reason, cibo_id, and stats which we overwrite.
+We prefer that you don't supply the following fields in the properties object
+of each Feature.
+We overwrite status, reason, cibo_id, and stats with our own values.
 See `geojson output` below for details:
 - status
 - reason
@@ -1014,18 +1014,21 @@ We insert these fields in the properties object of each Feature:
 - paddock_name: the name we have in our system of the paddock containing the polygon 
 - stats: a list of stats objects with the statistics
 
-If you provide any of the above attributes in the body, we will overwrite
-status, reason, cibo_id and stats. We don't overwrite the others.
+We overwrite `status`, `reason`, `cibo_id` and `stats`.
+All other attributes you provide are returned unchanged.
 
-We will refuse to process polygons for the following reasons:
+We may refuse to process polygons. Check the `status` and `reason` fields
+for each Feature for details. Reasons include:
 - Geometry is not of type Polygon or MultiPolygon 
 - Invalid topology 
-- Polygon < 1 ha 
-- Polygon bounding box < 10 m 
-- Sliver polygon – provide the Polsby-popper score and the threshold. E.g. score < threshold 
+- Polygon < 1 ha
+- Polygon too large
+- Polygon bounding box < 10 m in either dimension
+- It's a sliver polygon
 - Polygon is not contained within a paddock 
 - No satellite observations for the paddock within 10 days of the requested date 
- 
+
+Example output: 
 
 ```json
 {