Review wording, formatting and consistency to make technical writing clearer.
A systematic style check for your documents: concrete versus abstract wording, clean heading levels, unified numbers and units, sentence length, terminology used the same way throughout. Bilingual drafts get an extra pass — do the Chinese and English versions actually say the same thing? Dropped sentences, mismatched figures and drifting tone surface here.
Every issue arrives with its location and basis, as an accept-or-reject list; direct edits happen only when you ask, and the original stays as its own version, re-checked after editing. Style is checkable, truth isn't: an unverifiable claim gets marked 'needs a source' instead of being smoothed over.
Examples describe the request and the shape of the expected deliverable; they are not completed run results.
Run a style pass on this API guide and report only, no edits: location, basis and quoted text per issue.
A category-grouped issue list with the terminology-and-figures consistency check and 'needs a source' flags, original untouched.
The Chinese and English versions of these user prompts drifted after edits — check paired claims, numbers and caveats, then unify terminology.
A bilingual drift report with itemized fixes, Chinese punctuation left intact, re-checked after editing.
iOS · Android
iOS
Android
MPL-2.0
Floe original guide. Replaces the original candidate with independently authored content; upstream text is not distributed. Candidate identity and provenance remain in the package.
Floe
Publication commit 25e07dbeeb, audited source 84c524b6fb; catalog digest iOS 46196ba57ed7… · Android 16de89d019e2….
Version records ship with the signed catalog; the target and released versions are shown below.
