A list of unfamiliar software words becomes more useful when each entry points to something you can do or inspect. A definition alone may remain too abstract to help during a task.
Choose three terms from one lesson. For each, write a plain explanation, the place where you encountered it, and one harmless action that demonstrates it. Keep the scope narrow enough to test in a practice file.
For example, an entry for selection might say: “the items the next command will act on.” Its demonstration could be selecting two cells, checking their highlight, and changing only their fill colour. Record what stayed unchanged as well as what changed.
If the same term behaves differently in another application, add that context rather than forcing one universal instruction. The word export, for instance, does not identify a single format or destination across all tools.
Use screenshots only when they clarify the control, and remove personal information first. A cropped image of a button without the surrounding task may be harder to understand than one sentence naming the menu and purpose.
Review the glossary after another practice session. Replace entries that merely repeat a technical term with an example you can explain. The collection should remain small enough to use while working, and specific enough that your future self can reproduce the observation.
Editorial illustration from the site’s image collection.