Alphabetize the Docs on Dependencies

Persumably this list of was supposed to be alphabetized, but a few of
the items were out of order. This confused me because I was looking for
numpy, got the the Os and thought it wasn't there.

Author: kjmeagher

docs/markdown/Dependencies.md

@@ -427,6 +427,34 @@ foreach h : check_headers
 endforeach
 ```
 
+## DIA SDK
+
+*(added 1.6.0)*
+
+Microsoft's Debug Interface Access SDK (DIA SDK) is available only on Windows,
+when using msvc, clang-cl or clang compiler from Microsoft Visual Studio.
+
+The DIA SDK runtime is not statically linked to target. The default usage
+method requires the runtime DLL (msdiaXXX.dll) to be manually registered in the
+OS with `regsrv32.exe` command, so it can be loaded using `CoCreateInstance`
+Windows function.
+
+Alternatively, you can use meson to copy the DIA runtime DLL to your build
+directory, and load it dynamically using `NoRegCoCreate` function provided by
+the DIA SDK. To facilitate this, you can read DLL path from dependency's
+variable 'dll' and use fs module to copy it. Example:
+
+```meson
+dia = dependency('diasdk', required: true)
+fs = import('fs')
+fs.copyfile(dia.get_variable('dll'))
+
+conf = configuration_data()
+conf.set('msdia_dll_name', fs.name(dia_dll_name))
+```
+
+Only the major version is available (eg. version is `14` for msdia140.dll).
+
 ## dl (libdl)
 
 *(added 0.62.0)*
@@ -448,18 +476,18 @@ providing them instead.
 GCC will use OpenCoarrays if present to implement coarrays, while Intel and NAG
 use internal coarray support.
 
-## GPGME
-
-*(added 0.51.0)*
-
-`method` may be `auto`, `config-tool` or `pkg-config`.
-
 ## GL
 
 This finds the OpenGL library in a way appropriate to the platform.
 
 `method` may be `auto`, `pkg-config` or `system`.
 
+## GPGME
+
+*(added 0.51.0)*
+
+`method` may be `auto`, `config-tool` or `pkg-config`.
+
 ## GTest and GMock
 
 GTest and GMock come as sources that must be compiled as part of your
@@ -649,6 +677,14 @@ language-specific, you must specify the requested language using the
 
 Meson uses pkg-config to find NetCDF.
 
+## NumPy
+
+*(added 1.4.0)*
+
+`method` may be `auto`, `pkg-config`, or `config-tool`.
+`dependency('numpy')` supports regular use of the NumPy C API.
+Use of `numpy.f2py` for binding Fortran code isn't yet supported.
+
 ## ObjFW
 
 *(added 1.5.0)*
@@ -694,14 +730,6 @@ The `language` keyword may used.
 
 `method` may be `auto`, `pkg-config`, `system` or `cmake`.
 
-## NumPy
-
-*(added 1.4.0)*
-
-`method` may be `auto`, `pkg-config`, or `config-tool`.
-`dependency('numpy')` supports regular use of the NumPy C API.
-Use of `numpy.f2py` for binding Fortran code isn't yet supported.
-
 ## pcap
 
 *(added 0.42.0)*
@@ -859,34 +887,6 @@ version.
 
 *New in 0.54.0* the `system` method.
 
-## DIA SDK
-
-*(added 1.6.0)*
-
-Microsoft's Debug Interface Access SDK (DIA SDK) is available only on Windows,
-when using msvc, clang-cl or clang compiler from Microsoft Visual Studio.
-
-The DIA SDK runtime is not statically linked to target. The default usage
-method requires the runtime DLL (msdiaXXX.dll) to be manually registered in the
-OS with `regsrv32.exe` command, so it can be loaded using `CoCreateInstance`
-Windows function.
-
-Alternatively, you can use meson to copy the DIA runtime DLL to your build
-directory, and load it dynamically using `NoRegCoCreate` function provided by
-the DIA SDK. To facilitate this, you can read DLL path from dependency's
-variable 'dll' and use fs module to copy it. Example:
-
-```meson
-dia = dependency('diasdk', required: true)
-fs = import('fs')
-fs.copyfile(dia.get_variable('dll'))
-
-conf = configuration_data()
-conf.set('msdia_dll_name', fs.name(dia_dll_name))
-```
-
-Only the major version is available (eg. version is `14` for msdia140.dll).
-
 <hr>
 <a name="footnote1">1</a>: They may appear to be case-insensitive, if the
     underlying file system happens to be case-insensitive.