Start with the word you actually saw
Give the assistant the term and one sentence of non-sensitive context. “What does cache mean in a browser?” is a smaller question than “Teach me computers.” You can ask for familiar language without pretending to know the technical vocabulary.
Leave account details and screenshots containing personal information out of the exercise. A typed description is often enough.
Try a short teaching prompt
Explain a browser cache to someone who is new to computers in under 100 words. Define any technical word you need. Use one everyday analogy, then explain where that analogy stops working. Ask me one question to check my understanding and wait for my reply. Do not ask me to change settings.
If the answer brings in three more unfamiliar terms, follow up: “Please explain just the first sentence with a concrete example.” You can set the pace.
Keep an anchor fact
MDN's web documentation describes a cache as storage for web responses that can be reused when the relevant conditions are met. In beginner terms, a browser may reuse a saved copy of something it previously received instead of fetching it afresh every time.
An analogy might compare that to keeping a frequently used item nearby. The analogy does not explain all the rules about when a saved web response can be reused. Check the linked definition if the explanation starts making broader claims.
Explain it back in your own words
Try: “My understanding is that a cache can let the browser reuse some previously received material. What part of that needs correcting?” Then compare the correction with the documentation.
The assistant can help you practice, but its praise is not proof that your explanation is right. Ask for one example and one counterexample, and check them against the source.
Finish with a small note
Write three lines for yourself: the word, your explanation, and a question you still have. You do not need to change browser settings or install anything to finish this exercise.
For a different word, choose a relevant primary source: the app maker's documentation, a university resource, or an official glossary. Keep the useful explanation and the source together.