Fix broken internal links

open-contracting · Jul 30, 2021 · 0691040 · 0691040
1 parent b6013c8
commit 0691040
Show file tree

Hide file tree

Showing 4 changed files with 5 additions and 5 deletions.
diff --git a/docs/getting_started/quality.md b/docs/getting_started/quality.md
@@ -29,7 +29,7 @@ Understanding all of the challenges above, we understand that increasing the tra
 
 All OCDS publications ought to meet the following criteria:
 
-1. **Registered**: The data uses a [registered OCID prefix](../schema/identifiers.md#contracting-process-identifier-ocid).
+1. **Registered**: The data uses a [registered OCID prefix](../schema/identifiers.md#open-contracting-process-identifier-ocid).
 1. **Discoverable**: It is possible to discover the data by navigating a website whose homepage is indexed by popular web search engines.
 1. **Retrievable**: It is possible to automate the download of all the data, either using an HTML page listing bulk download URLs, or using only machine-readable data as input.
 1. **Reviewable**: The [OCDS Data Review Tool](https://standard.open-contracting.org/review/) is able to report results on the data.

diff --git a/docs/getting_started/releases_and_records.md b/docs/getting_started/releases_and_records.md
@@ -47,7 +47,7 @@ Releases follow the [release schema](../schema/reference). The schema covers the
 
 #### Identifiers
 
-Each release contains an [ocid](../schema/identifiers.md#contracting-process-identifier-ocid) to identify the contracting process it relates to. An ocid is composed of a prefix and an unique process identifier chosen by the publisher.
+Each release contains an [ocid](../schema/identifiers.md#open-contracting-process-identifier-ocid) to identify the contracting process it relates to. An ocid is composed of a prefix and an unique process identifier chosen by the publisher.
 
 A release also needs a release identifier, unique in the scope of the contracting process. A release id can be built in several ways. Publishers can use any generation strategy, as long as the ids don’t collide within the same process.
 

diff --git a/docs/guidance/map/contracting_planning_processes.md b/docs/guidance/map/contracting_planning_processes.md
@@ -1,6 +1,6 @@
 # Contracting processes and planning processes
 
-OCDS recognizes two types of processes: contracting processes and planning processes. In OCDS, a given process is uniquely identified by an [open contracting process identifier](../../schema/identifiers.md#contracting-process-identifier-ocid) (`ocid`). This section helps map your contracting activities (most often procurement procedures) to their OCDS representation.
+OCDS recognizes two types of processes: contracting processes and planning processes. In OCDS, a given process is uniquely identified by an [open contracting process identifier](../../schema/identifiers.md#open-contracting-process-identifier-ocid) (`ocid`). This section helps map your contracting activities (most often procurement procedures) to their OCDS representation.
 
 OCDS defines a contracting process as:
 

diff --git a/docs/schema/records_reference.md b/docs/schema/records_reference.md
@@ -1,6 +1,6 @@
 # Record Reference
 
-A record aggregates releases with the same [open contracting process identifier (ocid)](identifiers.md#contracting-process-identifier-ocid).
+A record aggregates releases with the same [open contracting process identifier (ocid)](identifiers.md#open-contracting-process-identifier-ocid).
 
 There should be a single record per ocid per [distribution](https://www.w3.org/TR/vocab-dcat-2/#Class:Distribution), where a distribution might be a specific API endpoint or a specific bulk download file.
 
@@ -36,7 +36,7 @@ The following example demonstrates the package metadata and record fields.
 
 ## Record structure
 
-A record **must** contain an [ocid](identifiers.md#contracting-process-identifier-ocid) and all [releases](#releases) about the contracting process at the time of the record's publication. As such, a record functions as an index of releases about a contracting process.
+A record **must** contain an [ocid](identifiers.md#open-contracting-process-identifier-ocid) and all [releases](#releases) about the contracting process at the time of the record's publication. As such, a record functions as an index of releases about a contracting process.
 
 A record **should** contain a [compiledRelease](#compiled-release) object, which represents the state of the contracting process at the time of the record's publication.