Corrections
When we get something substantively wrong, we fix it and log the fix here; small copyedits live in each article's revision history instead. Found an error? Use the "Report issue" button on the article (no account needed). So far we have received 2 reports and reviewed 1, taking a median of 4.8 days. 1 is waiting, the oldest since September 26, 2026. That is our record rather than a promise. See the verifiability policy for how checking works.
321 articles were corrected in the last 30 days. Every correction note and resolved report is listed below, newest first. A fix applied to several articles with the same note is shown once, listing each article; "See the change" opens that version in the article's revision history.
- editorial
Verifier fixes (BlueField-4 announced, not launched, Oct 2025; Fortinet row overstated; Palo Alto and SecurityWeek wording; GPUNetIO early access; per-library references added; editorial lines removed; ref dates/authors)
- editorial
Verifier fixes (release quotes four executives; Boitano quote was from NVIDIA press call reported by CNBC; HF counts actions not agents; multi-agent prover is ongoing work; Meta caveat; Dell PowerEdge is being engineered; SAP wording attributed to NVIDIA)
- editorial
BlueField-2 first announced by Mellanox Aug 2019 (not Oct 2020); unsourced BlueField-3 7 nm claim removed; BlueField-3 generational ratios mis-cited (NVIDIA gave 10x/4x/5x at different dates, now attributed); "industry's first" attributed; BlueField-4 was revealed Oct 2025 with 2026 availability, not launched; BF-4 memory-bandwidth gain differs across NVIDIA posts (3.3x/3x+/4x); first BlueField SoC details and "third pillar", DOCA/CUDA quote, BF-3 adopters re-sourced; product-page tagline updated; broken Grace/Ampere links fixed. Update: NVIDIA Sentry on BlueField-4 (Open Agent Safety Platform, 28 Sep 2026), Rubin six vs seven chips, CMX, STX launch/security/datasheet, Vera Rubin shipping status (Aug 2026), DOCA 3.5.0.
- editorial
Vera was first shown at GTC March 2025 and launched March 16, 2026 (not 'unveiled' June 1, 2026); Vera memory capacity is 3x Grace, not 'roughly doubles'; L2/FP8/PCIe 6/CXL 3.1 are NVIDIA-published, not only 'reported'; 450 W socket figure was mis-cited to SQ Magazine (source is Phoronix; NVIDIA gives 250-450 W configurable TDP); unsupported Rubin CPX claim removed; Cisco was not in the GTC Taipei OEM list (it was in March); GTC Taipei customers were 'exploring', not 'early adopters'; standalone single/dual-socket servers were omitted; SMT 'separate execution lanes' wording replaced with NVIDIA's. Update: first deliveries (May 2026), AWS (Aug 2026), March launch customers (Meta, Alibaba, Cursor, labs), benchmark history (Phoronix, SPEC CPU 2026 whitepaper, Hot Chips 2026, AMD counterclaim), Starmind, and the Sep 28, 2026 OpenShell/Open Agent Safety Platform link.
- editorial
The 'about 17,600' figure was labelled 'Hugging Face activity' but is Hugging Face's count of attacker actions recovered from the agent's logs on the external sandbox for the whole July 9-13 campaign (July 16 disclosure: more than 17,000 recorded events); Hugging Face said five datasets, not 'five private datasets'; July 8/9 timeline rows made precise (internet access began July 8). Update: Later developments to 28 Sep 2026 (Open Secure AI Alliance and SAFE, OpenAI Aug 18 pause and Sep 25 review, Altman, Sep 20 DNS incident, Amodei's 'We Must Pace the Frontier', Hawley investigation, Van Hollen, Blumenthal, Bessent, NVIDIA Open Agent Safety Platform and Boitano's claims with Hugging Face's own counts); May Hugging Face token use, Black Hat talk, HF alert-paging failure, GLM-5.2-NVFP4, law-enforcement report.
- editorial
Russell Bryant misidentified as an NVIDIA maintainer (GitHub lists Red Hat); OWASP LLM01 is Prompt Injection, not Indirect Prompt Injection; LangChain release did not say Deep Agents would run in OpenShell sandboxes; 'NeMo Agent Toolkit' corrected to NVIDIA Agent Toolkit; issue #1868 is a PR; host-wildcard rule, Firecracker startup figure, Daytona open-source status, gVisor and sandbox-runtime rows corrected; unsourced 'project lead' and six-month quote attribution fixed. Update: OpenShell 0.1.0/0.1.2 (Sep 2026), alpha label removed, RFC 0012 supervisor-outside-workload redesign, privacy router/inference.local removed, standalone prover, install and HA changes, closed issues #899/#981, Open Agent Safety Platform (Vera, Sentry/BlueField-4, partner integrations), Windows MXC, stars 8,960 (28 Sep 2026).
- editorial
Removed unsupported claim that the alliance was 'not listed as a formal Linux Foundation project' in early August (its GitHub org called itself 'A Linux Foundation Working Group' from Aug 3); removed unverifiable opensecureaialliance.org-to-NVIDIA-redirect claim; Dropbox no longer on member list (122, not 123); ASRS 'non-punitive' not in LF source; RFC was published by alliance participants and shared by LF; Background wording aligned to OpenAI/HF disclosures. Update: Linux Foundation move (Sep 2 LinkedIn, Sep 14 release), secureaialliance.org + LFX enrollment, SAFE comment deadline Sep 21 and draft status on GitHub (36 issues, 12 PRs, no merged revision) as of Sep 28, NVIDIA Open Agent Safety Platform relationship, CNBC Sep 28 sandbox-escape context, Techstrong reception.
- editorial
OpenAI for Science was announced by Kevin Weil on September 2, 2025
- editorial
Code is Apache 2.0; only weights are under non-commercial terms (verifier V6)
- editorial
Titan schedule table cell matches both releases (verifier V6)
- editorial
Fine-tuning is now priced per base model; outdated up-to-16B rates replaced (verifier V6)
- editorial
RunPod charges no egress fees; RunPod cluster networking and 64-GPU cap; cluster table header (verifier V6)
- editorial
RunPod publishes no reserved-pricing discount (contact sales); cluster networking fabric not specified by RunPod; SOC 2 Type II now claimed (verifier V6)
- editorial
Space.com article date (verifier V4)
- editorial
The ART reverse transcriptase itself was already known; only the system was new (verifier V4)
- editorial
AlphaGenome weights are on Kaggle and Hugging Face, not GitHub; OpenAI Prism is not an autonomous research agent; ART repeat-unit description; unsourced superlative (verifier V4)
- editorial
Architect AX status after May 28, 2026 and 'imminently' quote; description of the CME Compute Futures page
- editorial
Silicon Data 27 Sep readings were $2.70 (H100) and $5.87 (B200); B200 provider expansion was announced June 30, before the CFTC filing; Architect AX status and American Innovation Exchange added (verifier V5)
- editorial
GPU cluster and dedicated-inference rates were out of date (H100 $3.49, H200 $4.19, B200 $7.49 on-demand); update to Together's price page as checked September 2026 and add HGX B300
- editorial
Competitor H100 prices were wrong or stale (AWS p5 $12.29 was the pre-cut rate, CoreWeave $4.76, Crusoe $1.71, RunPod range); update to provider price pages checked September 2026 and date Lambda's own rate tables
- editorial
GPU price table mislabeled Community Cloud rates as Secure Cloud and several rates were out of date; update Pod, serverless flex, and competitor H100 rates to RunPod, Lambda and CoreWeave price pages checked September 2026
- editorial
Model source code and weights were released on 28 January 2026 with the Nature paper (the page said weights were still only planned); added release terms and Google Cloud commercial availability
- editorial
Kevin Weil announced OpenAI for Science on X on 2 September 2025 (not 3 September, the date of press coverage); noted that MIT Technology Review and TechCrunch date a formal announcement to October 2025
- editorial
Edison Scientific was announced on 5 November 2025, not 7 November; the $70M seed/$250M valuation was reported in December 2025 and was miscited to November articles; Kosmos accuracy figure attributed to the Kosmos paper
- editorial
The AI for Science program dates from May 2025, not the Claude Science launch; protein-binder setup per model and 16/15 targets; LSVP wording; auto-retry sourcing; Yahoo date; QbitAI attribution; unsourced details and link targets (verifier V3)