implement corrections from the PR #52

Author: mariojmdavid

content/09.annex.md

@@ -1,6 +1,6 @@
 # A1. Annex {.page_break_before}
 
-The Quality Criteria described in this document follows a technology-agnostic approach, as such the
+The Quality Criteria described in this document follows a technology-agnostic approach. As such the
 choice of tools and services to implement the workflow for service quality assessment process, is up
 to the team or community developing or operating a given service.
 
@@ -10,25 +10,25 @@ Quality Criteria detailed in this document.
 ## A1.1. Code workflow
 
 The workflow for service quality assessment, is shown in Figure @fig:workflow. It depicts a real
-case example, Github is used in particular to host the Dockerfiles to build the service docker
-image, it also hosts the ansible role for the service deployment and configuration, thus the
+case example, GitHub is used in particular to host the Dockerfiles to build the service Docker
+image, it also hosts the Ansible role for the service deployment and configuration, thus the
 IaC (Infrastructure as Code).
 
 The SQA as a Service (SQAaaS), is used to create the Jenkinsfile (pipeline) to be executed in the
 Jenkins service.
 
 Before the Jenkins pipeline execution phase, the figure depicts the build and upload/publish of the
-service docker image in the Dockerhub.
+service Docker image in the Docker Hub.
 
 The Jenkins service is the main service used to execute he pipeline. The figure show a simple
 pipeline with automated deployment of the service, execution of functional tests and dynamic
 security tests, but in general the pipeline can be more complex and execute other tools to assess
 the other service quality criteria.
 
 The bottom part of the figure shows the services, tools and infrastructures that are actuated by the
-Jenkins pipeline execution: The IM (Infrastructure Manager) is the service that is used to deploy
-the service in cloud resources, fetching the corresponding ansible role from Ansible Galaxy to
-instantiate and configure it.
+Jenkins pipeline execution: The [IM (Infrastructure Manager)](https://www.grycap.upv.es/im) is the
+service that is used to deploy the service in cloud resources, fetching the corresponding Ansible
+role from Ansible Galaxy to instantiate and configure it.
 
 ![Workflow for service quality assessment](images/service-qa-workflow.png){height="700px"}{#fig:workflow}
 
@@ -38,7 +38,7 @@ As it can be seen in Figure @fig:workflow, multiple services take part in the ex
 pipelines. Table 1 shows the list of services used for the service for the Quality Criteria
 assessment detailed in this document.
 
-One of the most popular services for Software source code management is Github. It is uses Git
+One of the most popular services for Software source code management is GitHub. It is uses Git
 as the Version Control System, branching and tag management.
 
 Ansible and Ansible-Galaxy are used in many software frameworks as deployment and configuration
@@ -55,20 +55,20 @@ Regarding the CI/CD automation, Jenkins pipelines can be easily composed through
 and put into the git repositories to be used by the Jenkins CI service to perform the tests. The
 tools used in the CI automation are shown in section A1.2.
 
-Kubernetes is a container management service where services or platforms can be deployed while the
+Kubernetes is a container management platform where services or platforms can be deployed while the
 IM (Infrastructure Manager) can also be used to automatically deploy services both in cloud
 resources or kubernetes clusters.
 
 | Service                     | Usage                         | Criteria      |  Repo URL or documentation               | Comment                                  |
 |-----------------------------|-------------------------------|---------------|------------------------------------------|------------------------------------------|
-| Github                      | VCS                           | **SvcQC.Dep** | <https://docs.github.com/>               | Source code repository - git             |
+| GitHub                      | VCS                           | **SvcQC.Dep** | <https://docs.github.com/>               | Source code repository - git             |
 | Ansible, Galaxy             | Install, Config               | **SvcQC.Dep** | <https://docs.ansible.com/>              | Automated deployment and configuration   |
 | SQAaaS platform             | Pipeline composition          | **All**       | <https://sqaaas.eosc-synergy.eu>         | Pipeline composition for automatic tests |
 | SQAaaS platform             | Assessment & awarding         | **All**       | <https://sqaaas.eosc-synergy.eu>         | Badge awarding                           |
 | Jenkins CI service          | Automated tests               | **All**       | <https://www.jenkins.io/>                | Execution of automatic tests             |
 | Docker Hub                  | Docker images                 | N.A.          | <https://hub.docker.com/>                | Public repository of Docker images       |
 | Kubernetes                  | Service deployment/management |**SvcQC.Dep**  | <https://kubernetes.io/>                 | Docker container management              |
-| Infrastructure Manager (IM) | Service deployment            |**SvcQC.Dep**  | <https://www.grycap.upv.es/im/index.php> | Service deployment                       |
+| Infrastructure Manager (IM) | Service deployment            |**SvcQC.Dep**  | <https://www.grycap.upv.es/im> | Service deployment                       |
 
 Table 1: Tools and services used to implement the Service QA criteria, also shown the criteria where
 applicable.