Let's see if your favorite "GitHub" accomplishes this task, since you expect this from a much smaller company: Searching for "GitHub Markdown" on Google yields

Let's see if your favorite "GitHub" accomplishes this task, since you expect this from a much smaller company: Searching for "GitHub Markdown" on Google yields the following two links at the top: - https://guides.github.com/features/mastering-markdown/ https://guides.github.com/features/mastering-markdown/ - https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax https://docs.github.com/en/github/writing-on-github/getting-... Some snippets from those two pages, where they call their own syntax just "Markdown": > Markdown is a lightweight and easy-to-use syntax for styling all forms of writing on the GitHub platform. > You can use Markdown most places around GitHub: > Here’s an overview of Markdown syntax that you can use anywhere on GitHub.com or in your own text files. > Create sophisticated formatting for your prose and code on GitHub with simple syntax. It's until the bottom of those pages that they start mentioning GitHub Flavored Markdown (GFM). Just like how Obsidian deals with the very same documentation. Not sure what the problem is, Markdown has always been different on different entities on the internet, since there is no common specification. Blaming Obsidian for this seems short-sighted.