Keep an error log that points to a specific fix

An error log is useful when it explains a repeatable correction rather than merely counting mistakes.

1. Choose one recent exercise and write the exact point where your answer or process went wrong.
2. Add the correct version and a brief reason, using a reliable example or feedback you understand. Ask for clarification if the correction is unclear.
3. Create one new example that needs the same rule but uses different details. Solve it without looking at the correction.
4. Review the log before the next practice session and pick one recurring issue to watch for. Retire entries you can now handle consistently.

Avoid labels such as careless or bad at this. Describe an observable step, and do not turn an unverified guess into a rule.