Fixes startdate and enddate comments

[Spaxe]

Use YYYY-MM-DD instead of "YYYY-MM-DD", which offends tools/check.py

[wking]

On Thu, Jan 21, 2016 at 07:06:46PM -0800, Xavier Ho wrote:

Use YYYY-MM-DD instead of "YYYY-MM-DD", which offends
tools/check.py

I'm pretty sure the quotes are intended for:

YYYY-MM-DD

although that isn't consistently applied (e.g. the instructor example
just dives in with the YAML ‘[…]’ which includes double-quotes). The
simple fix would be to pick a safer character like a backtick (`), use
that consistently, and explain it in the README 1. The more robust
solution would be to remove the comments here (just stop after
‘FIXME’) and to document each setting in the README (where you can use
Markdown backtics to get literal examples rendered differently without
visible characters delimiting them).

[gvwilson]

Or modify the comment lines to say:

startdate: FIXME # use YYYY-MM-DD format like 2015-01-01 (no quotes around the date)

??

[wking]

On Fri, Jan 22, 2016 at 02:33:36AM -0800, Greg Wilson wrote:

Or modify the comment lines to say:

startdate: FIXME # use YYYY-MM-DD format like 2015-01-01 (no quotes around the date)

And repeat for every entry where we currently use quote delimiters
that should not be included in the final value? I'd rather just use
backticks and explain not to copy backticks in the README.