Proofreader API separate from Prompt?

[Colin Mummery]

I've read the Proofreader API description and I'm just trying to plan the user interface for integrating this into my HTML/JS book authoring app. I've already successfully integrated the Prompt and Rewriter APIs for a variety of uses but am I right in thinking that the Proofreader API is using a completely different model install that requires it's own separate download into the browser so that if the ProofReader API is ready to use, this doesn't mean the Prompt/Rewriter API is ready to use or vice-versa? And should I assume that the context window for Proofreader will be the same limited size that Prompt has?