ci: Simplify CI workflow configuration and improve documentation form…

…atting

.github/workflows/ci-coverage-ubuntu-full-qt-tests.yml

@@ -8,9 +8,6 @@ on:
 jobs:
   build:
     runs-on: ubuntu-latest
-    strategy:
-        matrix:
-          os: [x86_64-linux-gnu]
 
     steps:
       - uses: actions/checkout@v2

doc/build-unix.md

@@ -1,11 +1,11 @@
-UNIX BUILD NOTES
-====================
+# UNIX BUILD NOTES
+
 Some notes on how to build DigiByte Core in Unix.
 
 (For BSD specific instructions, see `build-*bsd.md` in this directory.)
 
-Note
----------------------
+## Note
+
 Always use absolute paths to configure and compile DigiByte Core and the dependencies.
 For example, when specifying the path of the dependency:
 
@@ -14,20 +14,18 @@ For example, when specifying the path of the dependency:
 Here BDB_PREFIX must be an absolute path - it is defined using $(pwd) which ensures
 the usage of the absolute path.
 
-To Build
----------------------
+## To Build
 
-```bash
-./autogen.sh
-./configure
-make # use "-j N" for N parallel jobs
-make install # optional
-```
+    ```bash
+    ./autogen.sh
+    ./configure
+    make # use "-j N" for N parallel jobs
+    make install # optional
+    ```
 
 This will build digibyte-qt as well, if the dependencies are met.
 
-Dependencies
----------------------
+### Dependencies
 
 These dependencies are required:
 
@@ -51,14 +49,12 @@ Optional dependencies:
 
 For the versions used, see [dependencies.md](dependencies.md)
 
-Memory Requirements
---------------------
+### Memory Requirements
 
 C++ compilers are memory-hungry. It is recommended to have at least 1.5 GB of
 memory available when compiling DigiByte Core. On systems with less, gcc can be
 tuned to conserve memory with additional CXXFLAGS:
 
-
     ./configure CXXFLAGS="--param ggc-min-expand=1 --param ggc-min-heapsize=32768"
 
 Alternatively, or in addition, debugging information can be skipped for compilation. The default compile flags are
@@ -74,7 +70,7 @@ Finally, clang (often less resource hungry) can be used instead of gcc, which is
 
 ### Ubuntu & Debian
 
-#### Dependency Build Instructions
+#### Ubuntu & Debian Dependency Build Instructions
 
 Build requirements:
 
@@ -124,10 +120,9 @@ libqrencode (optional) can be installed with:
 Once these are installed, they will be found by configure and a digibyte-qt executable will be
 built by default.
 
-
 ### Fedora
 
-#### Dependency Build Instructions
+#### Fedora Dependency Build Instructions
 
 Build requirements:
 
@@ -179,13 +174,12 @@ libqrencode (optional) can be installed with:
 Once these are installed, they will be found by configure and a digibyte-qt executable will be
 built by default.
 
-Notes
------
+## Notes
+
 The release is built with GCC and then "strip digibyted" to strip the debug
 symbols, which reduces the executable size by about 90%.
 
