docs: normalise table headers

README.md

@@ -22,7 +22,7 @@ This job performs a SonarQube analysis of your code.
 
 It is bound to the `test` stage, and uses the following variables:
 
-| Name                     | description                     | default value |
+| Name                     | Description                     | Default value |
 | ------------------------ | ------------------------------- | ----------------------------- |
 | `SONAR_SCANNER_IMAGE`    | The Docker image used to run [sonar-scanner](https://docs.sonarqube.org/latest/analysis/scan/sonarscanner/) | `registry.hub.docker.com/sonarsource/sonar-scanner-cli:latest` |
 | `SONAR_HOST_URL`         | SonarQube server url            | _none_ (disabled) |
@@ -65,7 +65,7 @@ This variant allows delegating your secrets management to a [Vault](https://www.
 
 In order to be able to communicate with the Vault server, the variant requires the additional configuration parameters:
 
-| Name              | description                            | default value     |
+| Name              | Description                            | Default value     |
 | ----------------- | -------------------------------------- | ----------------- |
 | `TBC_VAULT_IMAGE` | The [Vault Secrets Provider](https://gitlab.com/to-be-continuous/tools/vault-secrets-provider) image to use (can be overridden) | `$CI_REGISTRY/to-be-continuous/tools/vault-secrets-provider:master` |
 | `VAULT_BASE_URL`  | The Vault server base API url          | _none_ |
@@ -83,7 +83,7 @@ Then you may retrieve any of your secret(s) from Vault using the following synta
 
 With:
 
-| Name                             | description                            |
+| Name                             | Description                            |
 | -------------------------------- | -------------------------------------- |
 | `secret_path` (_path parameter_) | this is your secret location in the Vault server |
 | `field` (_query parameter_)      | parameter to access a single basic field from the secret JSON payload |