Name the page without private details
The fictional schedule page is enough context. A real private account URL or screenshot is unnecessary. The language task does not require troubleshooting access to any service.
Describe the action in order
Say which button you pressed. The order helps the reader understand what led to the observation. Ask Mocchi to simplify the sentence if several clauses obscure the action.
| Japanese | Romaji | Meaning |
|---|---|---|
| 予定のページで、来週のボタンを押しました。 | Yotei no pēji de, raishū no botan o oshimashita. | On the schedule page, I pressed the next-week button. |
State the visible result
The displayed week did not change. That is the observation. It does not establish whether the cause is the browser, network or website code.
| Japanese | Romaji | Meaning |
|---|---|---|
| でも、表示が変わりません。 | Demo, hyōji ga kawarimasen. | But the display does not change. |
Answer a clarification accurately
If asked about an error message, say that none appeared in this fictional version. Avoid supplying a convincing invented error simply to make the report longer.
| Japanese | Romaji | Meaning |
|---|---|---|
| エラーメッセージは出ていません。 | Erā messēji wa dete imasen. | No error message is displayed. |
Practise a spoken follow-up
A suitable AI Sensei exchange can ask which action you tried or what you expected. Answer the specific question. Keep the practice focused on communication rather than treating the teacher as a real support channel.
Review the report for a usable sequence
Ask Mocchi whether page, action and result are distinguishable. Revise one unclear point and try a different fictional interface action. Compare current writing and speaking access when planning regular practice.