mirror of
https://github.com/brues-code/ClassicAPI.git
synced 2026-11-16 08:00:42 +00:00
User-facing API docs should describe the contract (behavior, inputs, outputs, errors, observable caveats), not how a method is built or which engine path it uses. Drop the "engine already computes this internally / only adds the binding / comes from the engine's own wrap math / reads what it last drew and compares" narration from the FontString entries, keeping every observable behavior and caveat (the setup requirements, the must-have-rendered-once note, the icon-inclusive widths, the <=1px rounding note).