Reorder OS-related FAQ categories

Author: mpilgrem

doc/faq.md

@@ -476,59 +476,6 @@
 
     See the [Azure CI](topics/azure_ci.md) documentation.
 
-## Windows-related
-
-??? question "What is licensing restrictions on Windows?"
-
-    Currently, on Windows, GHC produces binaries linked statically with
-    [GNU Multiple Precision Arithmetic Library](https://gmplib.org/) (GMP), which is
-    used by [integer-gmp](https://hackage.haskell.org/package/integer-gmp) library
-    to provide big integer implementation for Haskell. Contrary to the majority of
-    Haskell code licensed under permissive BSD3 license, GMP library is licensed
-    under LGPL, which means resulting binaries
-    [have to be provided with source code or object files](http://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynamic).
-    That may or may not be acceptable for your situation. Current workaround is to
-    use GHC built with alternative big integer implementation called
-    `integer-simple`, which is free from LGPL limitations as it's pure Haskell and
-    does not use GMP.  Unfortunately it has yet to be available out of the box with
-    Stack. See issue [#399](https://github.com/commercialhaskell/stack/issues/399)
-    for the ongoing effort and information on workarounds.
-
-??? question "How to get a working executable on Windows?"
-
-    When executing a binary after building with `stack build` (e.g. for target
-    "foo"), the command `foo.exe` might complain about missing runtime libraries
-    (whereas `stack exec foo` works).
-
-    Windows is not able to find the necessary C++ libraries from the standard
-    prompt because they're not in the PATH environment variable. `stack exec` works
-    because it's modifying PATH to include extra things.
-
-    Those libraries are shipped with GHC (and, theoretically in some cases, MSYS2).
-    The easiest way to find them is `stack exec which`. For example, command:
-
-    ~~~text
-    stack exec -- which libstdc++-6.dll
-    /c/Users/Michael/AppData/Local/Programs/stack/i386-windows/ghc-7.8.4/mingw/bin/libstdc++-6.dll
-    ~~~
-
-    A quick workaround is adding this path to the PATH environment variable or
-    copying the files somewhere Windows finds them (see
-    https://msdn.microsoft.com/de-de/library/7d83bc18.aspx).
-
-    See issue [#425](https://github.com/commercialhaskell/stack/issues/425).
-
-    Another issue that may arise with building on Windows is as follows. The default
-    location of Stack's programs folder is `%LOCALAPPDATA\Programs\stack`. If there
-    is a space character in the `%LOCALAPPDATA%` path this may, in some
-    circumstances, cause problems with building packages that make use of the GNU
-    project's `autoconf` package and `configure` shell script files. It may be
-    necessary to override the default location of Stack's programs folder. See the
-    [local-programs-path](configure/yaml/non-project.md#local-programs-path) option
-    for more information.
-
-    See issue [#4726](https://github.com/commercialhaskell/stack/issues/4726).
-
 ## Setup-related
 
 ??? question "Where is Stack installed?"
@@ -658,3 +605,56 @@
 
     Issue [#4009](https://github.com/commercialhaskell/stack/issues/4009) goes into
     further detail.
+
+## Windows-related
+
+??? question "What is licensing restrictions on Windows?"
+
+    Currently, on Windows, GHC produces binaries linked statically with
+    [GNU Multiple Precision Arithmetic Library](https://gmplib.org/) (GMP), which is
+    used by [integer-gmp](https://hackage.haskell.org/package/integer-gmp) library
+    to provide big integer implementation for Haskell. Contrary to the majority of
+    Haskell code licensed under permissive BSD3 license, GMP library is licensed
+    under LGPL, which means resulting binaries
+    [have to be provided with source code or object files](http://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynamic).
+    That may or may not be acceptable for your situation. Current workaround is to
+    use GHC built with alternative big integer implementation called
+    `integer-simple`, which is free from LGPL limitations as it's pure Haskell and
+    does not use GMP.  Unfortunately it has yet to be available out of the box with
+    Stack. See issue [#399](https://github.com/commercialhaskell/stack/issues/399)
+    for the ongoing effort and information on workarounds.
+
+??? question "How to get a working executable on Windows?"
+
+    When executing a binary after building with `stack build` (e.g. for target
+    "foo"), the command `foo.exe` might complain about missing runtime libraries
+    (whereas `stack exec foo` works).
+
+    Windows is not able to find the necessary C++ libraries from the standard
+    prompt because they're not in the PATH environment variable. `stack exec` works
+    because it's modifying PATH to include extra things.
+
+    Those libraries are shipped with GHC (and, theoretically in some cases, MSYS2).
+    The easiest way to find them is `stack exec which`. For example, command:
+
+    ~~~text
+    stack exec -- which libstdc++-6.dll
+    /c/Users/Michael/AppData/Local/Programs/stack/i386-windows/ghc-7.8.4/mingw/bin/libstdc++-6.dll
+    ~~~
+
+    A quick workaround is adding this path to the PATH environment variable or
+    copying the files somewhere Windows finds them (see
+    https://msdn.microsoft.com/de-de/library/7d83bc18.aspx).
+
+    See issue [#425](https://github.com/commercialhaskell/stack/issues/425).
+
+    Another issue that may arise with building on Windows is as follows. The default
+    location of Stack's programs folder is `%LOCALAPPDATA\Programs\stack`. If there
+    is a space character in the `%LOCALAPPDATA%` path this may, in some
+    circumstances, cause problems with building packages that make use of the GNU
+    project's `autoconf` package and `configure` shell script files. It may be
+    necessary to override the default location of Stack's programs folder. See the
+    [local-programs-path](configure/yaml/non-project.md#local-programs-path) option
+    for more information.
+
+    See issue [#4726](https://github.com/commercialhaskell/stack/issues/4726).