Merge pull request #12 from SEKOIA-IO/update/doc

update(doc): change SEKOIA.IO to Sekoia.io

README.md

@@ -1,6 +1,6 @@
-# SEKOIA.IO Forwarder
+# Sekoia.io Forwarder
 
-The files in this repository are used to build and create a Docker container running a Rsyslog as a concentrator to forward events to SEKOIA.IO.
+The files in this repository are used to build and create a Docker container running a Rsyslog as a concentrator to forward events to Sekoia.io.
 
 To catch incoming events and apply the right intake key, this image processes each source on a specific TCP port.
 
@@ -20,7 +20,7 @@ The docker-compose folder contains the two files needed to start the container w
 ### intakes.yaml file
 The `intakes.yaml` file is used to tell Rsyslog what ports and intake keys to use.
 In the `intakes` key, specify:
-* a name (it has nothing to do with SEKOIA.IO, it can be a random value)
+* a name (it has nothing to do with Sekoia.io, it can be a random value)
 * the protocol, tcp or udp
 * a port, to process incoming events
 * the intake key
@@ -57,7 +57,7 @@ logging:
 Docker logging system enables you to view events received on the container in real time with the command `docker logs <container_name>`. These logs are stored by default in `/var/lib/docker/containers/<container_uuid>/<container_uuid>-json.log`. To avoid the overload of disk space, some options are specified. `max-size` specifies the max size a one file and `max-file` specifies the total number of files allowed. When the maximum number of files is reached, a log rotation is performed and the oldest file is deleted.
 
 #### Environment variables
-This image uses two environment variables to customize the container. These variables are used to define a queue for incoming logs in case there is an temporaly issue in transmitting events to SEKOIA.IO. The queue stores messages in memory up to a certain number of events and then store them on disk.
+This image uses two environment variables to customize the container. These variables are used to define a queue for incoming logs in case there is an temporaly issue in transmitting events to Sekoia.io. The queue stores messages in memory up to a certain number of events and then store them on disk.
 
 ```yaml
 environment: