docs: Use warning signs for critical information

parent fa5b9246
...@@ -72,9 +72,9 @@ By default, the stack exposes the following ports: ...@@ -72,9 +72,9 @@ By default, the stack exposes the following ports:
* 9300: Elasticsearch TCP transport * 9300: Elasticsearch TCP transport
* 5601: Kibana * 5601: Kibana
> :information_source: Elasticsearch's [bootstrap checks][booststap-checks] were purposely disabled to facilitate the > :warning: Elasticsearch's [bootstrap checks][booststap-checks] were purposely disabled to facilitate the setup of the
> setup of the Elastic stack in development environments. For production setups, we recommend users to set up their host > Elastic stack in development environments. For production setups, we recommend users to set up their host according to
> according to the instructions from the Elasticsearch documentation: [Important System Configuration][es-sys-config]. > the instructions from the Elasticsearch documentation: [Important System Configuration][es-sys-config].
### SELinux ### SELinux
...@@ -110,7 +110,7 @@ $ docker-compose up ...@@ -110,7 +110,7 @@ $ docker-compose up
You can also run all services in the background (detached mode) by adding the `-d` flag to the above command. You can also run all services in the background (detached mode) by adding the `-d` flag to the above command.
> :information_source: You must run `docker-compose build` first whenever you switch branch or update a base image. > :warning: You must run `docker-compose build` first whenever you switch branch or update a base image.
If you are starting the stack for the very first time, please read the section below attentively. If you are starting the stack for the very first time, please read the section below attentively.
...@@ -352,7 +352,7 @@ $ docker-compose build ...@@ -352,7 +352,7 @@ $ docker-compose build
$ docker-compose up $ docker-compose up
``` ```
> :information_source: Always pay attention to the [upgrade instructions][upgrade] for each individual component before > :warning: Always pay attention to the [upgrade instructions][upgrade] for each individual component before
performing a stack upgrade. performing a stack upgrade.
### Plugins and integrations ### Plugins and integrations
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment