Skip to content

Commit e58430d

Browse files
committed
[DOCS] Removes the term: tutorial from the Getting started with the Elastic Stack page (#392)
This PR removes the term "tutorial" from the getting started page for better differentiation between the two content types. Resolves conflict. Related issue: #391
1 parent 619c796 commit e58430d

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

docs/en/getting-started/get-started-stack.asciidoc

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
[[get-started-elastic-stack]]
22
== Getting started with the {stack}
33

4-
Looking for an {stack} ("ELK" tutorial) that shows how to set up the {stack}? In
5-
this tutorial, you learn how to get up and running quickly. First you install
6-
the core open source products:
4+
Looking for an {stack} ("ELK") guide that shows how to set up the {stack} and
5+
get up and running quickly? You're on the right place! First you install the
6+
core products:
77

88
* <<install-elasticsearch,{es}>>
99
* <<install-kibana,{kib}>>
@@ -310,7 +310,7 @@ The {beats} are open source data shippers that you install as agents on your
310310
servers to send operational data to {es}. {beats} can send data directly to {es}
311311
or via {ls}, where you can further process and enhance the data.
312312

313-
Each Beat is a separately installable product. In this tutorial, you learn how
313+
Each Beat is a separately installable product. In this guide, you learn how
314314
to install and run {metricbeat} with the `system` module enabled to collect system
315315
metrics.
316316

@@ -645,7 +645,7 @@ To learn more about installing, configuring, and running {ls}, read the
645645
==== Configure {ls} to listen for {beats} input
646646

647647
{ls} provides {logstash-ref}/input-plugins.html[input plugins] for reading from
648-
a variety of inputs. In this tutorial, you create a {ls} pipeline configuration
648+
a variety of inputs. In this guide, you create a {ls} pipeline configuration
649649
that listens for {beats} input and sends the received events to the {es} output.
650650

651651
To configure {ls}:
@@ -785,9 +785,9 @@ For example:
785785

786786
Rather than sending the whole command-line argument to {es}, you might want to
787787
send just the command's path. One way to do that is by using a Grok filter.
788-
Learning Grok is beyond the scope of this tutorial, but if you want to learn
789-
more, see the {logstash-ref}/plugins-filters-grok.html[Grok filter plugin]
790-
documentation.
788+
Learning Grok is beyond the scope of this getting started guide, but if you want
789+
to learn more, see the
790+
{logstash-ref}/plugins-filters-grok.html[Grok filter plugin] documentation.
791791

792792
To extract the path, add the following Grok filter between the input and output
793793
sections in the {ls} config file that you created earlier:

0 commit comments

Comments
 (0)