Tweak some wording

Author: bbatsov

doc/modules/ROOT/pages/basics/up_and_running.adoc

@@ -41,12 +41,6 @@ CIDER figures out this by parsing the output from the command and waiting for a
 TIP: You can see the exact command that `cider-jack-in` invoked in your minibuffer, while
 waiting for nREPL to start. You can also find this command in Emacs's `+*Messages*+` buffer.
 
-IMPORTANT: `cider-jack-in` is mainly designed for local development with files on a local machine and 
-the nREPL process running on the same machine. It has as well features to support various remote / container
-scenarious, see below. Due to the large variation of remote scenarious it cannot support all of them, 
-so in some cases a manual nREPL start and usage of `cider-connect` is needed.
-
-
 In some cases one project might have multiple project markers in it - e.g. `project.clj` and `deps.edn`.
 When this happens CIDER will prompt you to select the build tool to use. You can override this behavior
 by setting the variable `cider-preferred-build-tool`. While you can set it globally in your Emacs config,
@@ -58,6 +52,12 @@ most of the time you'd probably want to have a project-specific setting for it i
   (cider-preferred-build-tool . lein)))
 ----
 
+NOTE: `cider-jack-in` is mainly designed for local development (with files on a
+local machine and the nREPL process running on the same machine). It does support
+various common remote/container scenarios, as documented later in this section. Due
+to the large variation of remote scenarios it cannot support all of them, so in
+some cases a manual nREPL start and usage of `cider-connect` might be a better option.
+
 === Auto-Injecting Dependencies
 
 While CIDER's core functionality requires nothing more than an nREPL server,