Skip to content

Commit 50ccf02

Browse files
committed
apply review suggestions
1 parent e21128f commit 50ccf02

File tree

4 files changed

+1
-38
lines changed

4 files changed

+1
-38
lines changed

docs/guidance/map.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,6 @@ Mapping data to OCDS is not always obvious. Please refer to our how-to guides an
9797
:maxdepth: 2
9898
:titlesonly:
9999
100-
map/contracting_planning_processes
101100
map/unsuccessful_processes
102101
map/framework_agreements
103102
map/pre-qualification

docs/guidance/map/contracting_planning_processes.md

Lines changed: 0 additions & 35 deletions
This file was deleted.

docs/schema/codelists.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,6 @@ Added 'parent'. Deprecated 'subContract', 'replacementProcess' and 'renewalProce
129129
```
130130

131131
```{seealso}
132-
* [Map: Contracting processes and planning processes](../guidance/map/contracting_planning_processes.md)
133132
* [Map: Framework agreements](../guidance/map/framework_agreements.md)
134133
```
135134

schema/dereferenced-release-schema.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@
6969
},
7070
"tag": {
7171
"title": "Release Tag",
72-
"description": "A tag labeling the release, using the the open [releaseTag](https://standard.open-contracting.org/{{version}}/{{lang}}/schema/codelists/#release-tag) codelist. Tags distinguish, for example, planning and contracting processes and the stages of contracting processes. Codes outside the releaseTag codelist may indicate, for example, the notice or form to which the release corresponds, or the event that triggered the publication of the release. A planning process must use either the 'planning' or 'planningUpdate' code, and must not use any other code from the releaseTag codelist. A contracting process should not use the 'planning' or 'planningUpdate' codes.",
72+
"description": "A tag labeling the release, using the open [releaseTag](https://standard.open-contracting.org/{{version}}/{{lang}}/schema/codelists/#release-tag) codelist. Tags distinguish, for example, planning and contracting processes and the stages of contracting processes. Codes outside the releaseTag codelist might indicate, for example, the notice or form to which the release corresponds, or the event that triggered the publication of the release. A planning process must use either the 'planning' or 'planningUpdate' code, and must not use any other code from the releaseTag codelist. A contracting process should not use the 'planning' or 'planningUpdate' codes.",
7373
"type": "array",
7474
"items": {
7575
"type": "string"

0 commit comments

Comments
 (0)