apply review suggestions

open-contracting · Nov 19, 2024 · 50ccf02 · 50ccf02
1 parent e21128f
commit 50ccf02
Show file tree

Hide file tree

Showing 4 changed files with 1 addition and 38 deletions.
diff --git a/docs/guidance/map.md b/docs/guidance/map.md
@@ -97,7 +97,6 @@ Mapping data to OCDS is not always obvious. Please refer to our how-to guides an
 :maxdepth: 2
 :titlesonly:
 
-map/contracting_planning_processes
 map/unsuccessful_processes
 map/framework_agreements
 map/pre-qualification

diff --git a/docs/guidance/map/contracting_planning_processes.md b/docs/guidance/map/contracting_planning_processes.md
diff --git a/docs/schema/codelists.md b/docs/schema/codelists.md
@@ -129,7 +129,6 @@ Added 'parent'. Deprecated 'subContract', 'replacementProcess' and 'renewalProce
 ```
 
 ```{seealso}
-* [Map: Contracting processes and planning processes](../guidance/map/contracting_planning_processes.md)
 * [Map: Framework agreements](../guidance/map/framework_agreements.md)
 ```
 

diff --git a/schema/dereferenced-release-schema.json b/schema/dereferenced-release-schema.json
@@ -69,7 +69,7 @@
     },
     "tag": {
       "title": "Release Tag",
-      "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.",
+      "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.",
       "type": "array",
       "items": {
         "type": "string"
-Original file line number
+Diff line change
@@ Expand Up @@
     ```
     ```{seealso}
-    * [Map: Contracting processes and planning processes](../guidance/map/contracting_planning_processes.md)
     * [Map: Framework agreements](../guidance/map/framework_agreements.md)
     ```
@@ Expand Down @@