get rid of multiple headings with same content

Author: boegel

docs/including-additional-python-modules.md

@@ -96,7 +96,7 @@ Since EasyBuild 4.2.0, easyblocks from a pull request on GitHub can also
 be included, using `--include-easyblocks-from-pr` (see
 [Using easyblocks from pull requests][github_include_easyblocks_from_pr]).
 
-### Example
+**Example**
 
 The example below shows how all self-implemented easyblocks (both
 software-specific and generic) located in the `$HOME/myeasyblocks`
@@ -123,7 +123,7 @@ path to the corresponding Python modules can be specified via
 To verify that EasyBuild is aware of the additional module naming
 schemes, the `--avail-module-naming-schemes` option can be used.
 
-### Example
+**Example**
 
 The example below shows how all custom module naming schemes located in
 the `$HOME/myebmns` can be included:
@@ -156,7 +156,8 @@ directory named according to the type of component (`compiler`, `mpi`,
 To verify that EasyBuild is aware of the included toolchains,
 `--list-toolchains` can be used.
 
-### Example
+
+**Example**
 
 The example below shows how the support for additional toolchains and
 the required additional compiler/MPI toolchain components implemented by

docs/integration-with-github.md

@@ -729,7 +729,7 @@ have in place already (cfr. [Specify location of working directories][github_git
     you *must* specify a (meaningful) commit message using
     `--pr-commit-msg`, see [Controlling pull request metadata][github_controlling_pr_metadata].
 
-#### Example
+**Example**
 
 For example, to create a pull request for a new version of, let's say,
 EasyBuild:
@@ -802,7 +802,7 @@ the repository, no changes are made to a possible existing working copy.
     When using `--update-pr` you *must* specify a (meaningful) commit message  
     via `--pr-commit-msg`, see [Controlling pull request metadata][github_controlling_pr_metadata].
 
-#### Example
+**Example**
 
 For example, to update pull request \#3153 with a changed easyconfig
 file: