Polish naming in docs

- Relates #637

spring-shell-docs/src/main/asciidoc/using-shell-commands-registration-legacyannotation.adoc

@@ -1,5 +1,5 @@
 [[commands-registration-legacyannotation]]
-==== Annotation Legacy
+==== Legacy Annotation
 ifndef::snippets[:snippets: ../../test/java/org/springframework/shell/docs]
 
 When you use the standard API, methods on beans are turned into executable commands, provided that:

spring-shell-docs/src/main/asciidoc/using-shell-commands-registration.adoc

@@ -14,8 +14,8 @@ and removed. Secondly so that we're able to provide same set of features than us
 `CommandRegistration`. Creating new a annotation model allows us to rethink and modernise that
 part without breaking existing applications.
 
-include::using-shell-commands-registration-annotation.adoc[]
-
 include::using-shell-commands-registration-programmatic.adoc[]
 
+include::using-shell-commands-registration-annotation.adoc[]
+
 include::using-shell-commands-registration-legacyannotation.adoc[]

spring-shell-docs/src/main/asciidoc/using-shell-options-basics-programmatic.adoc

@@ -1,5 +1,6 @@
 [[using-shell-options-basics-registration]]
-==== Registration
+[[using-shell-options-basics-programmatic]]
+==== Programmatic
 ifndef::snippets[:snippets: ../../test/java/org/springframework/shell/docs]
 
 Programmatic way with `CommandRegistration` is to use `withOption` to define

spring-shell-docs/src/main/asciidoc/using-shell-options-basics.adoc

@@ -6,8 +6,8 @@ This section gives a generic idea how an option can be defined. Following
 sections, beyond basics, discuss more about how various option behaviour
 can be accomplished for a particular use case.
 
+include::using-shell-options-basics-programmatic.adoc[]
+
 include::using-shell-options-basics-annotation.adoc[]
 
-include::using-shell-options-basics-registration.adoc[]
-
 include::using-shell-options-basics-legacyannotation.adoc[]