[closeparen]

It depends. An edit button with a WYSIWYG flow is much more conducive to casual fixes/updates than a fork -> clone -> edit -> build -> code review -> land workflow. But in-repo docs are easier to keep in sync with the code itself.

We like Git (alongside the code) for docs that are tightly coupled to the API, and Confluence / Google Docs for more general or high-level descriptions, design discussions, operational procedures, etc.