consistently use "certificate" instead of report

Author: nuest

faq.md

@@ -68,7 +68,7 @@ The _files_ and _archives_ (a Docker image is a tarball of a directory system) w
 
 ## What's the correct way of writing CODECHECK?
 
-- CODECHECK process.
+- A CODECHECK process implementation, the so called CODECHECK workflow, describes what happens before and after a paper has been codechecked.
 - A codechecker codechecks an article and creates the CODECHECK bundle.
-- Codecheckers write CODECHECK reports.
-- The CODECHECK report is created by the codechecker during the codechecking process.
+- Codecheckers write CODECHECK certificate.
+- The CODECHECK certificate is created by the codechecker during the codechecking process.

spec/config/1.0.md

@@ -14,7 +14,7 @@ redirect_from:
 The CODECHECK process describes a workflow for a reproduction of computations as part of a scientific peer review.
 CODECHECK follows a set of [principles](/) that allow many different variations into [concrete implementations](/process).
 The requirements for a successful CODECHECK are intentionally kept to a minimum, as are the requirements on how codechecking is conducted, or how the procedure is documented.
-At the end of the CODECHECK stands a CODECHECK report document, written by the codechecker and understandable to a person with some expertise in the scientific field of the related article.
+At the end of the CODECHECK stands a CODECHECK certificate, a document written by the codechecker and understandable to a person with some expertise in the scientific field of the related article.
 Besides the human-readable information in the CODECHEK report, there is a small set of metadata elements that are part of a CODECHECK procedure which are worth capturing in a more structured format.
 
 This metadata is saved in the CODECHECK configuration file, which is specified in this document in version {{ page.version }}.
@@ -189,11 +189,11 @@ The configuration file MUST include minimal metadata about the codechecker in a
 Each item in the `codechecker` sequence MUST have one node `name` with the codechecker's name.
 Each item in the `codechecker` sequence SHOULD have a child `ORCID` as defined in [Author and submission metadata](#author-and-submission-metadata).
 
-The configuration file MUST have a root-level node `report` with a unique identifier for the published CODECHECK report, such as a URL or DOI, ideally in a resolvable format.
+The configuration file MUST have a root-level node `report` with a unique identifier for the published CODECHECK certificate, such as an URL or DOI, ideally in a resolvable format.
 
 The CODECHECK CAN add further fields with the following names and semantics:
 
-- `summary`: Short textual summary of the CODECHECK report.
+- `summary`: Short textual summary of the CODECHECK certificate.
 - `repository`: A URL or a list of URLs to the code or data repository/ies where more files and a version history of the checked workflow are available.
 - `source`: see [`source`](#source).
 - `check_time`: A date or timestamp when the CODECHECK was completed. If not time is provided, it should be assumed that codechecking was completed at the publication date of the CODECHEK report.

spec/config/1.x.md

@@ -15,7 +15,7 @@ permalink: spec/config/1.x/
 The CODECHECK process describes a workflow for a reproduction of computations as part of a scientific peer review.
 CODECHECK follows a set of [principles](/) that allow many different variations into [concrete implementations](/process).
 The requirements for a successful CODECHECK are intentionally kept to a minimum, as are the requirements on how codechecking is conducted, or how the procedure is documented.
-At the end of the CODECHECK stands a CODECHECK report document, written by the codechecker and understandable to a person with some expertise in the scientific field of the related article.
+At the end of the CODECHECK stands a CODECHECK certificate document, written by the codechecker and understandable to a person with some expertise in the scientific field of the related article.
 Besides the human-readable information in the CODECHEK report, there is a small set of metadata elements that are part of a CODECHECK procedure which are worth capturing in a more structured format.
 
 This metadata is saved in the CODECHECK configuration file, which is specified in this document in version {{ page.version }}.
@@ -190,11 +190,11 @@ The configuration file MUST include minimal metadata about the codechecker in a
 Each item in the `codechecker` sequence MUST have one node `name` with the codechecker's name.
 Each item in the `codechecker` sequence SHOULD have a child `ORCID` as defined in [Author and submission metadata](#author-and-submission-metadata).
 
-The configuration file MUST have a root-level node `report` with a unique identifier for the published CODECHECK report, such as a URL or DOI, ideally in a resolvable format.
+The configuration file MUST have a root-level node `report` with a unique identifier for the published CODECHECK certificate, such as a URL or DOI, ideally in a resolvable format.
 
 The CODECHECK CAN add further fields with the following names and semantics:
 
-- `summary`: Short textual summary of the CODECHECK report.
+- `summary`: Short textual summary of the CODECHECK certificate.
 - `repository`: A URL or a list of URLs to the code or data repository/ies where more files and a version history of the checked workflow are available.
 - `source`: see [`source`](#source).
 - `check_time`: A date or timestamp when the CODECHECK was completed. If not time is provided, it should be assumed that codechecking was completed at the publication date of the CODECHEK report.