Tip: Choose Save as PDF in the print dialog to download. Use A4 paper size.
Shade in the A or B circle for each question.
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1Version history | ARetyping wastes time because version history already keeps earlier versions. Open version history and restore the version from before the work was deleted. | |
| 2Restore this version | BA list of earlier saved versions of a shared file that shows who changed what and when | |
| 3Give an important saved version a clear name so your team can find it later | CName this version: Final draft v1 | |
| 4See which team member made each edit by looking at colours or names beside each change | DBring back an older saved version of the file so it becomes the current one | |
| 5Someone deleted my work, so I will type it all again from scratch. | ELeaving versions unnamed makes it hard to tell them apart. Name key versions, such as 'Before teacher feedback', and check the names and times of editors. | |
| 6Version history: Version 1, Version 2, Version 3, Version 4 (no names or times) | FShow changes - Mia (blue), Sam (green) |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
Version history — A list of earlier saved versions of a shared file. It shows who changed what and when, so you can name a version or restore an older one.File > Version history > See version historyVersion history > Name this versionPick an older version > Restore this versionEach editor's edits show in their own colourHistory shows who changed what and when