An initial comparison
The first check tells you where your lesson differs from the documentation as it reads today. Some of those differences are years old and were never noticed.
How it works
TeachCurrent compares course content with documentation so you can see what changed, which lesson it affects, and what to update. Four steps, with your judgement at the end of every one.
Bring in a lesson as SRT, VTT or plain text. Timed formats keep the timestamps you supplied; a TXT file is untimed, so findings point at passages rather than moments.
The lesson is compared with documentation inside the supported topic — today that is Shopify theme architecture. Anything outside coverage is reported as unsupported, not as a pass.
Each finding shows the source it came from, the date it was read, and the passage it affects, with an explicit state: confirmed, needs review, or action required.
Accept, adjust or dismiss each finding. Accepted items collect into an update plan with your notes. You make the edits in your own course platform.
The first check tells you where your lesson differs from the documentation as it reads today. Some of those differences are years old and were never noticed.
A change detected at the source later is a separate event with its own date. A changed documentation page still is not proof that the software behaves differently — read the evidence before rewriting a lesson.