Apply suggestions from code review

docs/examples/purchase_orders/contracts_pos.csv

@@ -1,5 +1,5 @@
 contracts/0/id,contracts/0/awardID,contracts/0/value/amount,contracts/0/title
-LP-12006-23-231421,LP-12006-23-231421-426631,3150000000,Asuncion office cleaning services
-LP-12006-23-23142-1,LP-12006-23-231421-426631,20500000,DGFT building cleaning
-LP-12006-23-231421-2,LP-12006-23-231421-426631,20500000,DGGC building cleaning
-LP-12006-23-231421-3,LP-12006-23-231421-426631,20000000,SET building cleaning
+1,1,3150000000,Office cleaning services
+1-1,1,20500000,DGFT building cleaning
+1-2,1,20500000,DGGC building cleaning
+1-3,1,20000000,SET building cleaning

docs/examples/purchase_orders/parent_contract.csv

@@ -1,2 +1,2 @@
 contracts/0/id,contracts/0/awardID,contracts/0/value/amount,contracts/0/title
-LP-12006-23-231421,LP-12006-23-231421-426631,3150000000,Asuncion office cleaning services
+1,1,3150000000,Office cleaning services

docs/guidance/map/awards_contracts.md

@@ -152,32 +152,31 @@ A purchase order is a specific type of contract, an official document issued by
 
 Purchase orders can be issued against an existing contract, or if no prior contract exists then acceptance of a purchase order by a supplier forms a contract between buyer and supplier.
 
-Purchase orders can be made against contracts with indefinite quantities or maximum only values. In these cases the initial contract and resulting purchase orders ought to be modelled as [a closed framework agreement with no second-stage competition](https://standard.open-contracting.org/staging/1.2-dev/en/guidance/map/framework_agreements/).
+Purchase orders can be made against contracts that specify only minimum and maximum limits on the quantity or value of the items being procured. Such contracts are known as indefinite-delivery/indefinite-quantity (IDIQ) contracts. IDIQ contracts are considered to be two-stage procurement techniques and ought to be modelled according to the [guidance for framework agreements](https://standard.open-contracting.org/staging/1.2-dev/en/guidance/map/framework_agreements/).
 
-Purchase orders that are made against contracts with a definite quantity or value of items ought to not be disclosed in the `contracts` section of OCDS, due to the risk of double counting items on the purchase order and the contract it relates to.
+Purchase orders made against contracts with definite quantities or values ought to not be disclosed in the `contracts` section of OCDS, due to the risk of double counting.
 
 ### Example: Double counting contracts and purchase orders
 
-Paraguay's Dirección Nacional de Ingresos Tributarios awards a contract worth 3,150 million Gs to Carlos Ruben Oviedo Centurion for cleaning services in administrative buildings in Asunción. The contract is represented in the `contracts` section of OCDS as follows:
+A buyer awards a contract worth 3,150m Gs for cleaning services across several office buildings. The contract is added to the `contracts` array.
 
 ```{csv-table-no-translate}
 :header-rows: 1
 :file: ../../examples/purchase_orders/parent_contract.csv
 ```
 
-Calculating the sum of the contract value in the above example gives the correct result of Gs 3,150 million.
 
-During the first month of the contract Dirección Nacional de Ingresos Tributarios issues 3 purchase orders for cleaning in 3 different buildings.
+The buyer issues three purchase orders for cleaning in three different buildings.
 
-If purchase orders were also disclosed in the `contracts` section of OCDS, the `contracts` section of OCDS would now be populated as follows:
+If the purchase orders were added to the `contracts` array, it would lead to double counting. The total value of the contracts in the OCDS data would be greater than the value of the real-life contract. 
 
 ```{csv-table-no-translate}
 :header-rows: 1
 :file: ../../examples/purchase_orders/contracts_pos.csv
 ```
 
-Calculating the sum of the contract value in the above example gives an incorrect result of Gs 3,211 million.
+The correct approach is to add only the 'parent' contract to the `contracts` array.
 
 ```{note}
-The approach for modelling purchase orders in OCDS has not been standardized. Implementers are encouraged to describe their use of purchase orders in this ([GitHub issue](https://github.com/open-contracting/standard/issues/897)) to help develop a standardized approach.
+The approach to modelling purchase orders in OCDS is not yet standardized. Implementers are encouraged to describe their use of purchase orders in the ([GitHub issue](https://github.com/open-contracting/standard/issues/897)) to help develop a standardized approach.
 ```