[Docs][Backport]Asciidoctor formatting changes for ls ref (#10768)

* Asciidoctor formatting changes for ls ref

* More asciidoctor formatting changes
This commit is contained in:
Karen Metts 2019-05-10 16:31:29 -04:00 committed by GitHub
parent 62257c2891
commit 657cb465fc
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
5 changed files with 25 additions and 31 deletions

View file

@ -47,7 +47,6 @@ filebeat.prospectors:
output.logstash:
hosts: ["localhost:5043"]
--------------------------------------------------------------------------------
<1> Absolute path to the file or files that Filebeat processes.
Save your changes.
@ -690,7 +689,6 @@ filebeat.prospectors:
output.logstash:
hosts: ["localhost:5043"]
--------------------------------------------------------------------------------
<1> Absolute path to the file or files that Filebeat processes.
<2> Adds a field called `type` with the value `syslog` to the event.

View file

@ -110,27 +110,27 @@ Please see following annotated example and see a concrete example in https://raw
[source,markdown]
----
## 1.0.x // <1> <2>
- change description // <3>
- tag: change description // <3> <4>
- tag1,tag2: change description // <3> <5>
- tag: Multi-line description // <3> <6>
## 1.0.x // <1>
- change description // <2>
- tag: change description // <3>
- tag1,tag2: change description // <4>
- tag: Multi-line description // <5>
must be indented and can use
additional markdown syntax
// <7>
## 1.0.0 // <8>
// <6>
## 1.0.0 // <7>
[...]
----
<1> Latest version is the first line of CHANGELOG.md
<2> Each version identifier should be a level-2 header using `##`
<3> One change description is described as a list item using a dash `-` aligned under the version identifier
<4> One change can be tagged by a word and suffixed by `:`. +
<1> Latest version is the first line of CHANGELOG.md.
Each version identifier should be a level-2 header using `##`
<2> One change description is described as a list item using a dash `-` aligned under the version identifier
<3> One change can be tagged by a word and suffixed by `:`. +
Common tags are `bugfix`, `feature`, `doc`, `test` or `internal`.
<5> One change can have multiple tags separated by a comma and suffixed by `:`
<6> A multi-line change description must be properly indented
<7> Please take care to *separate versions with an empty line*
<8> Previous version identifier
<4> One change can have multiple tags separated by a comma and suffixed by `:`
<5> A multi-line change description must be properly indented
<6> Please take care to *separate versions with an empty line*
<7> Previous version identifier
[float]
==== Continuous Integration

View file

@ -8,7 +8,7 @@ can start adding custom code to process data with Logstash.
**Example Usage**
[source,sh]
--------------------------------------------
-------------------------------------------
bin/logstash-plugin generate --type input --name xkcd --path ~/ws/elastic/plugins
-------------------------------------------

View file

@ -20,13 +20,10 @@ bin/logstash-plugin list --verbose <2>
bin/logstash-plugin list '*namefragment*' <3>
bin/logstash-plugin list --group output <4>
----------------------------------
<1> Will list all installed plugins
<2> Will list installed plugins with version information
<3> Will list all installed plugins containing a namefragment
<4> Will list all installed plugins for a particular group (input, filter, codec, output)
<1> Lists all installed plugins
<2> Lists installed plugins with version information
<3> Lists all installed plugins containing a namefragment
<4> Lists all installed plugins for a particular group (input, filter, codec, output)
[float]
[[installing-plugins]]
@ -82,9 +79,8 @@ subcommand you can get the latest or update to a particular version of the plugi
bin/logstash-plugin update <1>
bin/logstash-plugin update logstash-output-kafka <2>
----------------------------------
<1> will update all installed plugins
<2> will update only this plugin
<1> Updates all installed plugins
<2> Updates only this plugin
[[removing-plugins]]
[float]

View file

@ -24,7 +24,7 @@ Distributions like Debian Jessie, Ubuntu 15.10+, and many of the SUSE derivative
`systemctl` command to start and stop services. Logstash places the systemd unit files in `/etc/systemd/system` for both deb and rpm. After installing the package, you can start up Logstash with:
[source,sh]
--------------------------------------------
-------------------------------------------
sudo systemctl start logstash.service
-------------------------------------------
@ -34,7 +34,7 @@ sudo systemctl start logstash.service
For systems that use upstart, you can start Logstash with:
[source,sh]
--------------------------------------------
-------------------------------------------
sudo initctl start logstash
-------------------------------------------
@ -46,7 +46,7 @@ The auto-generated configuration file for upstart systems is `/etc/init/logstash
For systems that use SysV, you can start Logstash with:
[source,sh]
--------------------------------------------
-------------------------------------------
sudo /etc/init.d/logstash start
-------------------------------------------