Under 'Criteria for passing a review'

Reading for content; editing for consistency.

This way MkDocs will be able to report errors for broken links

Done with:

perl -0777 -i -pe \
's@(?<!!)\[([^\]]*)\]\((?!https?://)(?!mailto:)(/(?:(?:(?:/(?![\)#]))|[^/)#])(?!.md))+)/?(#[^)]*)?\)@[$1]($2.md$3)@gm' \
`find . -name '*.md'`

@nganivet and I worked out this wording, based on a discussion in the Extensions Working Group. The aim is to help eliminate surprises and increase trust.

content from:
https://docs.google.com/document/d/1nUfSqIpMQplrj6cv4Nvkxf-dR3NClghhKdB_Xw3MpYY/edit
No substantive content changes, but quite a bit of content clean up
during import

real content

perl -0777 -i -pe 's|^(.*)\n-{3,}$|## $1|gm' `find . -name '*.md'`
perl -0777 -i -pe 's|^(.*)\n={3,}$|# $1|gm' `find . -name '*.md'`

Large scale clean up of markdown code (in almost all files) to conform to markdown conventions that I observed to be used consistently in the official CiviCRM User Guide. These convensions are now documented in the markdownrules.md file

During the meeting of the Extension Working group on 27-Oct-16, we discussed
trade-offs in the names.  (Ex: Now that "Stewardship" has an option for
"Seeking Maintainer", it seems a bit confusing to have "Maturity" as
"Maintained/Unmaintained".) There was support changing these two names and
no opposition.

The goal is to publicize this soon in a public blog.  Hopefully, this is the
last round, but if there's strong feedback we could revise again.

The table layout looks right with `mkdocs` but not with Github. This works in both.