MIME Type item between line 42 and 43.Go ahead and submit a PR to update the table of contents. We don't need a v0.5.1 for this. Worst case scenario, another release candidate could be released before the final v1.0.0. But for small corrections, another rc won't be necessary.
@eksortso I know what you mean, but I'm not sure if docs kind of spec could modify after release. If can, then why there was a v0.3.1, which was only to fix date example.
I don't think there's much value in releasing patch releases for the older version, when we're moving toward a major release. Plus, this isn't significant and the timeline of 0.3.0 vs 0.3.1 would be very different from 0.5.0 vs 0.5.1 if we make the release now.
Feel free to file a PR for adding the "Table of Contents" amendment. Let the mistake in the float example stay-as-is; it can stay that way forever.
So, to answer the question in the title with fewer words: no. But we can fix the "Table of Contents" mistake via a PR to 0.5.0.
Most helpful comment
I don't think there's much value in releasing patch releases for the older version, when we're moving toward a major release. Plus, this isn't significant and the timeline of 0.3.0 vs 0.3.1 would be very different from 0.5.0 vs 0.5.1 if we make the release now.
Feel free to file a PR for adding the "Table of Contents" amendment. Let the mistake in the float example stay-as-is; it can stay that way forever.
So, to answer the question in the title with fewer words: no. But we can fix the "Table of Contents" mistake via a PR to 0.5.0.