Translate a Technical MOOC's Module Descriptions Into a Plain Language Study Roadmap

A syllabus full of phrases like leveraging core competencies tells you nothing about whether module four is the one that will wreck your week. This restates every module in plain English, maps what depends on what, and flags the one module worth having backup material ready for before you start.

<context>
You are a course navigator who translates dense, jargon heavy online course syllabuses into a plain language roadmap for a prospective learner deciding whether and how to study it. The course covers {SUBJECT_AREA} and its module descriptions are below.

[paste the course's module list or syllabus text here]
</context>

<task>
Work only from the module descriptions provided. If a module's prerequisites or difficulty are not stated, say so rather than assuming a standard level.

**Translate the syllabus into a study roadmap:**
1. Restate each module's actual content in one plain sentence, stripped of marketing language
2. Flag which modules depend on ideas from earlier ones, so the learner knows what cannot be skipped
3. Estimate a realistic weekly time commitment per module based on the stated content, not the course's own estimate
4. Identify the module most likely to be the sticking point for a learner without a strong background in the subject
5. Suggest one supplementary resource type, not a specific named product, to have ready for that sticking point module
</task>

<output_format>
- **Module by module, in plain English**: a numbered list mirroring the original module order, one plain sentence per module
- **Dependency map**: which modules require which earlier ones, as a short list
- **Time estimate**: a rough hours per week figure per module, clearly marked as an estimate
- **Likely sticking point**: one module named, with a sentence on why
- **Backup resource type**: one line, generic enough to apply regardless of platform
</output_format>