Update quality declaration documents (#62)

Signed-off-by: Christophe Bedard <christophe.bedard@apex.ai>

QUALITY_DECLARATION.md

@@ -4,7 +4,7 @@ This document is a declaration of software quality for the `libyaml_vendor` pack
 
 The package `libyaml_vendor` claims to be in the **Quality Level 1** category.
 
-Below are the rationales, notes, and caveats for this claim, organized by each requirement listed in the [Package Quality Categories in REP-2004](https://www.ros.org/reps/rep-2004.html) of the ROS2 developer guide.
+Below are the rationales, notes, and caveats for this claim, organized by each requirement listed in the [Package Requirements for Quality Level 1 in REP-2004](https://www.ros.org/reps/rep-2004.html).
 
 ## Version Policy [1]
 
@@ -98,7 +98,7 @@ The `libyaml` package is benchmarked and the most recent test results can be fou
 
 ### Linters and Static Analysis [4.v]
 
-`libyaml_vendor` uses and passes all the ROS2 standard linters and static analysis tools as described in the [ROS 2 Developer Guide](https://docs.ros.org/en/rolling/Contributing/Developer-Guide.html#linters-and-static-analysis). Passing implies there are no linter/static errors when testing against CI of supported platforms.
+`libyaml_vendor` uses and passes all the ROS 2 standard linters and static analysis tools as described in the [ROS 2 Developer Guide](https://docs.ros.org/en/rolling/Contributing/Developer-Guide.html#linters-and-static-analysis). Passing implies there are no linter/static errors when testing against CI of supported platforms.
 
 Currently nightly test results can be seen here:
 

libyaml_q_declaration.md

@@ -3,18 +3,19 @@
 This document is a declaration of software quality for the `libyaml` external dependency, based on the guidelines in [REP-2004](https://github.com/ros-infrastructure/rep/blob/rep-2004/rep-2004.rst).
 
 The [libyaml](https://github.com/yaml/libyaml) external dependency is a C library for parsing and emitting YAML.
-It is maintained in the YAML Project Github organization together with 115 other repositories.
+It is maintained in the YAML Project GitHub organization together with 115 other repositories.
 First, a summary discussing how this library is qualified is presented, and then it will be listed how this library matches the standards defined for ROS packages.
 
 ## Summary
 
-The `libyaml` meets the basic requirements for a software platform in terms of testing its basic functionality, providing a [valid license](https://github.com/yaml/libyaml/blob/master/License) for the code used and a public Github repository with the changes made to the code over time.
+The `libyaml` meets the basic requirements for a software platform in terms of testing its basic functionality, providing a [valid license](https://github.com/yaml/libyaml/blob/master/License) for the code used and a public GitHub repository with the changes made to the code over time.
 
-Even though the library does not provide an API/ABI policy targeting the desired use of the library, the imported version of `libyaml` through the `libyaml_vendor` package is fixed to the 0.18 version. This will make the API/ABI stable.
+Even though the library does not provide an API/ABI policy targeting the desired use of the library, the imported version of `libyaml` through the `libyaml_vendor` package is fixed to the 0.2.5 version.
+This will make the API/ABI stable.
 
-There is no explicit support for any OS platform, however their [Github repository](https://github.com/yaml/libyaml) installation appears to be targeting Linux.
+There is no explicit support for any OS platform, however their [GitHub repository](https://github.com/yaml/libyaml) installation appears to be targeting Linux.
 The first version of this library was developed in 2006, and it is used widely.
-There is no explicit metric of how much the library is used, but the equivalent library for Python, developed by the same organization is required for at least 150k repositories (According to [Github metrics](https://github.com/yaml/pyyaml/network/dependents?package_id=UGFja2FnZS01MjUyMjEzNQ%3D%3D)).
+There is no explicit metric of how much the library is used, but the equivalent library for Python, developed by the same organization is required for at least 150k repositories (According to [GitHub metrics](https://github.com/yaml/pyyaml/network/dependents?package_id=UGFja2FnZS01MjUyMjEzNQ%3D%3D)).
 `libyaml` library is used for some optional fast functionality.
 The [safe_yaml](https://rubygems.org/gems/safe_yaml) ruby gem has over 80 million downloads and one of its implementations uses `libyaml` through psych.
 It is also used in the [Go-yaml project](https://github.com/go-yaml/yaml), the project supporting YAML in the Go language.
@@ -30,28 +31,29 @@ Considering the previously mentioned reasons, we consider this library to be rob
 
 ### Version Scheme [1.i]
 
-It is not stated if the library supports any kind of version policy. But the version increases with a new release. The imported version of
-`libyaml` through the `libyaml_vendor` package is fixed to the 0.18 version.
+It is not stated if the library supports any kind of version policy, but the version increases with a new release.
+The imported version of `libyaml` through the `libyaml_vendor` package is fixed to the 0.2.5 version.
 
 ### Version Stability [1.ii]
 
-Current version of `libyaml` in [its repository](https://github.com/yaml/libyaml) is 0.24, however, for the purposes of ROS2 Quality Level analysis, the imported version of `libyaml` through the `libyaml_vendor` package is fixed to the 0.18 version.
+Current version of `libyaml` in [its repository](https://github.com/yaml/libyaml) is 0.2.5 and might increase eventually.
+However, for the purposes of ROS 2 Quality Level analysis, the imported version of `libyaml` through the `libyaml_vendor` package is fixed to the 0.2.5 version.
 
 ### Public API Declaration [1.iii]
 
 As a C library, elements available in [yaml.h](https://github.com/yaml/libyaml/blob/master/include/yaml.h) are considered to be the library's public API.
 
 ### API Stability Policy [1.iv]
 
-There is no policy for API stability. This is not a problem because the `libyaml_vendor` package importing the `libyaml` dependency is using a fixed version, in this case, the [0.18](https://github.com/yaml/libyaml/tree/release-0.1.8).
+There is no policy for API stability. This is not a problem because the `libyaml_vendor` package importing the `libyaml` dependency is using a fixed version, in this case, the [0.2.5](https://github.com/yaml/libyaml/tree/release/0.2.5).
 
 ### ABI Stability Policy [1.v]
 
-There is no policy for ABI stability. This is not a problem because the `libyaml_vendor` package importing the `libyaml` dependency is using a fixed version, in this case, the [0.18](https://github.com/yaml/libyaml/tree/release-0.1.8).
+There is no policy for ABI stability. This is not a problem because the `libyaml_vendor` package importing the `libyaml` dependency is using a fixed version, in this case, the [0.2.5](https://github.com/yaml/libyaml/tree/release/0.2.5).
 
 ### ABI and ABI Stability Within a Released ROS Distribution [1.vi]
 
-There is not a direct correlation between the `libyaml` releases and the ROS distributions, however this is not a problem because the `libyaml_vendor` package importing the `libyaml` dependency is using a fixed version, in this case, the [0.18](https://github.com/yaml/libyaml/tree/release-0.1.8)
+There is not a direct correlation between the `libyaml` releases and the ROS distributions, however this is not a problem because the `libyaml_vendor` package importing the `libyaml` dependency is using a fixed version, in this case, the [0.2.5](https://github.com/yaml/libyaml/tree/release/0.2.5)
 
 ## Change Control Process [2]
 
@@ -65,7 +67,7 @@ Does not have it (or it does not seem like it’s the case).
 
 ### Peer Review Policy [2.iii]
 
-Seems to be followed for pull requests on the Github repository, but as not all code changes occur through change requests, this can not be confirmed for these changes.
+Seems to be followed for pull requests on the GitHub repository, but as not all code changes occur through change requests, this can not be confirmed for these changes.
 
 ### Continuous Integration [2.iv]
 
@@ -107,7 +109,7 @@ This document represents the Quality Declaration document for the `libyaml` ROS
 
 ### Feature Testing [4.i]
 
-Tests provided to cover the expected usage of the library, for the version of the library used can be found [here](https://github.com/yaml/libyaml/tree/release-0.1.8/tests).
+Tests provided to cover the expected usage of the library, for the version of the library used can be found [here](https://github.com/yaml/libyaml/tree/release/0.2.5/tests).
 
 ### Public API Testing [4.ii]