Content correction
Identify the page, exact statement, supporting evidence, document date, jurisdiction when relevant, and any relationship to the subject.
Email a private correction →One inbox, clear routing
Tell us what you are contacting us about and include the evidence or context needed to understand it. We use one monitored publication address for every inquiry.
Publication inbox
Use this address for editorial, expert, rights, privacy, accessibility, media, or business correspondence.
A clear subject line helps us place the message in the appropriate reviewer. Select the closest option or write directly to the address above.
Identify the page, exact statement, supporting evidence, document date, jurisdiction when relevant, and any relationship to the subject.
Email a private correction →Suggest a primary document, or introduce your qualifications, review scope, availability, and any financial or professional conflicts.
Contact the editorial team →Describe the affected material, personal-data concern, access barrier, or accommodation needed. Include a page URL when one is involved.
Email a rights or privacy inquiry →State the organization, request, intended use, deadline, and any commercial relationship. Editorial coverage cannot be purchased.
Start a conversation →Public correction record
The structured GitHub queue creates a public issue number and keeps the review history visible. Use email when the evidence contains private, rights-sensitive, or identifying information.
Start with our spray foam questions and answers, or ask the Research Desk. The question form sends privately from the website when available. It never publishes your message automatically.
Use the contractor checklist to prepare for an on-site professional. Contact the exact product manufacturer for its current instructions and safety documents. Your local building authority determines applicable permit and code requirements.
Email correspondence is handled according to our privacy notice. Message text is not sent to site analytics.