Alex Martini

Changing the title heading to "Chapter" seems reasonable to me — if we like that better, I'm fine doing it all on this PR.

Here's a screenshot of what TSPL looks like without the title headings (this PR's change), with [chapter abstracts](https://github.com/apple/swift-book/pull/47) added, and built with current [DocC main](https://github.com/apple/swift-docc/commit/61100a442ff1021405e19de8b4b225e576b19cdd).

Copying my initial assessment of documentation impact from below. Updated the title because it's not just the grammar that needs to be updated. In the Properties > Computed Properties section...

This needs some discussion — the format of documentation comments comes from Swift-DocC, not from the Swift language itself. Teams who use a different tool for their documentation follow that...

Caused by https://github.com/apple/swift-markdown/issues/93

This was considered when the Swift Evolution process started, and we intentionally didn't make this change at the time. I believe the main reason was that the average Swift developer...

Information about which Swift Evolution proposals are implemented when is already available in the [dashboard](https://www.swift.org/swift-evolution/). We shouldn't try to manually replicate that in TSPL — the dashboard pulls the latest...

> The target audience for this document is not those involved with changing the language so much as those learning the language and practitioners whose use the document as a...

I agree that this information should be provided on Swift.org — in fact, that's where the dashboard I linked above is hosted today: https://www.swift.org/swift-evolution/ If you haven't used this dashboard...

Thanks! This change looks like it's probably correct, but I'll need to find someone who can tech review to confirm this is exactly the expected behavior.