Semiconductors Editing and Proofreading Services

A datasheet is a contract written in tables. A design engineer will build a product around your part on the strength of the numbers in it, commit to a board layout, and discover eighteen months into production that a parameter was typical rather than guaranteed, or specified at 25°C when their enclosure runs at 70. Semiconductor documentation is unforgiving in a way that most technology writing is not: an ambiguous footnote does not cause confusion, it causes a respin, and the customer who paid for that respin remembers which vendor's datasheet caused it.

We edit what semiconductor companies produce — device datasheets and parameter tables, application notes and reference designs, user guides for evaluation boards and development kits, errata documents and product change notices, hardware design guidelines and layout recommendations, register maps and programming guides, firmware and driver documentation, qualification and reliability reports, product selection guides and comparison material, product briefs and marketing collateral, foundry and packaging documentation, and IP core documentation for licensees. Our editors check that every parameter carries its test conditions, that minimum, typical and maximum are used consistently and never interchangeably, and that units, symbols and notation match across the tables, the diagrams and the text.

The errata document is the one that most damages a vendor's reputation when written badly, and it is almost always written under pressure by someone who would rather not be writing it. The failure pattern is euphemism: a description of the anomaly in language so hedged that a customer cannot determine whether their design is affected, and a workaround stated as a possibility rather than an instruction. We rewrite errata so each entry names the conditions under which the fault occurs and the conditions under which it cannot, so the affected silicon revisions and date codes are listed explicitly, so the workaround is a concrete design or firmware change with its cost stated, and so the status — fixed in revision C, no fix planned — is unambiguous. Engineers respect a vendor that documents its faults precisely far more than one that appears to have none, and the alternative is a support engineer explaining the same fault fifty times.

Everything you send is treated in confidence, including pre-release datasheets, qualification data and errata not yet published. Whether you are preparing documentation for a new product family, revising a datasheet that has generated avoidable support traffic, or working in English as an additional language, we can make the documents exact and consistent.