docs: Markdown headers don't need trailing hash signs

This is a cosmetic change because github seems to interpret those
correctly. Nonetheless, it adds unnecessary noise and makes people
modifying the pages think it might be needed.

See syntax guide at https://guides.github.com/features/mastering-markdown/

1 files changed, 2 insertions, 2 deletions

diff --git a/docs/markdown/Using-multiple-build-directories.md b/docs/markdown/Using-multiple-build-directories.md
index c07b39c68..245564074 100644
--- a/docs/markdown/Using-multiple-build-directories.md
+++ b/docs/markdown/Using-multiple-build-directories.md
@@ -8,7 +8,7 @@ Secondly this makes it very easy to clean your projects: just delete the build s
 
 The true benefit comes from somewhere else, though.
 
-## Multiple build directories for the same source tree ##
+## Multiple build directories for the same source tree
 
 Since a build directory is fully self contained and treats the source tree as a read-only piece of data, it follows that you can have arbitrarily many build trees for any source tree at the same time. Since all build trees can have different configuration, this is extremely powerful. Now you might be wondering why one would want to have multiple build setups at the same time. Let's examine this by setting up a hypothetical project.
 
@@ -36,7 +36,7 @@ The cross compilation file sets up Wine so that not only can you compile your ap
 
 To compile any of these build types, just cd into the corresponding build directory and run `ninja` or instruct your IDE to do the same. Note that once you have set up your build directory once, you can just run Ninja and Meson will ensure that the resulting build is fully up to date according to the source. Even if you have not touched one of the directories in weeks and have done major changes to your build configuration, Meson will detect this and bring the build directory up to date (or print an error if it can't do that). This allows you to do most of your work in the default directory and use the others every now and then without having to babysit your build directories.
 
-## Specialized uses ##
+## Specialized uses
 
 Separate build directories allows easy integration for various different kinds of tools. As an example, Clang comes with a static analyzer. It is meant to be run from scratch on a given source tree. The steps to run it with Meson are very simple.