I’d be happy with a PDF reference tome, but FreeRTOS_Reference_Manual_V10.0.0.pdf says it’s for ‘10.0.0 issue 1’, presumably that’s the issue 1 of the PDF. So it doesn’t look to be versioned per release of FreeRTOS.
I don’t want to double-check everything by searching a history file. I just want to be confined within a document that tries to match the source I’m using. So if needs be, that’s the source itself, but then there’s all the code getting in the way.
Is improving this area on a roadmap? Say by building the documentation from the source, e.g. Doxygen, or maintaining it as mark-up text alongside the source so it’s in lockstep for every code review, etc?