openedge-doc-editor

You can check OpenEdge documentation for style guide and grammar issues by pasting the text, file path, URL, or PDF into the chat. The tool applies a 14-section editorial review and computes metrics like passive voice, lexical density, and forbidden term hits.

Automated editorial review for technical documentation ingests content and evaluates it against style guidelines to ensure consistency. It flags terminology, capitalization, and structure inconsistencies while computing metrics like average sentence length and spelling errors.

Yes, you can review a PDF or URL for passive voice and lexical density. The tool ingests text, file paths, URLs, or PDFs, auto-detects the document type, and calculates linguistic metrics to produce an annotated change sheet.

Yes, the editorial review works with release notes and reference guides. It auto-detects document types including courseware, user guides, reference, and release notes to apply tailored style checks and terminology validation.

The best way to generate an annotated change sheet for technical docs is to run an automated editorial review. It evaluates content against a 14-section style guide and exports a color-coded Word document complete with an executive summary and radar chart.

A limitation of automated proofreading for OpenEdge documentation is its specialization in OpenEdge-specific style guidelines. Its terminology and forbidden term checks are tailored for OpenEdge reference, user guides, and release notes rather than general technical writing.