Adjust title order in learning toctree and fix some typos

source/learn.md

@@ -155,9 +155,9 @@ In print
 :::{toctree}
 :hidden:
 
-learn/quickstart/index
-learn/best_practices/index
 learn/os_setup/index
+learn/quickstart/index
 learn/building_programs/index
+learn/best_practices/index
 learn/intrinsics/index
 :::

source/learn/best_practices/index.md

@@ -12,15 +12,15 @@ and programming in general.
 ```{toctree}
 :maxdepth: 2
 :hidden:
-Allocatable Arrays <allocatable_arrays>
-Arrays <arrays>
-Callbacks <callbacks>
-Element-wise Operations on Array <element_operations>
-File Input/Output <file_io>
+Fortran Style Guide <style_guide>
 Floating Point Numbers <floating_point>
 Integer Division <integer_division>
 Modules and Programs <modules_programs>
+Arrays <arrays>
 Multidimensional Arrays <multidim_arrays>
-Fortran Style Guide <style_guide>
+Element-wise Operations on Array <element_operations>
+Allocatable Arrays <allocatable_arrays>
+File Input/Output <file_io>
+Callbacks <callbacks>
 Type Casting in Callbacks <type_casting>
 ```

source/learn/building_programs/build_tools.md

@@ -56,8 +56,9 @@ called `Makefile` or `makefile`, which usually leads to compiling a program
 from the provided source code.
 
 ::::{tip}
-For an in-depth `make` tutorial lookup its info page. There is an online version of this <a href=“https://www.gnu.org/software/make/manual/make.html“ target=“_blank“ rel=“noopener“>info page, available.
+For an in-depth `make` tutorial lookup its info page. There is an online version of this <a href="https://www.gnu.org/software/make/manual/make.html" target="_blank" rel="noopener">info page</a>, available.
 ::::
+
 We will start with the basics from your clean source directory. Create and open
 the file `Makefile`, we start with a simple rule called _all_:
 
@@ -306,7 +307,7 @@ While, it seems like an interesting feature to use, it tends to lead to
 surprising and unexpected outcomes. Usually, when defining variables like your
 compiler, there is little reason to actually use the recursive expansion at all.
 
-The same can easily be archived using the `:=` declaration:
+The same can easily be achieved using the `:=` declaration:
 
 ```make
 all:
@@ -533,7 +534,7 @@ CMake knows the details how to build the executable from the specified sources,
 so we do not have to worry about the actual steps in the build process.
 
 ::::{tip}
-CMake's offical reference can be found at the
+CMake's official reference can be found at the
 <a href="https://cmake.org/cmake/help/latest/", target="\_blank" rel="noopener">CMake webpage</a>.
 It is organised in manpages, which are also available with your local CMake
 installation as well using `man cmake`. While it covers all functionality of

source/learn/building_programs/include_files.md

@@ -5,7 +5,7 @@ same directory or organised in some convenient directory tree. The
 details of the organisation depend on personal taste, arrangements made
 by the group of developers you belong to, or simply the history of the
 program. Whatever the directory structure is, you will encounter a
-situation where the compiler needs assistence in order to compile a
+situation where the compiler needs assistance in order to compile a
 particular source file:
 
 - Fortran (and other languages) has the possibility to include an

source/learn/building_programs/index.md

@@ -45,13 +45,14 @@ consider all these details. In fact, this is the sort of things that is
 taken care of by the build process: the compiler and the linker.
 
 ```{toctree}
+:maxdepth: 2
 :hidden:
-Build tools <build_tools>
 Compiling the source code <compiling_source>
-Distributing your programs <distributing>
-Include files and modules <include_files>
 Linking the objects <linking_pieces>
+Run-time libraries <runtime_libraries>
+Include files and modules <include_files>
 Managing libraries (static and dynamic libraries) <managing_libraries>
+Build tools <build_tools>
 An introduction to make <project_make>
-Run-time libraries <runtime_libraries>
+Distributing your programs <distributing>
 ```

source/learn/building_programs/linking_pieces.md

@@ -34,7 +34,7 @@ achieve this, but one is to put it in a different source file. We can
 give the general program to a user and they provide a specific source code.
 
 Assume for the sake of the example that the function is implemented in a
-source file "function.f90" as:
+source file "functions.f90" as:
 
 ```fortran
 module user_functions

source/learn/building_programs/managing_libraries.md

@@ -64,7 +64,7 @@ the program with a new version of the library.
 
 A flexible alternative is to use the so-called dynamic libraries. These
 libraries remain outside the executable program and as a consequence
-can be replaced without rebulding the entire program. Compilers and
+can be replaced without rebuilding the entire program. Compilers and
 indeed the operating system itself rely heavily on such dynamic
 libraries. You could consider dynamic libraries as a sort of executable
 programs that need a bit of help to be run.

source/learn/os_setup/index.md

@@ -26,8 +26,8 @@ _The choice of text editors and IDEs has been controversial among the developers
 ```{toctree}
 :hidden:
 Choosing a compiler <choose_compiler>
-IDEs <ides>
 Installing GFortran <install_gfortran>
 Text Editors <text_editors>
+IDEs <ides>
 Smart Tips <tips>
 ```

source/learn/quickstart/index.md

@@ -11,10 +11,10 @@ Use the _Next_ button at the bottom to start the tutorial with a _Hello World_ e
 ```{toctree}
 :maxdepth: 2
 :hidden:
-Arrays and strings <arrays_strings>
-Derived Types <derived_types>
 Hello world <hello_world>
+Variables <variables>
+Arrays and strings <arrays_strings>
 Operators and flow control <operators_control_flow>
 Organising code structure <organising_code>
-Variables <variables>
+Derived Types <derived_types>
 ```

source/learn/quickstart/variables.md

@@ -179,7 +179,7 @@ end program float
 
 > Always use a `kind` suffix for floating-point literal constants.
 
-**Example:** C-interoperable `kind`s
+**Example:** C-interoperable `kind`
 
 ```fortran
 program float