Skip to content

Commit 089e652

Browse files
Apply suggestions from code review
Co-authored-by: Edu González de la Herrán <[email protected]>
1 parent db2a35b commit 089e652

File tree

4 files changed

+8
-9
lines changed

4 files changed

+8
-9
lines changed

deploy-manage/deploy/self-managed.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ If you want to install Elastic on your own premises without the assistance of an
1515
To quickly set up {{es}} and {{kib}} in Docker for local development or testing, jump to [](/deploy-manage/deploy/self-managed/local-development-installation-quickstart.md).
1616

1717
:::{admonition} Simplify the deployment process
18-
Self-managed clusters are useful for local development, and for exploring Elastic features. However, Elastic offer several deployment options that can simplify the process of deploying and managing multi-node deployments, especially in production. They also allow you to deploy and manage multiple deployments from a single surface.
18+
Self-managed clusters are useful for local development, and for exploring Elastic features. However, Elastic offers several deployment options that can simplify the process of deploying and managing multi-node deployments, especially in production. They also allow you to deploy and manage multiple deployments from a single surface.
1919

2020
Managed by Elastic:
2121
* [{{serverless-full}}](/deploy-manage/deploy/elastic-cloud/serverless.md)
@@ -54,7 +54,7 @@ Learn how to install and configure {{es}}. {{es}} is the distributed search and
5454

5555
### Deploying Kibana
5656

57-
After you deploy {{es}}, you can install {{kib}}. {{kib}} provides the user interface for all Elastic solutions. It’s a powerful tool for visualizing and analyzing your data, and for managing and monitoring the {{stack}}. Although {{kib}} is not required to use {{es}}, it's required for most use cases.
57+
After you deploy {{es}}, you can install {{kib}}. {{kib}} provides the user interface for all Elastic solutions. It’s a powerful tool for [visualizing and analyzing](/explore-analyze/index.md) your data, and for managing and monitoring the {{stack}}. Although {{kib}} is not required to use {{es}}, it's required for most [use cases](/solutions/index.md).
5858

5959
* [](/deploy-manage/deploy/self-managed/install-kibana.md): Install {{kib}} using one of our install packages or container images, and enroll {{kib}} with your {{es}} cluster.
6060
* [](/deploy-manage/deploy/self-managed/configure-kibana.md): Learn how to make configuration changes to {{kib}}.
@@ -81,7 +81,7 @@ Review these other sections for critical information about securing and managing
8181
Learn how to secure your Elastic environment to restrict access to only authorized parties, and allow communication between your environment and external parties.
8282

8383
* [](/deploy-manage/security.md): Learn about security features that prevent bad actors from tampering with your data, and encrypt communications to, from, and within your cluster.
84-
* [](/deploy-manage/users-roles/cluster-or-deployment-auth.md): Set up authentication and authorization for your cluster, and learn about the underlying security technologies that {{es}} uses to authenticate and authorize requests internally and across services.
84+
* [Users and roles](/deploy-manage/users-roles/cluster-or-deployment-auth.md): Set up authentication and authorization for your cluster, and learn about the underlying security technologies that {{es}} uses to authenticate and authorize requests internally and across services.
8585
* [](/deploy-manage/manage-spaces.md): Learn how to organize content in {{kib}}, and restrict access to this content to specific users.
8686
* [](/deploy-manage/api-keys.md): Authenticate and authorize programmatic access to your deployments and {{es}} resources.
8787
* [](/deploy-manage/manage-connectors.md): Manage connection information between Elastic and third-party systems.

deploy-manage/deploy/self-managed/_snippets/cmd-line-config.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,7 @@
11
{{es}} loads its configuration from the following location by default:
22

3-
```
3+
```sh subs=true
44
{{es-conf}}{{slash}}elasticsearch.yml
5-
```
65

76
The format of this config file is explained in [](/deploy-manage/deploy/self-managed/configure-elasticsearch.md).
87

deploy-manage/deploy/self-managed/air-gapped-install.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,12 +40,12 @@ Specifically:
4040

4141
## {{beats}} [air-gapped-beats]
4242

43-
Elastic {{beats}} are light-weight data shippers. They do not require any unique setup in the air-gapped scenario. To learn more, refer to the [{{beats}} documentation](asciidocalypse://docs/beats/docs/reference/index.md).
43+
Elastic {{beats}} are light-weight data shippers. They do not require any special configuration in air-gapped environments. To learn more, refer to the [{{beats}} documentation](asciidocalypse://docs/beats/docs/reference/index.md).
4444

4545

4646
## {{ls}} [air-gapped-logstash]
4747

48-
{{ls}} is a versatile data shipping and processing application. It does not require any unique setup in the air-gapped scenario. To learn more, refer to the [{{ls}} documentation](asciidocalypse://docs/logstash/docs/reference/index.md).
48+
{{ls}} is a versatile data shipping and processing application. It does not require any special configuration in air-gapped environments. To learn more, refer to the [{{ls}} documentation](asciidocalypse://docs/logstash/docs/reference/index.md).
4949

5050

5151
## {{agent}} [air-gapped-elastic-agent]

deploy-manage/deploy/self-managed/install-elasticsearch-docker-prod.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -186,9 +186,9 @@ docker.elastic.co/elasticsearch/elasticsearch:{{stack-version}}
186186

187187
## Always bind data volumes [_always_bind_data_volumes]
188188

189-
You should use a volume bound on `/usr/share/elasticsearch/data` for the following reasons:
189+
You should use a volume bound to `/usr/share/elasticsearch/data` for the following reasons:
190190

191-
1. The data of your {{es}} node won’t be lost if the container is killed.
191+
1. The data of your {{es}} node won’t be lost if the container is deleted.
192192
2. {{es}} is I/O sensitive and the Docker storage driver is not ideal for fast I/O.
193193
3. It allows the use of advanced [Docker volume plugins](https://docs.docker.com/engine/extend/plugins/#volume-plugins).
194194

0 commit comments

Comments
 (0)