guidance/map/linked_standards: Clarify direction of OC4IDS link

docs/guidance/map/linked_standards.md

@@ -8,7 +8,7 @@ The [Open Contracting for Infrastructure Data Standards](https://standard.open-c
 
 A joint effort by the [Infrastructure Transparency Initiative](https://infrastructuretransparency.org) (CoST) and the Open Contracting Partnership, it builds on best practice in open data and openness of public infrastructure procurement globally.
 
-OCDS and OC4IDS datasets ought to be linked using the `planning.project` object, by referencing the OC4IDS project identifier in the `planning.project.id` field.
+OC4IDS datasets ought to be linked from OCDS datasets using the `planning.project` object, by referencing the OC4IDS project identifier in the `planning.project.id` field.
 
 ## Open Fiscal Data Package
 

docs/history/changelog.md

@@ -188,7 +188,7 @@ Per the [normative and non-normative content and changes policy](../governance/n
   * [#1513](https://github.com/open-contracting/standard/pull/1513) Update fields' use of "contracting process" and "contracting (or planning) process" to reflect the new definition.
   * [#1443](https://github.com/open-contracting/standard/pull/1443) `date`
   * [#1182](https://github.com/open-contracting/standard/pull/1182) `buyer`
-  - [#1684](https://github.com/open-contracting/standard/pull/1684) `budget.project` and `budget.projectID`
+  * [#1684](https://github.com/open-contracting/standard/pull/1684) `budget.project` and `budget.projectID`
   * [#1163](https://github.com/open-contracting/standard/pull/1163) `tender.procuringEntity`
   * [#1395](https://github.com/open-contracting/standard/pull/1417) `tender.procurementMethod`
   * [#1442](https://github.com/open-contracting/standard/pull/1442) `tender.submissionMethodDetails`