Merge pull request #1906 from AntelopeIO/rm-mandel-main

[5.0 -> main] Change remaining references of mandel to leap

docs/00_install/01_build-from-source/00_build-unsupported-os.md

@@ -4,13 +4,9 @@ content_title: Build Antelope from Source on Other Unix-based OS
 
 **Please keep in mind that instructions for building from source on other  unsupported operating systems provided here should be considered experimental and provided AS-IS on a best-effort basis and may not be fully featured.**
 
-### Using DUNE
+**A Warning On Parallel Compilation Jobs (`-j` flag)**: When building C/C++ software often the build is performed in parallel via a command such as `make -j $(nproc)` which uses the number of CPU cores as the number of compilation jobs to perform simultaneously. However, be aware that some compilation units (.cpp files) in leap are extremely complex and will consume nearly 4GB of memory to compile. You may need to reduce the level of parallelization depending on the amount of memory on your build host. e.g. instead of `make -j $(nproc)` run `make -j2`. Failures due to memory exhaustion will typically but not always manifest as compiler crashes.
 
-For the official multi-platform support try [Docker Utilities for Node Execution](https://github.com/AntelopeIO/DUNE) which runs in an ubuntu image via a docker container.  
-
-**A Warning On Parallel Compilation Jobs (`-j` flag)**: When building C/C++ software often the build is performed in parallel via a command such as `make -j $(nproc)` which uses the number of CPU cores as the number of compilation jobs to perform simultaneously. However, be aware that some compilation units (.cpp files) in mandel are extremely complex and will consume nearly 4GB of memory to compile. You may need to reduce the level of parallelization depending on the amount of memory on your build host. e.g. instead of `make -j $(nproc)` run `make -j2`. Failures due to memory exhaustion will typically but not always manifest as compiler crashes.
-
-Generally we recommend performing what we refer to as a "pinned build" which ensures the compiler and boost version remain the same between builds of different mandel versions (mandel requires these versions remain the same otherwise its state needs to be repopulated from a portable snapshot).
+Generally we recommend performing what we refer to as a "pinned build" which ensures the compiler and boost version remain the same between builds of different leap versions (leap requires these versions remain the same otherwise its state needs to be repopulated from a portable snapshot).
 
 <details>
   <summary>FreeBSD 13.1 Build Instructions</summary>

docs/index.md

@@ -10,7 +10,7 @@ Antelope is the next-generation blockchain platform for creating and deploying s
 
 The basic relationship between these components is illustrated in the diagram below.
 
-![Antelope components](mandel_components.png)
+![Antelope components](leap_components.png)
 
 Additional Antelope Resources:
 * [Antelope Utilities](10_utilities/index.md) - Utilities that complement the Antelope software.  

libraries/chain/include/eosio/chain/kv_config.hpp

@@ -6,7 +6,7 @@
 namespace eosio { namespace chain {
 
    /**
-    * @brief limits for a kv database: NOT IN USE for mandel
+    * @brief limits for a kv database: NOT IN USE for leap
     *
     * Each database (ram or disk, currently) has its own limits for these parameters.
     * The key and value limits apply when adding or modifying elements.  They may be reduced