Update general scope

See #903 (comment)

schema/dereferenced-release-schema.json

@@ -2,7 +2,7 @@
  "id": "https://standard.open-contracting.org/schema/1__1__5/release-schema.json",
  "$schema": "http://json-schema.org/draft-04/schema#",
  "title": "Schema for an Open Contracting Release",
- "description": "A 'release' provides data about a single contracting or planning process at a particular point in time. Releases inform about new tenders, awards, contracts and other updates. Releases may repeat or update information provided previously in this process. One process may have many releases.\\n\\n A 'record' follows the same structure as a release, but combines information about a contracting or planning process from multiple points in time into a single summary.\\n\\n OCDS defines a 'contracting process' as 'All the actions aimed at implementing one or more contracts. This covers tendering, awarding, contracting and implementation. It does not include actions linked to planning, as these are often less structured and may be linked to multiple contracting processes. In multiple stage procedures (e.g. framework agreements with reopening of competition), each round of competition is treated as a separate contracting process.\\n\\n Procedures that failed and were restarted are considered new processes.\\n\\n Boundaries between processes (e.g. whether two contracts result from a single process or from two processes) are set by buyers depending on their needs (e.g. efficient division of labor, clear communication with the market) and legislation (e.g. rules on using procedures and lots).'\\n\\n OCDS defines a 'planning proces' as 'All the actions aimed at planning one or more contracting processes. This covers, for example, establishing the rationale for the procurement, giving the market a general description of the purchase, getting the necessary budget, forecasting and conducting market research.\\n\\n Planning processes are often less structured than contracting processes, so one or more planning process may end up leading to one or more contracting process.'",
+ "description": "Open Contracting Releases are used for contracts in public procurement (incl. design contests), concessions, public-private partnerships, government asset sales and other contexts. A 'release' provides data about a single contracting or planning process at a particular point in time. Releases inform about new tenders, awards, contracts and other updates. Releases may repeat or update information provided previously in this process. One process may have many releases.\\n\\n A 'record' follows the same structure as a release, but combines information about a contracting or planning process from multiple points in time into a single summary.\\n\\n OCDS defines a 'contracting process' as 'All the actions aimed at implementing one or more contracts. This covers tendering, awarding, contracting and implementation. It does not include actions linked to planning, as these are often less structured and may be linked to multiple contracting processes. In multiple stage procedures (e.g. framework agreements with reopening of competition), each round of competition is treated as a separate contracting process.\\n\\n Procedures that failed and were restarted are considered new processes.\\n\\n Boundaries between processes (e.g. whether two contracts result from a single process or from two processes) are set by buyers depending on their needs (e.g. efficient division of labor, clear communication with the market) and legislation (e.g. rules on using procedures and lots).'\\n\\n OCDS defines a 'planning proces' as 'All the actions aimed at planning one or more contracting processes. This covers, for example, establishing the rationale for the procurement, giving the market a general description of the purchase, getting the necessary budget, forecasting and conducting market research.\\n\\n Planning processes are often less structured than contracting processes, so one or more planning process may end up leading to one or more contracting process.'",
  "type": "object",
  "properties": {
  "ocid": {

schema/release-schema.json

@@ -2,7 +2,7 @@
  "id": "https://standard.open-contracting.org/schema/1__1__5/release-schema.json",
  "$schema": "http://json-schema.org/draft-04/schema#",
  "title": "Schema for an Open Contracting Release",
- "description": "A 'release' provides data about a single contracting or planning process at a particular point in time. Releases inform about new tenders, awards, contracts and other updates. Releases may repeat or update information provided previously in this process. One process may have many releases.\\n\\n A 'record' follows the same structure as a release, but combines information about a contracting or planning process from multiple points in time into a single summary.\\n\\n OCDS defines a 'contracting process' as 'All the actions aimed at implementing one or more contracts. This covers tendering, awarding, contracting and implementation. It does not include actions linked to planning, as these are often less structured and may be linked to multiple contracting processes. In multiple stage procedures (e.g. framework agreements with reopening of competition), each round of competition is treated as a separate contracting process.\\n\\n Procedures that failed and were restarted are considered new processes.\\n\\n Boundaries between processes (e.g. whether two contracts result from a single process or from two processes) are set by buyers depending on their needs (e.g. efficient division of labor, clear communication with the market) and legislation (e.g. rules on using procedures and lots).'\\n\\n OCDS defines a 'planning proces' as 'All the actions aimed at planning one or more contracting processes. This covers, for example, establishing the rationale for the procurement, giving the market a general description of the purchase, getting the necessary budget, forecasting and conducting market research.\\n\\n Planning processes are often less structured than contracting processes, so one or more planning process may end up leading to one or more contracting process.'",
+ "description": "Open Contracting Releases are used for contracts in public procurement (incl. design contests), concessions, public-private partnerships, government asset sales and other contexts. A 'release' provides data about a single contracting or planning process at a particular point in time. Releases inform about new tenders, awards, contracts and other updates. Releases may repeat or update information provided previously in this process. One process may have many releases.\\n\\n A 'record' follows the same structure as a release, but combines information about a contracting or planning process from multiple points in time into a single summary.\\n\\n OCDS defines a 'contracting process' as 'All the actions aimed at implementing one or more contracts. This covers tendering, awarding, contracting and implementation. It does not include actions linked to planning, as these are often less structured and may be linked to multiple contracting processes. In multiple stage procedures (e.g. framework agreements with reopening of competition), each round of competition is treated as a separate contracting process.\\n\\n Procedures that failed and were restarted are considered new processes.\\n\\n Boundaries between processes (e.g. whether two contracts result from a single process or from two processes) are set by buyers depending on their needs (e.g. efficient division of labor, clear communication with the market) and legislation (e.g. rules on using procedures and lots).'\\n\\n OCDS defines a 'planning proces' as 'All the actions aimed at planning one or more contracting processes. This covers, for example, establishing the rationale for the procurement, giving the market a general description of the purchase, getting the necessary budget, forecasting and conducting market research.\\n\\n Planning processes are often less structured than contracting processes, so one or more planning process may end up leading to one or more contracting process.'",
  "type": "object",
  "properties": {
  "ocid": {