* Eliminate "real languages" from our website
We know that this terminology is unfriendly and can be seen as
gatekeeping. We've moved away from it over time, but there are many
traces of it in our documentation -- most notably, even on our
homepage. Instead of "real languages", let's use "familiar languages",
and in places where deeper explanation makes sense in context, we
can say "familiar, general-purpose languages."
The current 2nd-level blurb on the homepage isn't very good right now
anyhow, so this is a convenient change. As we make progress on various
marketing efforts, we will likely make more extensive changes, but
for now this at least fixes this problem. We recently A/B tested
updates without much of an impact, so let's move ahead with this change
and then if we want to test alternatives to "familiar", we can do that.
For instance, we considered "popular", etc.
* Also eliminate "real code"
This way, we'll get build-time errors if we've moved a page around and haven't fixed the link, and it ensures a trailing `/` is present in the generated URL, which avoids unnecessary redirect S3 redirect hops.
* Add markdown linting script; fix markdown lint errors
* Add support for meta description and page title validation
* Add comments
* Fix lint errors; exclude autogenerated tutorials
* Address feedback; add more comments
* Add more checks for redirect pages; no index; and auto generated content
* More fixes for lint errors
* Allow duplicate headings in a page
* More lint error fixes
* Even more lint error fixes
* Getting started guide lint fixes
* Add custom h1 support to docs single pages
* Use custom h1 tags on cloud getting started guides
* Add custom h1 support to docs
* Add custom h1 support to docs lists.html
* Final round of intial lint fixes
* Add markdown linting to build script
* Update README
* Test build failure due to lint error
* Fix lint error so build will pass
* Readability fixes for lint script
