updated site

Author: eed3si9n

2.x/docs/en/print.html

@@ -2105,19 +2105,17 @@ <h3 id="sbt-runner-and-sbt-server"><a class="header" href="#sbt-runner-and-sbt-s
 <p>This mechanism allows builds to be configured to a specific version of sbt, and everyone working on the project would use the same build semantics, regardless of the sbt runner installed on their machine.</p>
 <p>This also means that some features are implemented at sbt runner or sbtn level, while other features are implemented at sbt server level.</p>
 <h2 id="sbt-commands"><a class="header" href="#sbt-commands">sbt commands</a></h2>
-<div id="admonition-note" class="admonition admonish-note" role="note" aria-labelledby="admonition-note-title">
+<div id="admonition-note-on-commands" class="admonition admonish-note" role="note" aria-labelledby="admonition-note-on-commands-title">
 <div class="admonition-title">
-<div id="admonition-note-title">
-<p>Note</p>
+<div id="admonition-note-on-commands-title">
+<p>Note on commands</p>
 </div>
-<a class="admonition-anchor-link" href="reference/sbt.html#admonition-note"></a>
+<a class="admonition-anchor-link" href="reference/sbt.html#admonition-note-on-commands"></a>
 </div>
 <div>
-<p>There is a technical distinction in sbt between <em>tasks</em>, which are
-<em>inside</em> the build definition, and <em>commands</em>, which often manipulate the
-build definition itself.
-This specific sbt meaning of <em>command</em> means there's no good general term for
-<em>thing you can type at the sbt prompt</em>, which may be a setting, task, or command.</p>
+<p>In sbt, there are <em>tasks</em> that operate at the subproject level (like <code>compile</code>), and <em>commands</em> in the narrow sense (like <code>set</code>), which is capable of manipulating the build definition itself.</p>
+<p>Given that settings and tasks are lifted into the <code>act</code> command, we can consider <em>all things that can be typed into the sbt shell</em> as commands in the wide sense.
+See the <a href="reference/../concepts/command.html">Command</a> concept page for details.</p>
 </div>
 </div>
 <!--
@@ -2128,11 +2126,11 @@ <h2 id="sbt-commands"><a class="header" href="#sbt-commands">sbt commands</a></h
     setting control which tasks from which projects are executed. See
     [multi-project builds][Multi-Project].
 -->
-<h3 id="project-level-tasks"><a class="header" href="#project-level-tasks">Project-level tasks</a></h3>
+<h3 id="subproject-level-tasks"><a class="header" href="#subproject-level-tasks">Subproject-level tasks</a></h3>
 <ul>
 <li><code>clean</code> Deletes all generated files (the <code>target</code> directory).</li>
 <li><a href="reference/./sbt-publish.html"><code>publish</code></a> Publishes artifacts (such as JARs) to the repository
-defined by the publishTo setting, described in Publishing.</li>
+defined by the <code>publishTo</code> setting.</li>
 <li><a href="reference/./sbt-publish.html"><code>publishLocal</code></a> Publishes artifacts (such as JARs) to the local Ivy
 repository as described in Publishing.</li>
 <li><a href="reference/./sbt-update.html"><code>update</code></a> Resolves and retrieves external dependencies.</li>
@@ -2184,15 +2182,16 @@ <h3 id="configuration-level-tasks"><a class="header" href="#configuration-level-
 <ol>
 <li>have not been run yet OR</li>
 <li>failed the last time they were run OR</li>
-<li>had any transitive dependencies recompiled since the last
-successful run <code>*</code> is interpreted as a wildcard in the
+<li>had any transitive dependencies recompiled since the last successful run<br>
+<code>*</code> is interpreted as a wildcard in the
 test name.</li>
 </ol>
 </li>
 <li><a href="reference/./sbt-test.html"><code>testFull</code></a> Runs all tests detected during test compilation.</li>
-<li><a href="reference/./sbt-test.html"><code>testOnly &lt;test&gt;*</code></a> Runs the tests provided as arguments.</li>
 </ul>
 <!--
+-   [`testOnly <test>*`](./sbt-test.md) Runs the tests provided as arguments.
+
 -   `consoleQuick` Starts the Scala interpreter with the project's
     compile-time dependencies on the classpath. Test/consoleQuick uses
     the test dependencies. This task differs from console in that it
