Update documentation

Author: fmbenhassine

spring-shell-docs/modules/ROOT/pages/appendices/techintro/index.adoc

@@ -1,6 +1,6 @@
 [appendix]
 [#appendix-tech-intro]
-= Techical Introduction
+= Technical Introduction
 :page-section-summary-toc: 1
 
 This appendix contains information for developers and others who would like to know more about how Spring Shell

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

@@ -4,10 +4,10 @@
 
 ifndef::snippets[:snippets: ../../../../../src/test/java/org/springframework/shell/docs]
 
-Catalog application is showing various ways how Terminal UI Framework can be used.
-In this section we discuss how this application works. It can be considered to be
+Catalog application shows various ways how the Terminal UI Framework can be used.
+In this section, we discuss how this application works. It can be considered as
 a reference application as it's using most of the features available and tries
-to follow best practices.
+to follow the best practices.
 
 [[create-scenario]]
 == Create Scenario

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

@@ -5,9 +5,9 @@
 
 ifndef::snippets[:snippets: ../../test/java/org/springframework/shell/docs]
 
-This is a technical introduction to _UI Framework_.
+This is a technical introduction to the _UI Framework_.
 
-_UI Framework_ is a toolkit to build rich console apps.
+The _UI Framework_ is a toolkit to build rich console apps.
 
 
 

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

@@ -2,7 +2,7 @@
 = View Development
 :page-section-summary-toc: 1
 
-While a _view_ just need to implement `View` it's usually convenient to just
+While a _view_ just needs to implement `View`, it's usually convenient to just
 use `BoxView` as a parent.
 
 [[register-bindings]]

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

@@ -5,13 +5,13 @@
 Throughout this documentation, we make references to configuring something by using
 annotations or programmatic examples.
 
-NOTE: There are two annotation models, xref:commands/registration/annotation.adoc[annotations]
-referred to new annotation model, xref:commands/registration/legacyannotation.adoc[legacy annotations]
-referred to old legacy annotation model.
+NOTE: There are two annotation models: the xref:commands/registration/annotation.adoc[annotations] model
+referred to as the new annotation model, and the xref:commands/registration/legacyannotation.adoc[legacy annotations]
+model referred to as the old legacy annotation model.
 
-Old legacy annotation model mostly relates to use of `@ShellMethod` and `@ShellOption` and
-new annotation model relates to use of `@Command`.
+The old legacy annotation model mostly relates to the use of `@ShellMethod` and `@ShellOption` and
+the new annotation model relates to the use of `@Command`.
 
 The programmatic model is how things are actually registered, even if you use annotations.
 
-NOTE: The documentation structure is getting revised to clarify how to provide configurations in separate ways. Thank you for understanding while that work is still in progress. 
+NOTE: The documentation structure is getting revised to clarify how to provide configurations in separate ways.

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

@@ -25,17 +25,17 @@ traditionally been relatively complex process while it may look like
 there's not that much happening as it's all just text.
 
 Remember all those old manual typewriters or matrix printers?
-A character is printed where a cursor is which then need to be moved
+A character is printed then a cursor needs to be moved
 if printing in a different position. In a nutshell that's how current
 terminal emulators work.
 
-To access and understand existing terminal emulator environment better
+To access and understand existing terminal emulators environment better,
 JLine can use native code via its own shared libraries. JLine detects
 which providers are present and then makes a choice which one to use.
 Traditionally there's been 3 providers, `jansi`, `jni` and `jna` which
 should all provide same functionalities.
 
-Our starters can be used to spesifically pick some of these JLine
+Our starters can be used to specifically pick some of these JLine
 providers.
 
 == FFM
@@ -127,7 +127,7 @@ When gradle build is run with `./gradlew nativeCompile` you should get binary
 under `build/native/nativeCompile` directory.
 
 For `maven` use `spring-boot-starter-parent` as parent and you'll get `native`
-profile which can be used to do a compilation. You need to configure metadata repository
+profile which can be used to do a native compilation. You need to configure metadata repository:
 
 [source, xml, subs=attributes+]
 ----

spring-shell-docs/modules/ROOT/pages/commands/alias.adoc

@@ -8,10 +8,9 @@ cases where you want to create a shorter version of a command or going
 through a complete command rename while keeping old one temporarily in
 place.
 
-Format for _alias_ is slighly different than a _command_. When _command_
+The format of _alias_ is slightly different from a _command_. When _command_
 is defined as an array it's concatenated together into a single command.
-When _alias_ is defined as an array it's used to create a separate
-aliases.
+When _alias_ is defined as an array it's used to create separate aliases.
 
 Aliases with a plain `CommandRegistration` is simple and clear as you
 get exactly what you define as there's no "magic" in it.

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

@@ -2,5 +2,5 @@
 = Clear
 :page-section-summary-toc: 1
 
-The `clear` command does what you would expect and clears the screen, resetting the prompt
+The `clear` command clears the screen, resetting the prompt
 in the top left corner.

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

@@ -2,8 +2,8 @@
 = Completion
 :page-section-summary-toc: 1
 
-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
+The `completion` command lets you create script files that can be used
+with an OS shell implementation to provide completion. This is very useful when
 working with non-interactive mode.
 
-Currently, the only implementation is for bash, which works with `bash` sub-command.
+Currently, the only implementation is for bash, which works with the `bash` sub-command.

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

@@ -2,9 +2,7 @@
 = 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,
-accessing a web browser or any other rich UI application (such as a PDF viewer) may not always
-be possible. This is why it is important that the shell commands are correctly self-documented, and this is where the `help`
+environment. This is why it is important that the shell commands are correctly self-documented, and this is where the `help`
 command comes in.
 
 Typing `help` + `ENTER` lists all the commands known to the shell (including xref:commands/availability.adoc[unavailable] commands)