mirror of
https://github.com/mattpocock/skills.git
synced 2026-06-25 08:24:06 +00:00
Clarify terminology in teaching documentation by replacing 'learner' with 'user' for consistency and improved user experience.
This commit is contained in:
parent
3b37863fc3
commit
dabb725dfd
1 changed files with 2 additions and 2 deletions
|
|
@ -37,7 +37,7 @@ You should be careful to split between two types of learning:
|
|||
- **Fluency strength**: in-the-moment retrieval of knowledge
|
||||
- **Storage strength**: long-term retention of knowledge
|
||||
|
||||
Fluency can give the learner an illusory sense of mastery, but storage strength is the real goal. Try to design lessons which build long-term retention by desirable difficulty:
|
||||
Fluency can give the user an illusory sense of mastery, but storage strength is the real goal. Try to design lessons which build long-term retention by desirable difficulty:
|
||||
|
||||
- Using retrieval practice (recall from memory)
|
||||
- Spacing (distributing practice over time)
|
||||
|
|
@ -71,7 +71,7 @@ Missions may change as the user develops more skills and knowledge. This is norm
|
|||
|
||||
## Zone Of Proximal Development
|
||||
|
||||
Each lesson, the learner should always feel as if they are being challenged 'just enough'.
|
||||
Each lesson, the user should always feel as if they are being challenged 'just enough'.
|
||||
|
||||
The user may specify an exact thing they want to learn. If they don't, figure out their zone of proximal development by:
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue