Skip to main content
Corrections

What we got wrong.

This is the running record of content we published that was incorrect, with the date it was fixed. It starts on August 7, 2026, when an outside reviewer read the public site cold and we then checked the articles against CompTIA's published objectives and other primary sources. Some of these were found by that review. Some we found ourselves. They are listed the same way either way.

Feature and product changes live on the changelog. This page is only for content that said something untrue. If you find one we have not logged, tell us and it goes here.

9 corrections logged
A+

Blog: the A+ troubleshooting methodology post

What was wrong

The post taught a seven-step troubleshooting methodology and presented it as a scored A+ 220-1201 objective. CompTIA's published 220-1201 objectives list six steps, give the methodology no objective number, and say it "does not constitute a formal objective" on that exam. The seven-step version belongs to Network+ N10-009, where it is scored. The central premise of the post was wrong, not a detail in it.

What it says now

The post teaches the six steps CompTIA publishes for A+, says plainly that the methodology carries no objective number on that exam and is still the workflow help desks hire for, and points to Network+ for the seven-step list.

A+

Blog: several A+ posts, objective numbering

What was wrong

Objective numbers were taken from the retired 220-1101 blueprint while the posts labeled themselves 220-1201. RAM was cited as objective 3.2, which is cables and connectors. A mobile-device post cited a 1.4 in a domain that stops at 1.3. Another cited a 5.7 in a domain that stops at 5.6. Readers mapping their study plan to those numbers were mapping it to an exam that had been retired.

What it says now

Objective numbers across the A+ posts were rechecked one at a time against the current 220-1201 objectives. The references that pointed at retired numbering are gone.

Security+

Blog: the Security+ risk math post

What was wrong

The worked example priced a control at $40,000 a year against exposure it reduced by $30,000, then concluded the control paid for itself. Subtracting the numbers in the example gives a $10,000 a year loss. A student who followed the arithmetic got the opposite answer from the one the post gave them.

What it says now

The example shows the subtraction and teaches the case it had been getting backwards, which is recognizing a control that costs more than the exposure it removes.

Security+

Blog: the incident response phases post

What was wrong

Seven incident-response phases were attributed to NIST, and NIST SP 800-61 Revision 2 was cited as current guidance. NIST withdrew Revision 2 on April 3, 2025. Revision 3 organizes incident response around the six Cybersecurity Framework 2.0 functions, and NIST has not published a seven-phase model. The seven steps in the post are CompTIA's own SY0-701 objective list.

What it says now

The seven steps are attributed to CompTIA, whose list they are. The NIST reference points at the current revision and notes that Revision 2 was withdrawn.

Network+

Blog: the network troubleshooting tools post, TTL

What was wrong

The post read a TTL of 64 in ping output as a zero-hop reply from the local gateway. A TTL you observe cannot establish hop count on its own. The reading only means something once you know the value the sender started with, and different operating systems start at different values.

What it says now

The post explains what a TTL reading supports, what it does not, and what you need to know about the sender before counting hops with it.

Network+

Blog: the network troubleshooting tools post, ping

What was wrong

A successful ping was described as confirmation that the lower layers of the path were healthy. It shows ICMP reachability along the one path you tested, at the moment you tested it. It does not clear the layers underneath, and it does not speak for the traffic you came to fix.

What it says now

The claim is scoped to what the tool returns and the moment it returns it.

Security+

Blog: the MFA factors post

What was wrong

The post counted five authentication factor categories. SY0-701 publishes four factors and treats the remaining items as attributes, which the exam handles as a separate group. Merging the two produced a count a student would have lost marks for.

What it says now

The count is four factors, with attributes named as attributes and kept apart from them.

Network+

Blog: what CompTIA Network+ costs in 2026

What was wrong

The N10-009 exam was listed at $369. That was correct when the post was written and stale after CompTIA moved the price to $399 on June 1, 2026. Anyone budgeting from our number was short by $30.

What it says now

The price reads $399, and the cost posts carry a dated note saying when we last checked them against CompTIA's published pricing.

Platform

Blog: post dates

What was wrong

Sixteen of twenty-two posts printed June 20, 2026 in the byline and in their structured data, which contradicted the date the blog listing showed for the same post. Each post carried its own copy of the date, so the two could drift and did. Queued posts were also readable at their direct URL before their publish date, while the listing described them as still coming up.

What it says now

Post pages read their date from the one record that also drives the blog listing and the sitemap, so there is no second copy to fall out of step. A queued post sends readers back to the blog until its date arrives.

How this page works

  • A correction goes here when something we published was untrue or misleading, not when we reword a page or ship a feature.
  • Entries stay up after they are fixed. Removing them would defeat the purpose of keeping the log.
  • The same August 2026 review also changed claims we could not back, on the platform pages and in the AI policy. Those are itemized on the changelog.
  • Found something wrong in a post? Email support@revystechjourney.com or start from the blog index. Who writes and reviews these posts is on the about page.