-miniupnpc
----------
+## miniupnpc
 
 [miniupnpc](https://miniupnp.tuxfamily.org) may be used for UPnP port mapping.  It can be downloaded from [here](
 https://miniupnp.tuxfamily.org/files/).  UPnP support is compiled in and
@@ -195,8 +189,7 @@ turned off by default.  See the configure options for UPnP behavior desired:
     --disable-upnp-default   (the default) UPnP support turned off by default at runtime
     --enable-upnp-default    UPnP support turned on by default at runtime
 
-libnatpmp
----------
+## libnatpmp
 
 [libnatpmp](https://miniupnp.tuxfamily.org/libnatpmp.html) may be used for NAT-PMP port mapping. It can be downloaded
 from [here](https://miniupnp.tuxfamily.org/files/). NAT-PMP support is compiled in and
@@ -206,33 +199,32 @@ turned off by default. See the configure options for NAT-PMP behavior desired:
     --disable-natpmp-default  (the default) NAT-PMP support turned off by default at runtime
     --enable-natpmp-default   NAT-PMP support turned on by default at runtime
 
-Berkeley DB
------------
+## Berkeley DB
+
 It is recommended to use Berkeley DB 4.8. If you have to build it yourself,
 you can use [the installation script included in contrib/](/contrib/install_db4.sh)
 like so:
 
-```shell
-./contrib/install_db4.sh `pwd`
-```
+    ```shell
+    ./contrib/install_db4.sh `pwd`
+    ```
 
 from the root of the repository.
 
 Otherwise, you can build DigiByte Core from self-compiled [depends](/depends/README.md).
 
 **Note**: You only need Berkeley DB if the wallet is enabled (see [*Disable-wallet mode*](#disable-wallet-mode)).
 
-Boost
------
+## Boost
+
 If you need to build Boost yourself:
 
     sudo su
     ./bootstrap.sh
     ./bjam install
 
+## Security
 
-Security
---------
 To help make your DigiByte Core installation more secure by making certain attacks impossible to
 exploit even if a vulnerability is found, binaries are hardened by default.
 This can be disabled with:
@@ -242,9 +234,9 @@ Hardening Flags:
     ./configure --enable-hardening
     ./configure --disable-hardening
 
-
 Hardening enables the following features:
-* _Position Independent Executable_: Build position independent code to take advantage of Address Space Layout Randomization
+
+* *Position Independent Executable*: Build position independent code to take advantage of Address Space Layout Randomization
     offered by some kernels. Attackers who can cause execution of code at an arbitrary memory
     location are thwarted if they don't know where anything useful is located.
     The stack and heap are randomly located by default, but this allows the code section to be
@@ -262,7 +254,7 @@ Hardening enables the following features:
      TYPE
     ET_DYN
 
-* _Non-executable Stack_: If the stack is executable then trivial stack-based buffer overflow exploits are possible if
+* *Non-executable Stack*: If the stack is executable then trivial stack-based buffer overflow exploits are possible if
     vulnerable buffers are found. By default, DigiByte Core should be built with a non-executable stack,
     but if one of the libraries it uses asks for an executable stack or someone makes a mistake
     and uses a compiler extension which requires an executable stack, it will silently build an
@@ -277,8 +269,8 @@ Hardening enables the following features:
 
     The STK RW- means that the stack is readable and writeable but not executable.
 
-Disable-wallet mode
---------------------
+## Disable-wallet mode
+
 When the intention is to run only a P2P node without a wallet, DigiByte Core may be compiled in
 disable-wallet mode with:
 
@@ -288,15 +280,14 @@ In this case there is no dependency on Berkeley DB 4.8 and SQLite.
 
 Mining is also possible in disable-wallet mode using the `getblocktemplate` RPC call.
 
-Additional Configure Flags
---------------------------
+## Additional Configure Flags
+
 A list of additional configure flags can be displayed with:
 
     ./configure --help
 
+## Setup and Build Example: Arch Linux
 
-Setup and Build Example: Arch Linux
------------------------------------
 This example lists the steps necessary to setup and build a command line only, non-wallet distribution of the latest changes on Arch Linux:
 
     pacman -S git base-devel boost libevent python
@@ -313,9 +304,8 @@ or building and depending on a local version of Berkeley DB 4.8. The readily ava
 As mentioned above, when maintaining portability of the wallet between the standard DigiByte Core distributions and independently built
 node software is desired, Berkeley DB 4.8 must be used.
 
+## ARM Cross-compilation
 
-ARM Cross-compilation
--------------------
 These steps can be performed on, for example, an Ubuntu VM. The depends system
 will also work on other Linux distributions, however the commands for
 installing the toolchain will be different.
@@ -334,5 +324,4 @@ To build executables for ARM:
     CONFIG_SITE=$PWD/depends/arm-linux-gnueabihf/share/config.site ./configure --enable-glibc-back-compat --enable-reduce-exports LDFLAGS=-static-libstdc++
     make
 
-
 For further documentation on the depends system see [README.md](../depends/README.md) in the depends directory.