Update logstah/diagnostic.md

[stefnestor]

👋 @theletterf, removing the tabs from just created LS Diag page from #1726 because it sub-content'd wrong but afterwards if it's okay I decided I like not tabs for searchability 🙂

"3." onwards shouldn't be sub-content

• 
• 

[github-actions]

🔍 Preview links for changed docs:

• troubleshoot/ingest/logstash/diagnostic.md

🔔 The preview site may take up to 3 minutes to finish building. These links will become live once it completes.

[colleenmcginnis]

A minor suggestion below. 🙂

[colleenmcginnis]

If you indent all the lines in the {tip} (65-73) one more time, the admonition block should better align with the list items:

Before	After

[colleenmcginnis]

Also, just for the future, it looks like before the second {tab-item} and the {tab-set} were never closed. This snippet would fix that:

2. Using the same environment parameters, run the diagnostic tool script.

    For information about the parameters that you can pass to the tool, refer to the [diagnostic parameter reference](https://github.com/elastic/support-diagnostics#standard-options).

    :::::{tab-set}
    ::::{tab-item} Unix-based systems
    ```sh
    sudo ./diagnostics.sh --type logstash-local --host 127.0.0.1 --port 9600 --bypassDiagVerify
    ```
    ::::
    ::::{tab-item} Windows
    ```sh
    .\diagnostics.bat --type logstash-local --host 127.0.0.1 --port 9600 --bypassDiagVerify
    ```
    ::::
    :::::

    ::::{tip}

    You can run the script in three [modes](https://github.com/elastic/support-diagnostics#diagnostic-types):

    * `local` (default, recommended): Polls the [{{ls}} API](https://www.elastic.co/docs/api/doc/logstash/), gathers operating system info, and captures node logs.
    * `remote`: Establishes an ssh session to the applicable target server to pull the same information as `local`.
    * `api`: Polls the [{{ls}} API](https://www.elastic.co/docs/api/doc/logstash/). All other data must be collected manually.

    ::::

3. When the script has completed, verify that no errors were logged to `diagnostic.log`. If the log file contains errors, refer to [Diagnose errors in `diagnostic.log`](#diagnostic-log-errors).