Typo, format of markdown

I prefer to limit 120 columns. A .nvimrc will be proposed to avoid
having to wide markdown lines.

doc/docs/usage.md

@@ -1,6 +1,8 @@
 # Basic Usage
 
-Basically, you can use `katenary` to transpose a docker-compose file (or any compose file compatible with `podman-compose` and `docker-compose`) to a configurable Helm Chart. This resulting helm chart can be installed with `helm` command to your Kubernetes cluster.
+Basically, you can use `katenary` to transpose a docker-compose file (or any compose file compatible with
+`podman-compose` and `docker-compose`) to a configurable Helm Chart. This resulting helm chart can be installed with
+`helm` command to your Kubernetes cluster.
 
 Katenary transforms compose services this way:
 
@@ -9,11 +11,14 @@ Katenary transforms compose services this way:
 - it a port is exposed, katenary creates a service (NodePort)
 - environment variables will be stored in `values.yaml` file
 - image, tags, and ingresses configuration are also stored in `values.yaml` file
-- if named volumes are declared, katenary create PersistentVolumeClaims - not enabled in values file (a `emptyDir` is used by default)
+- if named volumes are declared, katenary create PersistentVolumeClaims - not enabled in values file (a `emptyDir` is
+  used by default)
 - any other volume (local mount points) are ignored
 - `depends_on` needs that the pointed service declared a port. If not, you can use labels to inform katenary
 
-Katenary can also configure containers grouping in pods, declare dependencies, ignore some services, force variables as secrets, mount files as `configMap`, and many others things. To adapt the helm chart generation, you will need to use some specific labels.
+Katenary can also configure containers grouping in pods, declare dependencies, ignore some services, force variables as
+secrets, mount files as `configMap`, and many others things. To adapt the helm chart generation, you will need to use
+some specific labels.
 
 For more complete label usage, see [the labels page](labels.md).
 
@@ -28,7 +33,8 @@ katenary convert
 It will search standard compose files in the current directory and try to create a helm chart in "chart" directory.
 
 !!! Info
-    Katenary uses the compose-go library which respects the Docker and Docker-Compose specification. Keep in mind that it will find files exactly the same way as `docker-compose` and `podman-compose` do it.
+    Katenary uses the compose-go library which respects the Docker and Docker-Compose specification. Keep in mind that
+    it will find files exactly the same way as `docker-compose` and `podman-compose` do it.
 
 
 Of course, you can provide others files than the default with (cummulative) `-c` options:
@@ -47,7 +53,8 @@ Katenary proposes a lot of labels to configure the helm chart generation, but so
 
 ### Work with Depends On?
 
-Kubernetes does not propose service or pod starting detection from others pods. But katenary will create init containers to make you able to wait for a service to respond. But you'll probably need to adapt a bit the compose file.
+Kubernetes does not propose service or pod starting detection from others pods. But katenary will create init containers
+to make you able to wait for a service to respond. But you'll probably need to adapt a bit the compose file.
 
 See this compose file:
 
@@ -66,7 +73,9 @@ services:
       MYSQL_ROOT_PASSWORD: foobar
 ```
 
-In this case, `webapp` needs to know the `database` port because the `depends_on` points on it and Kubernetes has not (yet) solution to check the database startup. Katenary wants to create a `initContainer` to hit on the related service. So, instead of exposing the port in the compose definition, let's declare this to katenary with labels:
+In this case, `webapp` needs to know the `database` port because the `depends_on` points on it and Kubernetes has not
+(yet) solution to check the database startup. Katenary wants to create a `initContainer` to hit on the related service.
+So, instead of exposing the port in the compose definition, let's declare this to katenary with labels:
 
 
 ```yaml
@@ -89,7 +98,8 @@ services:
 
 ### Declare ingresses
 
-It's very common to have an `Ingress` on web application to deploy on Kuberenetes. The `katenary.io/ingress` declare the port to bind.
+It's very common to have an `Ingress` on web application to deploy on Kuberenetes. The `katenary.io/ingress` declare the
+port to bind.
 
 ```yaml
 # ...
@@ -103,12 +113,14 @@ services:
         hostname: myapp.example.com
 ```
 
-Note that the port to bind is the one used by the container, not the used locally. This is because Katenary create a service to bind the container itself.
+Note that the port to bind is the one used by the container, not the used locally. This is because Katenary create a
+service to bind the container itself.
 
 
 ### Map environment to helm values
 
-A lot of framework needs to receive service host or IP in an environment variable to configure the connexion. For example, to connect a PHP application to a database.
+A lot of framework needs to receive service host or IP in an environment variable to configure the connexion. For
+example, to connect a PHP application to a database.
 
 With a compose file, there is no problem as Docker/Podman allows to resolve the name by container name:
 
@@ -123,7 +135,8 @@ services:
     image: mariadb
 ```
 
-Katenary prefixes the services with `{{ .Release.Name }}` (to make it possible to install the application several times in a namespace), so you need to "remap" the environment variable to the right one.
+Katenary prefixes the services with `{{ .Release.Name }}` (to make it possible to install the application several times
+in a namespace), so you need to "remap" the environment variable to the right one.
 
 
 ```yaml
@@ -140,10 +153,11 @@ services:
       image: mariadb
 ```
 
-!!! Warning
-    This is a "multiline" label that accepts YAML or JSON content, don't forget to add a pipe char (`|` or `|-`) and to **indent** your content
+!!! Warning This is a "multiline" label that accepts YAML or JSON content, don't forget to add a pipe char (`|` or `|-`)
+and to **indent** your content
 
-This label can be used to map others environment for any others reason. E.g. to change an informational environment variable.
+This label can be used to map others environment for any others reason. E.g. to change an informational environment
+variable.
 
 ```yaml
 
@@ -157,4 +171,5 @@ services:
         RUNNING: kubernetes
 ```
 
-In the above example, `RUNNING` will be set to `kubernetes` when you'll deploy the application with helm, and it's `docker` for "podman" and "docker" executions.
+In the above example, `RUNNING` will be set to `kubernetes` when you'll deploy the application with helm, and it's
+`docker` for "podman" and "docker" executions.