Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add missing info about Homebrew installation #28902

Merged
merged 8 commits into from
Jun 20, 2018
Merged

Add missing info about Homebrew installation #28902

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
b773891
Add missing info about Homebrew installation
jrpool Mar 5, 2018
3a50957
Converted implicit reference to link.
jrpool Jun 19, 2018
60e97ee
Corrected markdown syntax.
jrpool Jun 19, 2018
53c6b5c
Re-corrected markdown syntax
jrpool Jun 19, 2018
956138e
Re-re-corrected markdown syntax
jrpool Jun 19, 2018
6194bb1
Split long line.
jrpool Jun 19, 2018
2a14797
Added anchor for link destination.
jrpool Jun 19, 2018
034b5f4
Merge remote-tracking branch 'origin/6.2' into patch-1
Jun 20, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/reference/getting-started.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -158,6 +158,8 @@ On macOS, Elasticsearch can also be installed via https://brew.sh[Homebrew]:
brew install elasticsearch
--------------------------------------------------

If installation succeeds, Homebrew will finish by saying that you can start Elasticsearch by entering `elasticsearch`. Do that now. The expected response is described below, under `Successfully running node`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe you could add an anchor like [[successfully-running-node]] to the section in question and then reference it with an internal cross references <<....>>? I think that would make navigating to the next step even easier.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, @cbuescher. I lost track of your suggestion. Now I have implemented it, after a long delay.


[float]
=== Installation example with MSI Windows Installer

Expand Down