Fix indentation for all pages

Author: rwinch

spring-shell-docs/modules/ROOT/pages/appendices-debugging.adoc

@@ -1,5 +1,5 @@
 [appendix]
 [#appendix-debugging]
-== Debugging
+= Debugging
 
 Please find more info about debugging from https://github.com/spring-projects/spring-shell/wiki/Debugging[project wiki].

spring-shell-docs/modules/ROOT/pages/appendices-techical-intro-commandcatalog.adoc

@@ -1,5 +1,6 @@
 [[command-catalog]]
-=== Command Catalog
+= Command Catalog
+
 The `CommandCatalog` interface defines how command registrations exist in
 a shell application. It is possible to dynamically register and de-register
 commands, which gives flexibility for use cases where possible commands
@@ -13,7 +14,7 @@ include::{snippets}/CommandCatalogSnippets.java[tag=snippet1]
 ====
 
 [[command-resolver]]
-==== Command Resolver
+== Command Resolver
 You can implement the `CommandResolver` interface and define a bean to dynamically
 resolve mappings from a command's name to its `CommandRegistration` instances. Consider
 the following example:
@@ -30,7 +31,7 @@ Thus, we advise not using it if a command resolution call takes a long time, as
 make the shell feel sluggish.
 
 [[command-catalog-customizer]]
-==== Command Catalog Customizer
+== Command Catalog Customizer
 You can use the `CommandCatalogCustomizer` interface to customize a `CommandCatalog`.
 Its main use is to modify a catalog. Also, within `spring-shell` auto-configuration, this
 interface is used to register existing `CommandRegistration` beans into a catalog.

spring-shell-docs/modules/ROOT/pages/appendices-techical-intro-commandcontext.adoc

@@ -1,5 +1,6 @@
 [[command-context]]
-=== Command Context
+= Command Context
+
 The `CommandContext` interface gives access to a currently running
 context. You can use it to get access to options:
 

spring-shell-docs/modules/ROOT/pages/appendices-techical-intro-execution.adoc

@@ -1,4 +1,5 @@
 [[command-execution]]
-=== Command Execution
+= Command Execution
+
 When command parsing has done its job and command registration has been resolved, command execution
 does the hard work of running the code.

spring-shell-docs/modules/ROOT/pages/appendices-techical-intro-parser.adoc

@@ -1,4 +1,5 @@
 [[command-parser]]
-=== Command Parser
+= Command Parser
+
 Before a command can be executed, we need to parse the command and whatever options the user may have provided. Parsing
 comes between command registration and command execution.

spring-shell-docs/modules/ROOT/pages/appendices-techical-intro-registration.adoc

@@ -1,13 +1,14 @@
 [#appendix-tech-intro-registration]
-=== Command Registration
+= Command Registration
+
 ifndef::snippets[:snippets: ../../test/java/org/springframework/shell/docs]
 
 Defining a command registration is a first step to introducing the structure of a command and its options
 and parameters. This is loosely decoupled from what happens later, such as parsing command-line input and running
 actual target code. Essentially, it is the definition of a command API that is shown to a user.
 
 [[commands]]
-==== Commands
+== Commands
 A command in a `spring-shell` structure is defined as an array of commands. This yields a
 structure similar to the following example:
 
@@ -25,7 +26,7 @@ NOTE: We do not currently support mapping commands to an explicit parent if sub-
 For example, `command1 sub1` and `command1 sub1 subsub1` cannot both be registered.
 
 [[interaction-mode]]
-==== Interaction Mode
+== Interaction Mode
 Spring Shell has been designed to work on two modes: interactive (which essentially
 is a `REPL` where you have an active shell instance throughout a series of commands) and
 non-interactive (where commands are executed one by one from a command line).
@@ -39,7 +40,7 @@ Also, being on an active `REPL` session may provide more information about what
 doing within an active session.
 
 [[options]]
-==== Options
+== Options
 Options can be defined as long and short, where the prefixing is `--` and `-`, respectively.
 The following examples show long and short options:
 
@@ -58,12 +59,12 @@ include::{snippets}/CommandRegistrationSnippets.java[tag=snippet2]
 ====
 
 [[target]]
-==== Target
+== Target
 The target defines the execution target of a command. It can be a method in a POJO,
 a `Consumer`, or a `Function`.
 
 [[method]]
-===== Method
+=== Method
 Using a `Method` in an existing POJO is one way to define a target.
 Consider the following class:
 
@@ -84,7 +85,7 @@ include::{snippets}/CommandTargetSnippets.java[tag=snippet12]
 ====
 
 [[function]]
-===== Function
+=== Function
 Using a `Function` as a target gives a lot of flexibility to handle what
 happens in a command execution, because you can handle many things manually by using
 a `CommandContext` given to a `Function`. The return type from a `Function` is
@@ -98,7 +99,7 @@ include::{snippets}/CommandTargetSnippets.java[tag=snippet2]
 ====
 
 [[consumer]]
-===== Consumer
+=== Consumer
 Using a `Consumer` is basically the same as using a `Function`, with the difference being
 that there is no return type. If you need to print something into a shell,
 you can get a reference to a `Terminal` from a context and print something

spring-shell-docs/modules/ROOT/pages/appendices-techical-intro-searchalgorithm.adoc

@@ -1,5 +1,6 @@
 [#appendix-tech-intro-searchalgorithm]
-=== Search Algorithms
+= Search Algorithms
+
 ifndef::snippets[:snippets: ../../test/java/org/springframework/shell/docs]
 
 `SearchMatch` is an interface to match _text_ with a _pattern_. Match
@@ -9,7 +10,7 @@ contains info about match positions and overall score of a match.
 https://github.com/junegunn/fzf[fzf].
 
 [[implementations]]
-==== Implementations
+== Implementations
 
 *FuzzyMatchV2Search*
 
@@ -22,7 +23,7 @@ Port of _fzf ExactMatchNaive_ algorithm. Simple exact match works more accuratel
 if you know what to search.
 
 [[searchmatch]]
-==== SearchMatch
+== SearchMatch
 
 Algorithms and default syntax are hidden inside package protected classes
 as we don't want to fully open these until we know API's are good to go
@@ -58,7 +59,7 @@ below table.
 |===
 
 [[examples]]
-==== Examples
+== Examples
 
 ====
 [source, java, indent=0]

spring-shell-docs/modules/ROOT/pages/appendices-techical-intro-theming.adoc

@@ -1,5 +1,6 @@
 [#appendix-tech-intro-theming]
-=== Theming
+= Theming
+
 ifndef::snippets[:snippets: ../../test/java/org/springframework/shell/docs]
 
 Styling in a theming is provided by a use of a _AttributedString_ from `JLine`.

spring-shell-docs/modules/ROOT/pages/appendices-techical-intro.adoc

@@ -1,6 +1,7 @@
 [appendix]
 [#appendix-tech-intro]
-== Techical Introduction
+= Techical Introduction
+
 This appendix contains information for developers and others who would like to know more about how Spring Shell
 works internally and what its design decisions are.
 

spring-shell-docs/modules/ROOT/pages/appendices-tui-catalog.adoc

@@ -1,5 +1,6 @@
 [#appendix-tui-catalog]
-=== Catalog App
+= Catalog App
+
 ifndef::snippets[:snippets: ../../test/java/org/springframework/shell/docs]
 
 Catalog application is showing various ways how Terminal UI Framework can be used.
@@ -8,6 +9,6 @@ a reference application as it's using most of the features available and tries
 to follow best practices.
 
 [[create-scenario]]
-==== Create Scenario
+== Create Scenario
 Every `Scenario` essentially is a sample code of a `View` as that's what catalog
 app demonstrates.

spring-shell-docs/modules/ROOT/pages/appendices-tui-control.adoc

@@ -1,5 +1,6 @@
 [#appendix-tui-control]
-=== Control
+= Control
+
 ifndef::snippets[:snippets: ../../test/java/org/springframework/shell/docs]
 
 _Control_ draws something into a screen with a given bounds.

spring-shell-docs/modules/ROOT/pages/appendices-tui-eventloop.adoc

@@ -1,5 +1,6 @@
 [#appendix-tui-eventloop]
-=== EventLoop
+= EventLoop
+
 ifndef::snippets[:snippets: ../../test/java/org/springframework/shell/docs]
 
 _EventLoop_ is a central system handling eventing in a framework.

spring-shell-docs/modules/ROOT/pages/appendices-tui-keyhandling.adoc

@@ -1,5 +1,6 @@
 [#appendix-tui-keyhandling]
-=== Key Handling
+= Key Handling
+
 ifndef::snippets[:snippets: ../../test/java/org/springframework/shell/docs]
 
 Handles incoming key events.

spring-shell-docs/modules/ROOT/pages/appendices-tui-mousehandling.adoc

@@ -1,5 +1,6 @@
 [#appendix-tui-mousehandling]
-=== Mouse Handling
+= Mouse Handling
+
 ifndef::snippets[:snippets: ../../test/java/org/springframework/shell/docs]
 
 Handles incoming mouse events.

spring-shell-docs/modules/ROOT/pages/appendices-tui-screen.adoc

@@ -1,5 +1,6 @@
 [#appendix-tui-screen]
-=== Screen
+= Screen
+
 ifndef::snippets[:snippets: ../../test/java/org/springframework/shell/docs]
 
 _Screen_ is an abstraction providing higher level concept to draw something

spring-shell-docs/modules/ROOT/pages/appendices-tui-view.adoc

@@ -1,5 +1,6 @@
 [#appendix-tui-view]
-=== View
+= View
+
 ifndef::snippets[:snippets: ../../test/java/org/springframework/shell/docs]
 
 _View_ extends _Control_ providing integration into event loop.

spring-shell-docs/modules/ROOT/pages/appendices-tui.adoc

@@ -1,6 +1,7 @@
 [appendix]
 [#appendix-tech-intro-tui]
-== Terminal UI
+= Terminal UI
+
 ifndef::snippets[:snippets: ../../test/java/org/springframework/shell/docs]
 
 This is a technical introduction to _UI Framework_.

spring-shell-docs/modules/ROOT/pages/getting-started.adoc

@@ -1,13 +1,14 @@
 [[getting-started]]
-== Getting Started
+= Getting Started
+
 To see what Spring Shell has to offer, we can write a trivial _hello world_
 shell application that has a simple argument.
 
 IMPORTANT: _Spring Shell_ is based on _Spring Boot_ {spring-boot-version} and
 _Spring Framework_ {spring-version} and thus requires _JDK 17_.
 
 [[creating-a-project]]
-=== Creating a Project
+== Creating a Project
 
 For the purpose of this tutorial, we create a simple Spring Boot application by
 using https://start.spring.io where you can choose _Spring Shell_ dependency.
@@ -98,7 +99,7 @@ TIP: Check out <<using-shell-customization-logging>> making logging to work
 better with shell apps.
 
 [[using-spring-shell-your-first-command]]
-=== Your First Command
+== Your First Command
 
 Now we can add our first command. To do so, create a new class (named whatever you want) and
 annotate it with `@ShellComponent` which is a variation of `@Component` that is used to restrict

spring-shell-docs/modules/ROOT/pages/introduction.adoc

@@ -1,5 +1,6 @@
 [[what-is-spring-shell?]]
-== What is Spring Shell?
+= What is Spring Shell?
+
 Not all applications need a fancy web user interface.
 Sometimes, interacting with an application through an interactive terminal is
 the most appropriate way to get things done.

spring-shell-docs/modules/ROOT/pages/using-shell-basics-reading.adoc

@@ -1,5 +1,5 @@
 [[using-shell-basics-reading]]
-=== Reading Docs
+= Reading Docs
 
 Throughout this documentation, we make references to configuring something by using
 annotations or programmatic examples.

spring-shell-docs/modules/ROOT/pages/using-shell-basics.adoc

@@ -1,5 +1,6 @@
 [[using-shell-basics]]
-== Basics
+= Basics
+
 This section covers the basics of Spring Shell. Before going on to define actual commands and options,
 we need to go through some of the fundamental concepts of Spring Shell.
 

spring-shell-docs/modules/ROOT/pages/using-shell-building.adoc

@@ -1,10 +1,10 @@
 [[using-shell-building]]
-== Building
+= Building
 
 This section covers how to build a Spring Shell application.
 
 [[native]]
-=== Native Support
+== Native Support
 
 Support for compiling _Spring Shell_ application into a _GraalVM_ binary
 mostly comes from _Spring Framework_ and _Spring Boot_ where feature is

spring-shell-docs/modules/ROOT/pages/using-shell-commands-availability.adoc

@@ -1,5 +1,5 @@
 [[dynamic-command-availability]]
-=== Dynamic Command Availability
+= Dynamic Command Availability
 
 Registered commands do not always make sense, due to the internal state of the application.
 For example, there may be a `download` command, but it only works once the user has used `connect` on a remote

spring-shell-docs/modules/ROOT/pages/using-shell-commands-builtin-clear.adoc

@@ -1,4 +1,5 @@
 [[built-in-commands-clear]]
-==== Clear
+= Clear
+
 The `clear` command does what you would expect and clears the screen, resetting the prompt
 in the top left corner.

spring-shell-docs/modules/ROOT/pages/using-shell-commands-builtin-completion.adoc

@@ -1,5 +1,5 @@
 [[built-in-commands-completion]]
-==== Completion
+= Completion
 
 The `completion` command set lets you create script files that can be used
 with am OS shell implementations to provide completion. This is very useful when

spring-shell-docs/modules/ROOT/pages/using-shell-commands-builtin-exit.adoc

@@ -1,5 +1,5 @@
 [[built-in-commands-exit]]
-==== Exit
+= Exit
 
 The `quit` command (also aliased as `exit`) requests the shell to quit, gracefully
 closing the Spring application context. If not overridden, a JLine `History` bean writes a history of all

spring-shell-docs/modules/ROOT/pages/using-shell-commands-builtin-help.adoc

@@ -1,5 +1,5 @@
 [[built-in-commands-help]]
-==== Help
+= Help
 
 Running a shell application often implies that the user is in a graphically limited
 environment. Also, while we are nearly always connected in the era of mobile phones,

spring-shell-docs/modules/ROOT/pages/using-shell-commands-builtin-history.adoc

@@ -1,5 +1,5 @@
 [[built-in-commands-history]]
-==== History
+= History
 
 The `history` command shows the history of commands that has been executed.
 

spring-shell-docs/modules/ROOT/pages/using-shell-commands-builtin-script.adoc

@@ -1,5 +1,5 @@
 [[built-in-commands-script]]
-==== Script
+= Script
 
 The `script` command accepts a local file as an argument and replays commands found there, one at a time.
 

spring-shell-docs/modules/ROOT/pages/using-shell-commands-builtin-stacktrace.adoc

@@ -1,5 +1,5 @@
 [[built-in-commands-stacktrace]]
-==== Stacktrace
+= Stacktrace
 
 When an exception occurs inside command code, it is caught by the shell and a simple, one-line message is displayed
 so as not to overflow the user with too much information.

spring-shell-docs/modules/ROOT/pages/using-shell-commands-builtin-version.adoc

@@ -1,5 +1,5 @@
 [[built-in-commands-version]]
-==== Version
+= Version
 
 The `version` command shows existing build and git info by integrating into
 Boot's `BuildProperties` and `GitProperties` if those exist in the shell application.

spring-shell-docs/modules/ROOT/pages/using-shell-commands-builtin.adoc

@@ -1,5 +1,5 @@
 [[built-in-commands]]
-=== Built-In Commands
+= Built-In Commands
 
 include::using-shell-commands-builtin-help.adoc[]