add author, fix issue #19

Author: mariojmdavid

content/06.quality_criteria.md

@@ -65,7 +65,7 @@ testbeds MAY be used to cope with the integration testing requirements. [SQA-QC.
 ### Functional tests [SvcQC.Fun]
 Functional testing is a type of black-box testing. It involves the verification
 of the **Service** identified functionality, based on requested requirements and
-agreed design specifications. This type of **Service** testing focus on the evaluation
+agreed design specifications. This type of **Service** testing focuses on the evaluation
 of the functionality that the **Service** exposes, leaving apart any internal
 design analysis or side-effects to external systems.
 
@@ -95,7 +95,7 @@ mechanisms in critical systems [@url:http://www.swebok.org]. *Stress testing is
 a subset of Performance testing*
 [@url:https://www.geeksforgeeks.org/difference-between-performance-and-stress-testing/].
 
-Scalability testing is test methodology in which an application’s or **Service**
+Scalability testing is a test methodology in which an application’s or **Service**
 performance is measured in terms of its ability to scale up *and/or* scale out the
 number of user requests or other such performance measure attributes, through
 an increase in the amount of available resources. The definition
@@ -114,10 +114,10 @@ to variable demand or workload for those service(s) [@doi:10.1186/s13677-019-013
   **Service** to determine the behavioral limits under sudden increased load.
 
 * **[SvcQC.Per03]** Scalability testing MAY be carried out to check the
-  **Service** hability to scale up *and/or* scale out when its load reach the limits.
+  **Service** ability to scale up *and/or* scale out when its load reaches the limits.
 
 * **[SvcQC.Per04]** Elasticity testing MAY be carried out to check the
-  **Service** hability to scale out or scale in, depending on its demand or workload.
+  **Service** ability to scale out or scale in, depending on its demand or workload.
 
 ### Documentation [SvcQC.Doc]
 
@@ -355,7 +355,7 @@ infrastructures such as EOSC.
 
 * **[SvcQC.Met01]** The **Service** SHOULD implement the collection
 of metrics.
-  * **[SvcQC.Met01.1]** The collection of metrics SHOULD be comulative
+  * **[SvcQC.Met01.1]** The collection of metrics SHOULD be cumulative
   over time and timestamped, so that the values can be queried per
   time interval.
   * **[SvcQC.Met01.2]** The metric *Number of registered users* SHOULD

content/metadata.yaml

@@ -50,3 +50,9 @@ author:
     affiliations:
       - Spanish National Research Council (CSIC)
       - Institute of Physics of Cantabria (IFCA)
+  -
+    name: Miguel Caballer
+    github: micafer
+    orcid: 0000-0001-9393-3077
+    email: [email protected]
+    affiliation: Universitat Politècnica de València (UPV)