Merge pull request #413 from ravindrapalaskar17/Update-documentation-as-per-release

Update documentation as per release 2.2  (#5)

Author: rartych

documentation/API-linting-Implementation-Guideline.md

@@ -37,9 +37,9 @@ This file consolidates all rules:
 
 ## GitHub Actions Integration (Gherkin)
 
-1. Add **[.gherkin-lintrc](https://github.com/camaraproject/Commonalities/blob/main/artifacts/linting_rules/.gherkin-lintrc)** (rules) file to -> root location of repository
+1. Add **[.gherkin-lintrc](/artifacts/linting_rules/.gherkin-lintrc)** (rules) file to -> root location of repository
 
-2. Add <b>[megalinter.yml](https://github.com/camaraproject/Commonalities/blob/main/artifacts/linting_rules/.github/workflows/megalinter.yml)</b> to GitHub action workflows  in  `.github/workflows` folder
+2. Add <b>[megalinter.yml](/artifacts/linting_rules/.github/workflows/megalinter.yml)</b> to GitHub action workflows  in  `.github/workflows` folder
    which includes the configuration of Megalinter and Spectral for GitHub actions.   
 
 ### Manually running linting workflow
@@ -100,4 +100,3 @@ To integrate Gherkin linting into the Megalinter setup, follow these steps:
 
     *Replace **'test.feature'** with the path to your Test defination feature file.*
 
-

documentation/Linting-rules.md

@@ -32,7 +32,7 @@ Rules applying to OpenAPI v2.0, v3.0, and most likely v3.1 - details are describ
 |------------------------------------|--------------------------------------------------------------------------------------|-------------|------------|-------------------|-----------------|
 | contact-properties                 | contact object is full of the most useful properties: `name`, `url`, and `email`     | No          | No         | Warning           | Warning         |
 | duplicated-entry-in-enum           | Each value of an `enum` must be different from one another                           | Yes         | Yes        | Warning           | Warning         |
-| info-contact                       | Info object should contain `contact` object                                          | Yes         | Yes        | Warning           | Warning         |
+| info-contact                       | Info object should contain `contact` object                                          | No          | No         | Warning           | Warning         |
 | info-description                   | Info object should contain `description` object                                      | Yes         | Yes        | Warning           | Warning         | 
 | info-license                       | Info object should contain `license` object                                          | Yes         | Yes        | Warning           | Warning         |
 | license-url                        | link to the full text of licence                                                     | Yes         | Yes        | Warning           | Warning         |
@@ -156,7 +156,7 @@ Info object must include the following information: API Version in the format: X
 _Spectral rule_: [camara-info−version-format](/artifacts/linting_rules/.spectral.yml)
 
 *Severity*: `warn` <br>
-❕ Note: Currently the format like  `version: 0.10.0-wip` is used in the API development branch
+❕ Note: The version format may follow "wip", "x.y.z-alpha.n", or "x.y.z-rc.n" for unreleased or pre-release versions.