NIT fix readme formatting

Author: Gedochao

README.md

@@ -1,11 +1,12 @@
-
 # scala-cli
 
 [![Build status](https://github.com/VirtusLab/scala-cli/workflows/CI/badge.svg)](https://github.com/VirtusLab/scala-ci/actions?query=workflow%3ACI)
 [![Maven Central](https://img.shields.io/maven-central/v/org.virtuslab.scala-cli/cli_3.svg)](https://maven-badges.herokuapp.com/maven-central/org.virtuslab.scala-cli/cli_3)
 [![Discord](https://img.shields.io/discord/632277896739946517.svg?label=&logo=discord&logoColor=ffffff&color=404244&labelColor=6A7EC2)](https://discord.gg/KzQdYkZZza)
 
-Scala CLI is an experimental tool to run/compile/test Scala that aims at being a better `scala` command. It shares some similarities with build tools, but doesn't aim at supporting multi-module projects, nor to be extended via a task system.
+Scala CLI is an experimental tool to run/compile/test Scala that aims at being a better `scala` command. It shares some
+similarities with build tools, but doesn't aim at supporting multi-module projects, nor to be extended via a task
+system.
 
 User-facing documentation can be found on our website: [scala-cli.virtuslab.org](https://scala-cli.virtuslab.org/).
 
@@ -15,7 +16,8 @@ User-facing documentation can be found on our website: [scala-cli.virtuslab.org]
 
 Building Scala CLI requires JVM 17 to work properly.
 
-In theory, our build is able to download and install for its own needs JVM 17 on some OSes however it may not work in Intellij / Metals out of the box.
+In theory, our build is able to download and install for its own needs JVM 17 on some OSes however it may not work in
+Intellij / Metals out of the box.
 
 The Scala CLI sources ship with Mill launchers, so that Mill itself doesn't need to be installed on your system.
 
@@ -40,17 +42,20 @@ The Scala CLI sources ship with Mill launchers, so that Mill itself doesn't need
 ```
 
 Filter test suites with
+
 ```bash
 ./mill integration.test.jvm 'scala.cli.integration.RunTestsDefault.*'
 ./mill integration.test.jvm 'scala.cli.integration.RunTestsDefault.Multiple scripts'
 ```
 
 Pass the `--debug` option to debug integration tests:
+
 ```bash
 ./mill integration.test.jvm 'scala.cli.integration.RunTestsDefault.*' --debug
 ```
 
 The debug option uses 5005 port by default. It is possible to change it as follows:
+
 ```bash
 ./mill integration.test.jvm 'scala.cli.integration.RunTestsDefault.*' --debug:5006
 ```
@@ -66,11 +71,13 @@ The debug option uses 5005 port by default. It is possible to change it as follo
 #### Generate native packages
 
 Build native packagers:
+
 * `deb` for linux
 * `msi` for windows
 * `dmg` and `pkg` for macOS
 
 (generating native packager for specified format)
+
 ```bash
 ./mill -i scala package ..arguments... --deb --output 'path.deb'
 ./mill -i scala package ..arguments... --dmg --output 'path.dmg'
@@ -126,11 +133,14 @@ as binaries. In the latter case, Scala CLI downloads on-the-fly binaries from th
 repositories' GitHub release assets, and runs them as external processes.
 
 For example, here are a few external projects used by Scala CLI:
-- [scala-js-cli-native-image](https://github.com/scala-cli/scala-js-cli-native-image): provides a binary running the Scala.js linker
-- [scala-cli-signing](https://github.com/scala-cli/scala-cli-signing): provides both libraries and binaries to handle PGP concerns in Scala CLI
+
+- [scala-js-cli-native-image](https://github.com/scala-cli/scala-js-cli-native-image): provides a binary running the
+  Scala.js linker
+- [scala-cli-signing](https://github.com/scala-cli/scala-cli-signing): provides both libraries and binaries to handle
+  PGP concerns in Scala CLI
 - [libsodiumjni](https://github.com/scala-cli/libsodiumjni): provides minimal JNI bindings for
-[libsodium](https://github.com/jedisct1/libsodium), that is used by Scala CLI to encrypt secrets
-uploaded as GitHub repository secrets in the `publish setup` sub-command
+  [libsodium](https://github.com/jedisct1/libsodium), that is used by Scala CLI to encrypt secrets
+  uploaded as GitHub repository secrets in the `publish setup` sub-command
 
 For the full list of those projects and their description, see the
 [scala-cli repository list](https://github.com/orgs/scala-cli/repositories) and the READMEs
@@ -142,7 +152,8 @@ generate these binaries on the GitHub-provided GitHub actions hosts).
 
 ### Website
 
-The Scala CLI website is built with [Docusaurus](https://v1.docusaurus.io/en/) and uses [Infima](https://infima.dev/docs/layout/spacing) for styling.
+The Scala CLI website is built with [Docusaurus](https://v1.docusaurus.io/en/) and
+uses [Infima](https://infima.dev/docs/layout/spacing) for styling.
 
 Ensure you are using Node >= 16.14.2.
 
@@ -165,19 +176,22 @@ yarn run start
 
 ### Verifying the documentation
 
-We have a built-in tool to validate `.md` files called [Sclicheck](/sclicheck/Readme.md). 
+We have a built-in tool to validate `.md` files called [Sclicheck](/sclicheck/Readme.md).
 All `Sclicheck` tests can be run with `Mill` + `munit`: (and this is what we run on the CI, too)
+
 ```bash
 ./mill -i docs-tests.test
 ```
 
 The former also includes testing gifs and `Sclicheck` itself.
 To just check the documents, run:
+
 ```bash
 ./mill -i docs-tests.test 'sclicheck.DocTests.*'
 ```
 
 You can also check all root docs, commands, reference docs, guides or cookbooks:
+
 ```bash
 ./mill -i docs-tests.test 'sclicheck.DocTests.root*'
 ./mill -i docs-tests.test 'sclicheck.DocTests.guide*'
@@ -187,28 +201,37 @@ You can also check all root docs, commands, reference docs, guides or cookbooks:
 ```
 
 Similarly, you can check single files:
+
 ```bash
 ./mill -i docs-tests.test 'sclicheck.DocTests.<category> <doc-name>'
 ```
+
 For example, to run the check on `compile.md`
+
 ```bash
 ./mill -i docs-tests.test 'sclicheck.DocTests.command compile'
 ```
 
 ## Scala CLI logos
 
-Package with various logos for scala-cli can be found on [google drive](https://drive.google.com/drive/u/1/folders/1M6JeQXmO4DTBeRBKAFJ5HH2p_hbfQnqS)
+Package with various logos for scala-cli can be found
+on [google drive](https://drive.google.com/drive/u/1/folders/1M6JeQXmO4DTBeRBKAFJ5HH2p_hbfQnqS)
 
 ## Launcher script
 
-There is a script `scala-cli-src` in the repository root that is intended to work exactly like released scala-cli, but using a binary compiled the worktree.
+There is a script `scala-cli-src` in the repository root that is intended to work exactly like released scala-cli, but
+using a binary compiled the worktree.
 Just add it to your PATH to get the already-released-scala-cli experience.
 
 ## Releases
 
-Instructions on how to release - [Release Procedure](https://github.com/VirtusLab/scala-cli/blob/main/.github/release/release-procedure.md)
-
+Instructions on how to
+release - [Release Procedure](https://github.com/VirtusLab/scala-cli/blob/main/.github/release/release-procedure.md)
 
 ## Debugging BSP server
 
-The easiest way to debug BSP sever is using `scala-cli-src` script with `--bsp-debug-port 5050` flag (the port should be unique to the workspace where BSP will be debugged). In such case BSP will be launched using local source and will run on JVM. It will also expects a debugger running in the listen mode using provided port (so the initialization of the connection can be debugged). In such case we recommend to have option to auto rerun debugging session off (so there is always a debugger instance ready to be used).
+The easiest way to debug BSP sever is using `scala-cli-src` script with `--bsp-debug-port 5050` flag (the port should be
+unique to the workspace where BSP will be debugged). In such case BSP will be launched using local source and will run
+on JVM. It will also expects a debugger running in the listen mode using provided port (so the initialization of the
+connection can be debugged). In such case we recommend to have option to auto rerun debugging session off (so there is
+always a debugger instance ready to be used).