Mission 330

Nano editing bridge

Checkpoint search, save, verification, and recovery-note habits.

Nano and editing
8 minutes Capstone Lesson 330 of 360
nanogrepwc
Lesson 330 of 360 0/360 lessons 0/17 missions Nano and editing · 8 minutes
0%
Continue View profile
Ops lab terminal Training lab
New learnerrank 0XP 0%complete
learner@clairos:/home/learner $ Unix ops lab: type a command, press Enter
Instructions 8 minutes

Click any instruction for the command details, the why, and the common mistake to avoid.

Write the checkpoint note

Run nano lab/editing-bridge.txt. Type exactly: owner=learner, status=verified, rollback=ready on separate lines; find verified with Ctrl+W and save with Ctrl+O.

nano lab/editing-bridge.txt
Verify checkpoint status

Run grep verified lab/editing-bridge.txt.

grep verified lab/editing-bridge.txt
Count checkpoint lines

Run wc -l lab/editing-bridge.txt.

wc -l lab/editing-bridge.txt
Lesson support

What to notice while you play.

Objective

Build repeatable confidence with finishing an edit with observable verification.

Hint

Write the exact checkpoint lines, search for verified with Ctrl+W, and save with Ctrl+O.

Why it matters

Finishing an edit with observable verification helps operators explain what they know before they change anything.

Common mistakes
  • Skipping the output that proves finishing an edit with observable verification.
  • Changing several things before recording a baseline.
Reference

Commands in this lesson.

nano <file>

Open a simulated nano editor.

grep [-i] <text> <file>

Find literal text inside a file.

wc [-l] <file>

Count lines, words, and characters.