aboutsummaryrefslogtreecommitdiff
path: root/docs/markdown/FAQ.md
diff options
context:
space:
mode:
authorLuis Menina <luis.menina@external.softbankrobotics.com>2017-10-23 11:23:58 +0200
committerJussi Pakkanen <jpakkane@gmail.com>2017-10-23 18:43:04 +0200
commit36eb7bf0aaec8428299927b1131341d903df2670 (patch)
tree9133a224ad55c554b515464f236ca6771e8a01b5 /docs/markdown/FAQ.md
parentbe36b0554484f3c015195ecd4199060cf71fd0b1 (diff)
downloadmeson-36eb7bf0aaec8428299927b1131341d903df2670.zip
meson-36eb7bf0aaec8428299927b1131341d903df2670.tar.gz
meson-36eb7bf0aaec8428299927b1131341d903df2670.tar.bz2
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/
Diffstat (limited to 'docs/markdown/FAQ.md')
-rw-r--r--docs/markdown/FAQ.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/markdown/FAQ.md b/docs/markdown/FAQ.md
index 2023c7e..441cd69 100644
--- a/docs/markdown/FAQ.md
+++ b/docs/markdown/FAQ.md
@@ -98,7 +98,7 @@ The only reason why one would use Make instead of Ninja is working on a platform
Just use Ninja, you'll be happier that way. I guarantee it.
-## Why is Meson not just a Python module so I could code my build setup in Python? ##
+## Why is Meson not just a Python module so I could code my build setup in Python?
A related question to this is *Why is Meson's configuration language not Turing-complete?*