@@ -2205,32 +2204,29 @@ <h3 id="configuration-level-tasks"><a class="header" href="#configuration-level-
 -->
 <h3 id="general-commands"><a class="header" href="#general-commands">General commands</a></h3>
 <ul>
-<li>
-<p><code>exit</code> or <code>quit</code> End the current interactive session or build.
+<li><code>shutdown</code> Shuts down the sbt server to end the current sbt session.</li>
+<li><code>exit</code> or <code>quit</code> End the current interactive session or build.
 Additionally, Ctrl+D (Unix) or Ctrl+Z (Windows) will exit the
-interactive prompt.</p>
-</li>
-<li>
-<p><code>help &lt;command&gt;</code> Displays detailed help for the specified command.
+interactive prompt.</li>
+<li><code>help &lt;command&gt;</code> Displays detailed help for the specified command.
 If the command does not exist, help lists detailed help for commands
 whose name or description match the argument, which is interpreted
 as a regular expression. If no command is provided, displays brief
 descriptions of the main commands. Related commands are tasks and
-settings.</p>
-</li>
-<li>
-<p><code>projects [add|remove &lt;URI&gt;]</code> List all available projects if no
-arguments provided or adds/removes the build at the provided URI.</p>
-<!-- (See [multi-project builds][Multi-Project] for details on multi-project
+settings.</li>
+<li><code>projects [add|remove &lt;URI&gt;]</code> List all available projects if no
+arguments provided or adds/removes the build at the provided URI.<!-- (See [multi-project builds][Multi-Project] for details on multi-project
 builds.) -->
 </li>
-<li>
-<p><code>project &lt;project-id&gt;</code> Change the current project to the project
-with ID <code>&lt;project-id&gt;</code>. Further operations will be done in the
-context of the given project.</p>
-<!-- (See [multi-project builds][Multi-Project] for
-details on multiple project builds.) -->
-</li>
+</ul>
+<!--
+-   `project <project-id>` Change the current project to the project
+    with ID `<project-id>`. Further operations will be done in the
+    context of the given project.
+    (See [multi-project builds][Multi-Project] for
+    details on multiple project builds.)
+-->
+<ul>
 <li>
 <p><a href="reference/./watch.html">Watch command</a> <code>~ &lt;command&gt;</code> Executes the project specified action or method
 whenever source files change.</p>

2.x/docs/en/reference/sbt.html

@@ -238,19 +238,17 @@ <h3 id="sbt-runner-and-sbt-server"><a class="header" href="#sbt-runner-and-sbt-s
 <p>This mechanism allows builds to be configured to a specific version of sbt, and everyone working on the project would use the same build semantics, regardless of the sbt runner installed on their machine.</p>
 <p>This also means that some features are implemented at sbt runner or sbtn level, while other features are implemented at sbt server level.</p>
 <h2 id="sbt-commands"><a class="header" href="#sbt-commands">sbt commands</a></h2>
-<div id="admonition-note" class="admonition admonish-note" role="note" aria-labelledby="admonition-note-title">
+<div id="admonition-note-on-commands" class="admonition admonish-note" role="note" aria-labelledby="admonition-note-on-commands-title">
 <div class="admonition-title">
-<div id="admonition-note-title">
-<p>Note</p>
+<div id="admonition-note-on-commands-title">
+<p>Note on commands</p>
 </div>
-<a class="admonition-anchor-link" href="#admonition-note"></a>
+<a class="admonition-anchor-link" href="#admonition-note-on-commands"></a>
 </div>
 <div>
-<p>There is a technical distinction in sbt between <em>tasks</em>, which are
-<em>inside</em> the build definition, and <em>commands</em>, which often manipulate the
-build definition itself.
-This specific sbt meaning of <em>command</em> means there's no good general term for
-<em>thing you can type at the sbt prompt</em>, which may be a setting, task, or command.</p>
+<p>In sbt, there are <em>tasks</em> that operate at the subproject level (like <code>compile</code>), and <em>commands</em> in the narrow sense (like <code>set</code>), which is capable of manipulating the build definition itself.</p>
+<p>Given that settings and tasks are lifted into the <code>act</code> command, we can consider <em>all things that can be typed into the sbt shell</em> as commands in the wide sense.
+See the <a href="../concepts/command.html">Command</a> concept page for details.</p>
 </div>
 </div>
 <!--
@@ -261,11 +259,11 @@ <h2 id="sbt-commands"><a class="header" href="#sbt-commands">sbt commands</a></h
     setting control which tasks from which projects are executed. See
     [multi-project builds][Multi-Project].
 -->
-<h3 id="project-level-tasks"><a class="header" href="#project-level-tasks">Project-level tasks</a></h3>
+<h3 id="subproject-level-tasks"><a class="header" href="#subproject-level-tasks">Subproject-level tasks</a></h3>
 <ul>
 <li><code>clean</code> Deletes all generated files (the <code>target</code> directory).</li>
 <li><a href="./sbt-publish.html"><code>publish</code></a> Publishes artifacts (such as JARs) to the repository
-defined by the publishTo setting, described in Publishing.</li>
+defined by the <code>publishTo</code> setting.</li>
 <li><a href="./sbt-publish.html"><code>publishLocal</code></a> Publishes artifacts (such as JARs) to the local Ivy
 repository as described in Publishing.</li>
 <li><a href="./sbt-update.html"><code>update</code></a> Resolves and retrieves external dependencies.</li>
@@ -317,15 +315,16 @@ <h3 id="configuration-level-tasks"><a class="header" href="#configuration-level-
 <ol>
 <li>have not been run yet OR</li>
 <li>failed the last time they were run OR</li>
-<li>had any transitive dependencies recompiled since the last
-successful run <code>*</code> is interpreted as a wildcard in the
+<li>had any transitive dependencies recompiled since the last successful run<br>
+<code>*</code> is interpreted as a wildcard in the
 test name.</li>
 </ol>
 </li>
 <li><a href="./sbt-test.html"><code>testFull</code></a> Runs all tests detected during test compilation.</li>
-<li><a href="./sbt-test.html"><code>testOnly &lt;test&gt;*</code></a> Runs the tests provided as arguments.</li>
 </ul>
 <!--
+-   [`testOnly <test>*`](./sbt-test.md) Runs the tests provided as arguments.
+
 -   `consoleQuick` Starts the Scala interpreter with the project's
     compile-time dependencies on the classpath. Test/consoleQuick uses
     the test dependencies. This task differs from console in that it
@@ -338,32 +337,29 @@ <h3 id="configuration-level-tasks"><a class="header" href="#configuration-level-
 -->
 <h3 id="general-commands"><a class="header" href="#general-commands">General commands</a></h3>
 <ul>
-<li>
-<p><code>exit</code> or <code>quit</code> End the current interactive session or build.
+<li><code>shutdown</code> Shuts down the sbt server to end the current sbt session.</li>
+<li><code>exit</code> or <code>quit</code> End the current interactive session or build.
 Additionally, Ctrl+D (Unix) or Ctrl+Z (Windows) will exit the
-interactive prompt.</p>
-</li>
-<li>
-<p><code>help &lt;command&gt;</code> Displays detailed help for the specified command.
+interactive prompt.</li>
+<li><code>help &lt;command&gt;</code> Displays detailed help for the specified command.
 If the command does not exist, help lists detailed help for commands
 whose name or description match the argument, which is interpreted
 as a regular expression. If no command is provided, displays brief
 descriptions of the main commands. Related commands are tasks and
-settings.</p>
-</li>
-<li>
-<p><code>projects [add|remove &lt;URI&gt;]</code> List all available projects if no
-arguments provided or adds/removes the build at the provided URI.</p>
-<!-- (See [multi-project builds][Multi-Project] for details on multi-project
+settings.</li>
+<li><code>projects [add|remove &lt;URI&gt;]</code> List all available projects if no
+arguments provided or adds/removes the build at the provided URI.<!-- (See [multi-project builds][Multi-Project] for details on multi-project
 builds.) -->
 </li>
-<li>
-<p><code>project &lt;project-id&gt;</code> Change the current project to the project
-with ID <code>&lt;project-id&gt;</code>. Further operations will be done in the
-context of the given project.</p>
-<!-- (See [multi-project builds][Multi-Project] for
-details on multiple project builds.) -->
-</li>
+</ul>
+<!--
+-   `project <project-id>` Change the current project to the project
+    with ID `<project-id>`. Further operations will be done in the
+    context of the given project.
+    (See [multi-project builds][Multi-Project] for
+    details on multiple project builds.)
+-->
+<ul>
 <li>
 <p><a href="./watch.html">Watch command</a> <code>~ &lt;command&gt;</code> Executes the project specified action or method
 whenever source files change.</p>