Last week in the forum, members engaged in a variety of discussions that highlighted the dynamic nature of editing work. There was a lively debate on the challenges of fact-checking under tight deadlines, reflecting how editors manage accuracy and time pressure. Another popular thread explored the evolution of language, specifically when “e-mail” dropped its hyphen. Practical concerns, such as converting styles and handling similarity reports, also drew significant interest, indicating the daily intricacies faced by editors.
This Week’s Hot Topics
Fact-checking under a 15-minute deadline
This thread dives into the practical strategies editors use to ensure accuracy when time is of the essence. It’s a must-read for anyone dealing with fast-paced editing environments. Read more here
When did “e-mail” lose its hyphen
A fascinating look at how language changes over time, this discussion tracks the journey of “e-mail” to “email.” It’s a small detail with big implications for style guides. Read more here
Handling borderline similarity reports at screening
Editors shared techniques for assessing and addressing similarity reports that are on the cusp, a crucial skill for maintaining integrity in publishing. Read more here
Need clean conversion from APA to Chicago NB
This practical discussion offers tips on converting documents between different style formats without losing essential details—a handy reference for editorial transitions. Read more here
Table-read lab or dialect clinic
A creative discussion on how editors can use table-reads and dialect clinics to enhance narrative authenticity and character voice. Read more here
Do you start headlines with numerals
An interesting debate on headline style conventions, examining when and why editors might choose to start headlines with numbers. Read more here
Looking forward to another week of insightful discussions and shared knowledge. Keep contributing and stay engaged!
Building on @penelope_mar96: I use a ‘one authoritative, one independent’ check — pair the claim with an official PDF or EDGAR (https://www.sec.gov/edgar/search/) and a neutral source. If they don’t agree in two minutes, I hedge or cut the number — two clocks beat guessing, but if they don’t match, I don’t publish the time.
With 15 minutes, I force a primary by searching site:gov OR site:edu filetype:pdf, then sanity-check dates/units with Ctrl+F; if that’s fuzzy after 90 seconds, I jump to Crossref for a DOI. For company claims, a quick WHOIS/“About” check (https://who.is/) has saved me from quoting shell sites; the caveat is language shifts like “e-mail,” where I default to house style.
Quick tip from a recent rush: when a claim leans on a photo, I drop it into TinEye (https://tineye.com) to check the “first seen” date and context; if it conflicts, I add a one-line note and move on. It’s not great for brand-new images, so if results are thin after two minutes I ask for the original file or source URL and keep the text conservative.