This makes it easier to reference these things from other pages.

Broaden the "Coding Standards" chapter to "Development Standards" to
better encompass "Review Standards" as a page.

Remove an errant apostrophe

Minor changes to improve readability and fix typos

I've changed the link for contribution guidelines to an internal link within the guide (rather than an external link to GitHub that links back to the guide).

Updated wordpress checksum links

Tidy up hook_civicrm_buildForm Documentation and remove comments from…

Better to use the constant instead of the literal value

Not sure of the Petition Signature Pages URL - its not Event registration....

Add in some descriptors to the field types and minor tidy of the quc…

Minor changes to improve readability and fix typos

Remove instructions for adding amp settings to apache

Tim and I added these instructions to amp (and improved them) so now
it's better to remove them here.

Improve the terminology section

Clarify the text and ensure that the formatting is consistent with the rules set down in other parts of this style guide(!)

Issue # 397 Replace 'Wordpress' with 'WordPress' to use correct camel casing acco…

Make it clear that the text is an example

Also remove some superfluous commas.

Fix typo

Remove an errant 'k'.

Update markdown.md

removed second instance of guess

Replace 'Wordpress' with 'WordPress' to use correct camel casing according to the WordPress Wordmark and Trademark

Update framework/setting with updated link for settings override and …

Update framework/setting with updated link for settings override and also add in notes in regards to group_name now being domain or contact in 4.7 and update example

Fix typo

Just spotted a typo in my previous change.  That 'v' should have been an 'h'.

Document cv-nodejs and node-civicrm js bindings that can be used to interact with CiviCRM

Little typo

Fix the test for checking your path

The command `which civibuild` returns nothing even if the path is set correctly.